-
Notifications
You must be signed in to change notification settings - Fork 4
Add project: show more yaml
examples
#368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I used tabs to show different examples of YAML files, as suggested in #184. It looks great for an initial interactive approach. I like the tabs over the dropdown because it gives the user a clear idea there are more than Sphinx and MkDocs tools supported, which is a good marketing strategy, in my opinion. It also adds an "Others" option that's more generic and shows how to use `build.commands` in a generic way: install dependencies, build, copy assets under `$READTHDOCS_OUTPUT` directory.
I used `highlight.js` to highlight the examples when importing a project. It requires importing a CSS file that I'm not sure where to put it yet. https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.9.0/styles/dark.min.css Besides, I need to know where to place the small chunk of JS code that I added to make this work. Based on #368
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good! I think I might want to retain the dropdown over tabs if possible, the length of tabs and count of tabs will cause this to wrap in awkward ways. The dropdown was used to avoid these two issues.
Co-authored-by: Anthony <[email protected]>
Co-authored-by: Anthony <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great. I think we can tune these examples quite a bit once we have more examples, but they are good for now.
I used tabs to show different examples of YAML files, as suggested in #184. It looks great for an initial interactive approach.
I like the tabs over the dropdown because it gives the user a clear idea there are more than Sphinx and MkDocs tools supported, which is a good marketing strategy, in my opinion.
It also adds an "Others" option that's more generic and shows how to use
build.commands
in a generic way: install dependencies, build, copy assets under$READTHDOCS_OUTPUT
directory.