Skip to content
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

Closed
54 tasks done
Tracked by #247
RobTobias123 opened this issue Jan 5, 2024 · 52 comments
Closed
54 tasks done
Tracked by #247

[Docs content] HTML Examples #284

RobTobias123 opened this issue Jan 5, 2024 · 52 comments
Assignees
Labels
question Further information is requested Status: Completed Nothing further to be done with this issue. Awaiting to be closed Type: Documentation Improvements or additions to documentation

Comments

@RobTobias123
Copy link
Contributor

RobTobias123 commented Jan 5, 2024

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

  • Obtain all snippets currently used in storybook and save a local set for modifying
  • Ascertain the consistent use of placeholder text vs BG example text
  • Clean up HTML spacing indentation and formatting, removing unnecessary attributes eg. because default.
  • Apply agreed naming convention (hyphens not underscores) (standard + type + state etc)

Update HTML example files (standard + type + state etc) and check visuals in playground for each component:

  • ns-accordion
  • ns-alert
  • ns-appointment-picker
  • ns-article
  • ns-content
  • ns-calendar
  • ns-card
  • ns-caveat
  • ns-column
  • ns-content
  • ns-cta
  • ns-datepicker
  • ns-download
  • ns-editorial
  • ns-expander
  • ns-fieldset
  • ns-footer
  • ns-form
  • ns-form-group
  • ns-header
  • ns-highlighter
  • ns-icon
  • ns-illustration
  • ns-image
  • ns-inputter
  • ns-landmark
  • ns-live
  • ns-lockup
  • ns-panel
  • ns-password <-- QUESTION ON THIS: [Docs content] HTML Examples #284 (comment)
  • ns-pill
  • ns-price
  • ns-product-card
  • ns-progress <-- QUESTION ON THIS: [Docs content] HTML Examples #284 (comment)
  • ns-selector <-- QUESTION ON THIS: [Docs content] HTML Examples #284 (comment)
  • ns-skeleton
  • ns-skyline
  • ns-standout
  • ns-tab
  • ns-table
  • ns-tabs
  • ns-testimonial
  • ns-timeline
  • ns-timeline-event
  • ns-video
  • nsx-address-selector
  • nsx-footer
  • nsx-header
  • nsx-markting-consent
  • nsx-product-card-overview
@RobTobias123 RobTobias123 self-assigned this Jan 5, 2024
@RobTobias123 RobTobias123 added this to the Internal tools milestone Jan 5, 2024
@RobTobias123
Copy link
Contributor Author

Following discussions and initial trials, we decided the following:

  • All component examples should use 'Hipster Ipsum' placeholder text, unless it is an intrinsic part of that component (eg. 'select a date' on the ns-datepicker). This means that the text will not imply any content and that any description can be made in the docs itself. It is also more scalable should we use for another brand, meaning less maintenance requirements in the future.
  • All experiences will include the relative example content as specific to that brand. eg. ns-header component will show placeholder text, whereas nsx-header (the British Gas experience) would should BG examples of links/content etc. Because experiences may be particular to each brand we feel this is the right approach for now.

@RobTobias123
Copy link
Contributor Author

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

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123 RobTobias123 changed the title Example [Docs content] HTML Examples Jan 5, 2024
@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123 RobTobias123 added the Type: Documentation Improvements or additions to documentation label Jan 9, 2024
@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

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).

@RobTobias123 RobTobias123 added the question Further information is requested label Jan 10, 2024
@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

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?

@RobTobias123
Copy link
Contributor Author

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?

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

RobTobias123 commented Jan 10, 2024

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123
Copy link
Contributor Author

@RobTobias123 RobTobias123 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Status: Completed Nothing further to be done with this issue. Awaiting to be closed Type: Documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant