Skip to content

Commit 1d86837

Browse files
docs: 📝 Add AI prompts for generating documentation (#3975)
* docs: 📝 Add AI prompts for generating documentation Included tone/style documentation, prompts and rules. Generated / rewrote some documentation using the prompts
1 parent e2529ac commit 1d86837

File tree

7 files changed

+326
-110
lines changed

7 files changed

+326
-110
lines changed

apps/design-system-docs/docs/about/ABOUT_EDS.md

Lines changed: 1 addition & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -38,56 +38,4 @@ Motion is used to focus attention and is not decorative.
3838

3939
**Cross-platform**
4040

41-
Maintains the same UI across platforms---using shared components, tokens and guidelines.
42-
43-
44-
45-
# Meet the EDS core team
46-
47-
When expanded use tab to review current page headings and press enter or space to navigate to the selected section
48-
49-
ABOUT EDS
50-
51-
# Meet the EDS core team
52-
53-
54-
55-
The EDS core team maintains and provides support for the EDS.
56-
57-
with us.
58-
59-
Birte Thornquist
60-
61-
Add notes
62-
63-
Product Owner / UX Designer
64-
65-
Hjalmar Otto Fjøsne
66-
67-
Add notes
68-
69-
Developer / DevOps
70-
71-
Mikael Johannes Leppä
72-
73-
Add notes
74-
75-
Delivery responsible
76-
77-
Oddbjørn Øvernes
78-
79-
Add notes
80-
81-
Frontend Developer
82-
83-
Victor Nystad
84-
85-
Add notes
86-
87-
Team lead / Design Engineer
88-
89-
Marina Lin Arancibia
90-
91-
Add notes
92-
93-
Design System Designer
41+
Maintains the same UI across platforms---using shared components, tokens and guidelines.
Lines changed: 35 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,67 +1,61 @@
11
# Accordion
22

3-
An _accordion_ allows users to collapse and expand sections of content.
3+
The accordion component helps you organise content by allowing users to expand and collapse sections. This keeps pages tidy and makes information easy to scan.
44

5-
## Usage
5+
## When to Use an Accordion
66

7-
Accordions are composed of a header area and a content area. They deliver large amounts of information in user-controlled sections. They can be used to group or hide information which helps to keep order and scannability on a page.
7+
Accordions are useful for grouping related information and reducing visual clutter. They give users control over which sections they view, making it easier to focus on what matters. However, avoid using accordions for critical information that should always be visible.
88

9-
### Simple
9+
**Consider using an accordion when:**
1010

11-
### Different types of headers
11+
- You want to group related information.
12+
- You need to reduce visual clutter on a page.
13+
- Users should be able to choose which sections to view.
1214

13-
15+
## Structure
1416

15-
## Guidelines
16-
17-
### Header area
18-
19-
Whether expanded or collapsed, the header height must be 48px. The header area must contain one action indicating that the section expands or collapses and can contain additional actions. The expand/collapse functionality is tied to the entire header. Additional actions are triggered only by interacting directly with that action.
20-
21-
#### Labels
22-
23-
Labels should be to the point, short and no more than three words. Note that if the label is longer than the maximum width, it will be truncated and should have a provided.
24-
25-
### Content area
17+
An accordion is made up of a header area and a content area. The header is the clickable section that expands or collapses the content. The content area appears when the section is expanded.
2618

27-
When the accordion is expanded, the minimum height for the content area is 96px. There is no maximum height for the content area.
19+
## Guidelines
2820

29-
### Interaction
21+
**Header area:**
3022

31-
Multiple sections can be expanded simultaneously.
23+
- Always 48px in height, whether expanded or collapsed.
24+
- Must include an action to expand or collapse the section.
25+
- You may add extra actions if needed.
26+
- The entire header is clickable for expand/collapse. Additional actions are triggered only by clicking directly on them.
3227

28+
**Labels:**
3329

30+
- Keep labels short and clear, ideally no more than three words.
31+
- If a label is too long, it will be truncated. Provide a tooltip or another method to show the full label.
3432

35-
# Design
33+
**Content area:**
3634

37-
When expanded use tab to review current page headings and press enter or space to navigate to the selected section
35+
- When expanded, the content area should be at least 96px in height. There is no maximum height.
36+
- Users can expand multiple sections at the same time.
37+
- When navigating with a keyboard, use the tab key to move through headings and press enter or space to open a section.
3838

39-
SURFACES
39+
## Accessibility
4040

41-
# Accordion
41+
Make sure all actions are keyboard accessible. Use clear labels and provide tooltips for truncated text. Maintain a logical tab order for easy navigation.
4242

43-
An _accordion_ allows users to collapse and expand sections of content.
43+
When an accordion section is expanded, you can use the tab key to move through headings. Press enter or space to open the selected section. This ensures users can efficiently navigate and interact with accordion sections using a keyboard.
4444

4545
## Implementation in Figma
4646

47-
### Instructions
48-
49-
1. In Figma go to the **Assets Panel** and search for **accordion**.
50-
51-
2. Drag and drop the component in your frame.
52-
53-
3. Rename and resize the component if needed.
54-
55-
4. Choose the variant from the **Design Panel**.
47+
To add an accordion in Figma:
5648

49+
1. Open the Assets Panel and search for "accordion".
50+
2. Drag and drop the component into your frame.
51+
3. Rename and resize it as needed.
52+
4. Select the desired variant from the Design Panel.
53+
<!-- Add link to Figma when the UI-User Interface board is redone-->
5754

55+
## Code Example
5856

59-
# Code
57+
For implementation details and usage examples, please refer to our [Storybook documentation](https://storybook.eds.equinor.com/?path=/docs/surfaces-accordion--docs).
6058

61-
When expanded use tab to review current page headings and press enter or space to navigate to the selected section
62-
63-
SURFACES
64-
65-
# Accordion
59+
---
6660

67-
An _accordion_ allows users to collapse and expand sections of content.
61+
If you have questions or need support, please visit our [Support page](../../support/support.md). We are here to help you organise your content and create accessible, user-friendly experiences.
Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,32 @@
11
# Resources
22

3+
Welcome to the resources hub for the Equinor Design System. Here, you will find helpful links, tools, and guides to support your work, whether you are a developer, designer, QA, or part of a non-IT team. Our goal is to make it easy for you to access everything you need to create consistent, high-quality experiences.
4+
5+
## Design Assets
6+
- [Figma Library](https://www.figma.com/) – Access our official design components and templates.
7+
- [Brand Guidelines](../foundation/ASSETS.md) – Learn about our brand colours, logos, and visual identity.
8+
- [Icon Library](../foundation/assets/) – Download and use our system icons.
9+
10+
## Component Documentation
11+
- [Component Reference](../components/components.md) – Explore usage, props, and examples for all EDS components.
12+
- [Design Tokens](../foundation/DESIGN_TOKENS.md) – Use our colour, spacing, and typography tokens for consistent styling.
13+
14+
## Developer Guides
15+
- [API Documentation](../packages/eds-core-react/) – Find technical details and integration guides for our core packages.
16+
- [Accessibility Guidelines](../foundation/accessibility.md) – Ensure your work meets accessibility standards.
17+
18+
## Tutorials & How-To Guides
19+
- [Getting Started](../about/getting_started.md) – Begin using the design system in your projects.
20+
- [Patterns](../foundation/PATTERNS.md) – Review best practices and reusable patterns.
21+
22+
## Community & Support
23+
- [Support](../support/support.md) – Get help or contact the team for questions.
24+
- [Contribute](https://github.com/equinor/design-system) – Learn how to contribute to the design system.
25+
- [Updates](https://github.com/equinor/design-system/releases) – Stay informed about new releases and improvements.
26+
27+
## External Resources
28+
- [Equinor Brand Assets](https://www.equinor.com/about-us/brand) – Official brand resources.
29+
- [Accessibility Tools](https://www.w3.org/WAI/test-evaluate/) – Tools for testing accessibility.
30+
31+
If you have suggestions for new resources, please reach out via our support page. We are here to help you succeed and ensure you have everything you need to deliver great user experiences.
32+
Lines changed: 28 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,39 @@
1-
# Support
1+
# Support
22

3-
### Get in touch
3+
We are here to help you make the most of the Equinor Design System. Whether you are a developer, designer, QA, or part of a non-IT team, our support team is ready to assist you with advice, onboarding, questions, suggestions, and contributions.
44

5-
The maintains and provides support for the EDS and are here to help.
5+
## How to Get Help
66

7-
They can assist with advice, onboarding, questions, improvement suggestions and incorporating contributions.
7+
If you have a question or need guidance, please reach out to the EDS core team:
88

9-
Get in touch with the EDS core team here:
9+
- Slack: #eds-support (internal Equinor)
10+
- Teams: EDS Core Team (internal Equinor)
11+
- Email: [[email protected]](mailto:[email protected]) (internal Equinor)
1012

11-
- (internal Equinor)
12-
13-
-
14-
- (internal Equinor)
15-
13+
We aim to respond promptly and ensure you have the support you need.
1614

17-
### Report a bug
15+
## Reporting Bugs
1816

19-
GitHub users can create a and fill out the bug template.
17+
If you find a bug, please let us know so we can address it quickly:
2018

21-
Non-GitHub users can get in touch using the channels above.
19+
- GitHub users: [Create an issue](https://github.com/equinor/design-system/issues) and fill out the bug template.
20+
- Non-GitHub users: Contact us using the channels above.
2221

23-
### Request a feature
22+
## Requesting Features
2423

25-
GitHub users can create a and fill out the feature request template.
24+
If you have an idea for a new feature or improvement:
2625

27-
Non-GitHub users can get in touch using the channels above. Examples of feature requests can be added to in Figma.
26+
- GitHub users: [Create a feature request](https://github.com/equinor/design-system/issues) and fill out the template.
27+
- Non-GitHub users: Share your ideas with us through email, Teams, or Slack. You can also add examples to the EDS Figma file.
28+
29+
## Frequently Asked Questions
30+
31+
Visit our FAQ section for answers to common questions and troubleshooting tips. If you cannot find what you need, please contact us directly.
32+
33+
## Contributing and Feedback
34+
35+
We welcome your feedback and contributions. If you would like to help improve the design system, please see our [contribution guide](https://github.com/equinor/design-system/blob/develop/CONTRIBUTING.md) or reach out to the team.
36+
37+
---
38+
39+
Thank you for helping us build a better design system. We look forward to supporting you and working together to create great user experiences.
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
# Documentation Tone and Style
2+
3+
Our documentation should sound consistent, clear and approachable. To achieve this, we've agreed on two official styles: Sprout-inspired and Minimalist.
4+
These styles will be used as the foundation for all documentation.
5+
6+
7+
# 1. Friendly-Professional Style
8+
9+
Inspired by the sprout documentation style, the friendly-professional tone is warm, friendly, and encouraging.
10+
It focuses on building trust and fostering a sense of community. This style uses approachable language,
11+
positive messaging, and creative energy to guide users through the documentation.
12+
The goal is to make readers feel supported and inspired, while clearly connecting information to the brand’s values and purpose.
13+
14+
It's tone is:
15+
16+
Friendly and welcoming: The writing is approachable and encourages creativity and collaboration.
17+
18+
Clear and concise: Information is presented in short, direct sentences with minimal jargon.
19+
20+
Purpose-driven: The documentation often references values, brand purpose, and the importance of consistency.
21+
22+
Inspirational: Phrases like “inspire meaningful customer experiences” and “designed with care” are used to motivate and connect with the reader.
23+
24+
Trust-building: The tone emphasizes reliability, care, and long-term value.
25+
26+
Inclusive: The language is inclusive, using “we” and “our” to foster a sense of community.
27+
28+
Overall, the tone reflects a positive, supportive, and brand-focused voice,
29+
aiming to guide and empower users while reinforcing Sprout’s values and identity.
30+
31+
32+
33+
# 2. Minimalist Style
34+
35+
The minimalist tone is direct, neutral, and efficient. It prioritizes clarity and simplicity, presenting information in a
36+
straightforward manner without unnecessary embellishments. This style uses concise language, clean structure,
37+
and a calm voice to help users quickly find what they need.
38+
The aim is to reduce distractions and make the documentation as accessible and usable as possible.
39+
40+
It's tone is:
41+
42+
Direct and succinct: Information is presented in the fewest words possible,
43+
avoiding unnecessary details or embellishments by using bullet points or short sentences.
44+
45+
Neutral and objective: The writing avoids emotional language, focusing on facts and clarity.
46+
47+
Uncluttered structure: Content is organized with clear headings, short paragraphs, and ample whitespace.
48+
49+
Functional: Instructions and explanations are practical, with a focus on usability and efficiency.
50+
51+
Consistent: Terminology and formatting are uniform throughout, reducing cognitive load.
52+
53+
Calm and understated: The tone is quiet, confident, and avoids hype or persuasive language.
54+
55+
Accessible: Language is simple, avoiding jargon and complex sentence structures.
56+
57+
Overall, minimalist documentation prioritizes clarity, ease of use, and a clean reading experience,
58+
helping users find what they need quickly without distraction.

0 commit comments

Comments
 (0)