-
Notifications
You must be signed in to change notification settings - Fork 601
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
chore: update root readme language #3195
chore: update root readme language #3195
Conversation
a186413
to
c1ca345
Compare
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.
I like the alterations. I have some ideas for other things we can do in the readme. I'll send a link for you to look at and see if we want to incorporate anything.
@@ -24,15 +24,15 @@ There are a million and one great ways to build your next website or application | |||
This principle of being unopinionated manifests in several important ways including: | |||
|
|||
* A flat component architecture that lets you compose what you need without struggling with rigid patterns and complex objects. | |||
* Separating base components and style that supports multiple frameworks without re-writing or duplicating styles. This separation also lets you build your own styles, with your styling technology of choice, without having to re-build or duplicate the base components. | |||
* Separating base components from styles and design systems to support multiple implementations without re-writing or duplicating styles. Use the design system to customize existing styled components, or build your own styles, with your design system, without having to re-build or duplicate the base components. |
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.
* Separating base components from styles and design systems to support multiple implementations without re-writing or duplicating styles. Use the design system to customize existing styled components, or build your own styles, with your design system, without having to re-build or duplicate the base components. | |
* Separating base components from styles and design systems to support multiple implementations without re-writing or duplicating styles. Use the design system to customize existing styled components, or build your own styles with your design system, without having to re-build or duplicate the base components. |
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.
The above comma seems un-necessary but disregard if you disagree.
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.
@EisenbergEffect I merge this in so it could go with the other doc work being done over the weekend. If Chris didn't get a chance to resolve this we can do it in a future PR. I presume we'll be doing a wide edit session on all of this documentation in the future as well.
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.
I didn’t see this, but we certainly should do a scrub in the future. For now I’d agree that the most important thing is accurate content. Thx for merging Aaron!
Description
This PR updates the language in the root readme to better represent the current offerings of FAST-DNA.
Issue type checklist
Is this a breaking change?
Process & policy checklist