What is the current behavior?
As a designer, I'd like to have a scaffold page for the /styleguide page when setting up a new project. This page should include commonly used components within an application like; input fields, color palette, typography, etc. Wordpress harmonium seems to have a scaffold page, somewhat, setup for /styleguide page. We talked about setting up a scaffold page for /styleguide page during design meeting on September 23rd, 2020, and there seems to be a general consensus around this.
What is the expected behavior?As a designer;
[ ] When I setup a new project
[ ] Then I am able to see a scaffold /styleguide page
[ ] And I am able to customize the scaffold page /styleguide to reflect project branding and components needs
As an engineer/designer;
[ ] When a new project is setup
[ ] Then the scaffold page for /styleguide is included in the initial scaffold project setup
[ ] When I visit the /styleguide page
[ ] Then I am able to see the following sections already created
[ ] Color palette
[ ] Typography
[ ] Buttons
[ ] Forms and form elements (Select, checkboxes, Radio buttons, input group, media uploader, textarea, input, labels, date picker)
[ ] Alerts
[ ] Badges & Chips
[ ] Cards
[ ] Modals
[ ] Paginations
[ ] Menu (Topbar, Drawer)
[ ] Accordion
[ ] Tabs
[ ] Tables
[ ] Data grid
[ ] Progress bar, loader
For feature requests: why should the behavior change?
Some benefits of having a scaffold styleguide page:
Saves design time if the focus is on removing components that are not needed within a project versus building all needed components from scratch.
This would be a standard scaffold page and updates with changes made to the design token.
I'm submitting a ...
What is the current behavior? As a designer, I'd like to have a scaffold page for the
/styleguide
page when setting up a new project. This page should include commonly used components within an application like; input fields, color palette, typography, etc. Wordpress harmonium seems to have a scaffold page, somewhat, setup for/styleguide
page. We talked about setting up a scaffold page for/styleguide
page during design meeting on September 23rd, 2020, and there seems to be a general consensus around this.What is the expected behavior? As a designer;
/styleguide
page/styleguide
to reflect project branding and components needsAs an engineer/designer;
/styleguide
is included in the initial scaffold project setup/styleguide
pageFor feature requests: why should the behavior change? Some benefits of having a scaffold
styleguide
page:Saves design time if the focus is on removing components that are not needed within a project versus building all needed components from scratch.
This would be a standard scaffold page and updates with changes made to the design token.
[ ] Update reusable stories template