-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
Implement the new website docs structure #22
Comments
This issue is ready for implement @OlliesWorld |
I can get started on this next week! |
@benjagm question about which are just titles and which are pages. Are Overview, Getting Started and Reference the only titles? Every thing else are links to pages? |
Overview and Reference are just Titles, but Getting Started will be the title of a main section and with new page associated if that is possible. |
Those are just titles and the space is not required. FYI in the screenshot The Basics, JSON Schema Reference and Structuring a Complex Schema should be at same level than What is a Schema.... and if possible not using bold letters. I'll prefer to keep bold for top level sections. |
ok maybe have a subtitle component with less space around it. Keep the bold color, correct? |
Let's keep bold only for top level section. For Titles of subsections we can try: You can try and decide for what option works best. |
@benjagm Here are 2 screenshots for the subtitles. Let me know what yo think. I can push up if you want to see it full browser. Second - took off bold and left the text color the same |
I like the second option. |
This is the PR: #31 |
This is the new content taxonomy agreed in #9
Overview
Getting Started (Create an empty md page)
Reference:
Specification (Existing but poorly structured with multiple embedded sections. Requires analysis and break it into pieces)
The text was updated successfully, but these errors were encountered: