You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Landing pages serve a different purpose than most other documentation pages, and thus they have a different structure than the content-heavy structure that makes up most MyST sites.
For example, they tend to be more UI-heavy, and have elements like Hero boxes, splash pages, etc. They also often get rid of the left/right sidebars so that users focus on the content and don't get distracted.
A good example of this is the MySTMD landing page itself, which has this "blockier" and UI-heavy structure:
Suggestion
We document a workflow for landing pages using the building blocks that are already there (e.g. grids, cards, etc) to show off some best practices.
We create a list of UI components to develop that add different landing page-like functionality (e.g. hero cards, sliding galleries, etc)
Then we could use this as the tracking issue around a "landing page" use-case and chip away at the problem with a combination of new development + documentation.
Landing pages serve a different purpose than most other documentation pages, and thus they have a different structure than the content-heavy structure that makes up most MyST sites.
For example, they tend to be more UI-heavy, and have elements like Hero boxes, splash pages, etc. They also often get rid of the left/right sidebars so that users focus on the content and don't get distracted.
A good example of this is the MySTMD landing page itself, which has this "blockier" and UI-heavy structure:
Suggestion
Then we could use this as the tracking issue around a "landing page" use-case and chip away at the problem with a combination of new development + documentation.
Inspiration
The text was updated successfully, but these errors were encountered: