-
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
Spec list #326
Comments
Here are two PRs to help facilitate the user testing. Neither of these PRs should be merged. Once the tests have been performed these PRs are to be closed. |
Here's the suggested fonts and styles applied to the same spec list - with 48px paragraph spacing and keylines. Just a suggestion using existing styles. https://www.figma.com/file/wyuLUEt3qm01mR8E6Wm2Pf/Nucleus-Docs-exploration---engaging-and-interactive?type=design&node-id=279%3A5416&mode=design&t=T367BSaTQr4S3o4j-1 |
Here's the updated URLs for user testing: Spec table: Spec list: |
Here's the results analysis of significant findings and recommendations from the user testing: |
Summary based on the results of the user testing for specs...
The recommendation is to proceed with using both styles as above. (However, it should be considered if it may be of benefit to utilise the same format for both if it reduces complexity/maintenance effort etc. If that is the case I would suggest using DL for both.) |
To check, take a look at these preview pages:
|
Outcome
Display the specification tables into description lists instead.
Scope
<table>
markup inspecification.astro
with<dl>
properties
into the same list asattributes
The text was updated successfully, but these errors were encountered: