-
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
feat: primary styling content pages #1993
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
File structure and names are not final. Might still change
This reverts commit 083c04a.
this is good enough for the 5th, but it could still do with improving in certain sections
Slightly longer term
|
...nt-capabilities/019_styling/01_extending-genesis-components/02_overriding-default-styles.mdx
Show resolved
Hide resolved
</div> | ||
|
||
:::tip | ||
When using the DSC on your application it configure the `rapid` design system, which is the default. It can additionally be used to configure design |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using the DSC on your application it configure the `rapid` design system, which is the default. It can additionally be used to configure design | |
When using the DSC on your application it configures the `rapid` design system, which is the default. It can additionally be used to configure design |
|
||
## Component libraries | ||
|
||
An additional big advantage of this approach is that it's component library agnostic - you can use this approach when using Genesis syntax, as well as libraries like React and Angular. The code examples in this section will be shown as pure `html` and `css`, and then you can apply it to whichever component library you're using. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An additional big advantage of this approach is that it's component library agnostic - you can use this approach when using Genesis syntax, as well as libraries like React and Angular. The code examples in this section will be shown as pure `html` and `css`, and then you can apply it to whichever component library you're using. | |
An additional advantage of this approach is that it's component library agnostic - you can use this approach when using Genesis syntax, as well as libraries like React and Angular. The code examples in this section will be shown as pure `html` and `css`, and then you can apply it to whichever component library you're using. |
Or you could say "yuuuuge advantage" like the guy I keep seeing on the news every night
|
||
##### **Scenario 1: Extending Genesis Components** | ||
In this scenario, you create a new component by extending an existing Genesis component, such as `RapidButton`. This approach is ideal when you need to build reusable, branded components for your design system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice, like this scenario idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few little nitpicks. Nothing "yuuuuge"
ATTENTION! NEW DOCS STRUCTURE
FOR THE NEXT THREE WEEKS, ONLY BRANCH FROM new-docs-structure
OTHERWISE, WAIT UNTIL THE NEW STRUCTURE HAS BEEN RELEASED
Thank you for contributing to the documentation.
Do the changes you have made apply to both Current and Previous versions?
Have you done a trial build to check all new or changed links?
Is there anything else you would like us to know?
This week's exciting advice from the style guide
Write your headings in sentence case:
This is a correct heading.
This is not a correct heading.