Repository navigation
README: Dojo Coding banner, badges and footer - #1
Merged
Merged
Conversation
Light and dark banner generated with dojo-readme-kit, the README frame shared by every Dojo Coding open-source repo (name, summary, badges in the Dojo palette, link row) and a footer with the Dojo Coding mark.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the README in line with the Dojo Coding open-source look, the same frame as
hacienda-cr, built with
dojo-readme-kit.
docs/assets/, generated fromdocs/assets/banner.tomldocs/assets/README.mdexplains how to regenerate the bannerNote:
package.jsonpublishesdocs/, so the next npm release will also carrydocs/assets/(about 160 KB unpacked, measured withnpm pack --dry-run). Keeping it out of the package would need afilesor.npmignorechange, which this PR does not make.README and assets only; no code changes.