-
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
[Docs content] HTML Examples #284
Comments
Following discussions and initial trials, we decided the following:
|
LInk to the playground index (WIP) displaying a page of examples for visual reference of each component/experience using the modified HTML. (Please do not edit yet). https://playground.nucleus.design/?t=index.html#project=e20d2a4b-b286-40f0-a297-fade0aee3f16 |
ns-password https://playground.nucleus.design/?t=ns-password.html#project=c12de8da-35df-4ed8-9bcf-35641cfdf881 Question: I can only change certain elements of this component to use Hipsum (placeholder text), this results in a mix of both on each types.Is it better to retain all original real words like 'Password' for label, tip text etc in light of this or keep it mixed? (I prefer the former personally). |
ns-progress https://playground.nucleus.design/?t=ns-progress.html#project=3570b832-a1b2-4746-bc31-980fc8505280 Question: On the Form type, Buttons Back and Next are not part of the component and don't work outside of Storybook. Should we omit the buttons in this form.html example? |
ns-selector https://playground.nucleus.design/?t=ns-selector.html#project=0f62bcc9-971c-483e-8eea-3072a38d8941 Question: All these are wrapped in ns-inputter with a label. Is that required for this purpose? |
Outcome
A refined set of HTML examples for each component type and state as required, to pull into the docs where the legacy version used screenshots. Enables users to understand, view or copy the snippet for use in a prototype from one resource, without going to Storybook for a more efficient workflow.
Scope
Update HTML example files (standard + type + state etc) and check visuals in playground for each component:
The text was updated successfully, but these errors were encountered: