-
Notifications
You must be signed in to change notification settings - Fork 10
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
Content - long-form #371
Comments
Analysing existing docs content and identifying content to retain and suggested locations. |
Getting Started pages content considered to where it belongs - here with my comments in line (in red/pink etc): https://www.figma.com/file/8SAEjYluT2tYwSPBFHmtjO/371---Content---Long-form?type=design&node-id=1%3A13&mode=design&t=EftvQtEflpI5z2f1-1 Some of this content I have suggested using on the home page, some in a page that doesn't exist yet 'About Nucleus' as too detailed for home page but I don't think it should be left out from the New docs as important. Let me know what you think. |
Foundations pages content considered to where it belongs - here with my comments in line (in red/pink etc): https://www.figma.com/file/8SAEjYluT2tYwSPBFHmtjO/371---Content---Long-form?type=design&node-id=11%3A97&mode=design&t=EftvQtEflpI5z2f1-1 |
Community pages content analysed and considered to where it belongs - here with my comments in line (in red/pink etc): |
Set up a branch from astro docs called feature/long-form-content-populate where I will be adding the proposed content. |
Following yesterday evening's review and feedback session it was agreed that the content suggestions were appropriate and I will be adding/editing on the long-form content pages. |
Multiple pages of content have been added/edited and reconfigured and SVGs created and provided. Reviewed with team. PR for review/approal #408 Including Guidelines pages:
|
Following feedback today - looking into adding a Principles area to Guidelines. |
PR for review - adding principles to guidelines area and moving about us renamed as introduction to outside the containers. Further additions to the Guidelines will be made on this PR such as Accessibility as it is understood. #421 |
approved and merged |
Outcome
A clear definition of what log-form content pages should exist outside of the 'components template', where they live and what content should be on them.
Scope
Take the existing docs Getting Started, Foundations, and Community pages as a starting point to work out where the content belongs. (eg. we may want to remove 'Modular Scale')
Analyse content structure
Describe each in the comments in this ticket and suggest content arrangement using these labels as directives:
The text was updated successfully, but these errors were encountered: