feat(documentation): reorganize the whole documentation#3055
feat(documentation): reorganize the whole documentation#3055
Conversation
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Why not, on the homepage, add another button near "read the docs" to lead directly to components ? (or replace the button wuth "read the components doc") |
|
Maybe in the docs tab, in the left menu,
|
Not quite sure to understand, do you mean the navbar link in the header should be removed ? If yes, where should the homepage button redirect ? |
|
So as far as I understood, the idea is to remove the left menu Components part to insert it in some way inside the Components categories part, maybe via dropdowns or accordions. |
|
|
My understanding of Hannah's proposal is to completely remove the component list from the vertical menu, since we can find them in each category and through the component entry from the horizontal menu. Doing that would add 1 click for users in order to navigate from one component to an other. The component categories and and component list are a bit redundant but I don't see it as a problem, the understanding of "component categories" could be improved. |
815a112 to
29c0f2e
Compare
29c0f2e to
6b86746
Compare
|
I was just browsing and I have a UX issue with the Docs / Components tabs: when I am in the /components page with the visual list and I select one component, the Docs tab becomes active this is a little confusing tbh. |
|
I think we should take the opportunity to remove some pages that are currently draft and seems to me to not have a future in OUDS, like:
Other I'm not sure about:
|
|
For the pages, I'm fine with most of them, just for RTL and Collapse, I'm not sure tbh, but I'm fine with the rest to remove, maybe we can remove them in another PR ? |
There was a problem hiding this comment.
Since it is not a component but a wider guideline for forms, maybe we could move it to "foundation" instead.
| <div class="bd-heading sticky-xl-top align-self-start mt-5 mb-3 mt-xl-0 mb-xl-2"> | ||
| <h3>Figures</h3> | ||
| <a class="d-flex align-items-center" href={getVersionedDocsPath('content/figures')}>Documentation</a> | ||
| <a class="d-flex align-items-center" href={getVersionedDocsPath('/foundation/figures')}>Documentation</a> |
There was a problem hiding this comment.
Not sure if it should be a foundation or a component. It it pretty close to a card.
There was a problem hiding this comment.
TBH, not even sure that we will keep them, but I can set them in the components if you prefer 😄
| <div class="bd-heading sticky-xl-top align-self-start mt-5 mb-3 mt-xl-0 mb-xl-2"> | ||
| <h3>Sizing</h3> | ||
| <a class="d-flex align-items-center" href={getVersionedDocsPath('forms/form-control#sizing')}>Documentation</a> | ||
| <a class="d-flex align-items-center" href="#">Documentation</a> |
There was a problem hiding this comment.
we could keep the link to /components/text-input/#sizing. It is a bootstrap compat feature, but make sense with this page
There was a problem hiding this comment.
There are currently to type of components in the Alerts group in Figma : Alert message and Inline Alert. To stick with our logic, we should keeps the plural form.
There was a problem hiding this comment.
There will be also the Expand link component here, shouldn't we keep the plural ?
There was a problem hiding this comment.
I'm wondering if these "Customize" pages should go to foundation or to customize with a dedicated left menu. We may keep them in foundation and decide when we'll work on them later.
There was a problem hiding this comment.
Customize is only a page right now, but we can make it evolve to be a category just like the others
There was a problem hiding this comment.
Yeah that's what I had in mind. Making customize a category, like foundation, getting-started, ... and having a custom left menu for it with all content related to customization. But maybe part of the content of all these customization pages could be also interesting for general user to understand how it works ?
There was a problem hiding this comment.
I think so indeed at least for general content like this page
| Layout | ||
| </LinkItem> | ||
| <LinkItem | ||
| active={title === 'Components' || Astro.url.pathname.includes('/components/')} |
There was a problem hiding this comment.
The "Components" page of the Foundation category is both active in Getting Started and Components menu, because of the Components title :/
site/src/content/docs/components.mdx
Outdated
| ['Actions', 'Content display', 'Control', 'Data', 'Dialog', 'Indicator', 'Layout', 'Navigation', 'Visual assets'].map((element) => { | ||
| return ( | ||
| <> | ||
| {getData('sidebar-components').filter((group) => group.title === 'Components')[0].pages.filter((page) => page?.category === element).length > 0 && <h3>{element}</h3>} |
There was a problem hiding this comment.
Why don't we have the category title in the TOC ? Could be handy for someone searching for a specific category.
There was a problem hiding this comment.
Not quite sure how to do it, maybe I should add a component for this ? what do you think ?
Co-authored-by: Vincent Prothais <vincent.prothais@orange.com>
Co-authored-by: Maxime Lardenois <maxime.lardenois@orange.com> Co-authored-by: Vincent Prothais <vincent.prothais@orange.com>
Note: Please transform
- [ ]into- (NA)in the description when things are not applicableLast main commit: Release 1.0
Related issues
Closes #3018
Edit #2901 once this PR is merged
Description
Change the whole documentation according to what we decided all together.
If a page is changed or renamed, please check:
category/rather than/categoryMotivation & Context
Better comprehension for users and take the complexity on our side.
Types of change
Live previews
Checklist
Contribution
Accessibility
Design
Development
Documentation
Checklist (for Core Team only)
After the merge