-
Notifications
You must be signed in to change notification settings - Fork 7
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
Document Design Principles #144
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
* feat(docs): Add starting sections to "concepts & principles" Ref #144 * typos
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Todos:
|
Should we display in marigold the same doc like in this confluence link? With all links an images? |
I don't think we have implemented all the functions yet, nor the 8 pt grid or am I wrong? |
That's not a component but rather a design principle :)
Viktoria Schwarz ***@***.***> schrieb am Mi., 6. Okt. 2021,
15:37:
… I don't think we have implemented all the functions yet, nor the 8 pt grid
or am I wrong?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#144 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHQUZMNPRHS62NHBOA3PH3UFRGJ3ANCNFSM4LSXDWXQ>
.
|
and what do you basically think about my question? 😄 |
No |
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
IntroductionPrinciples
Concepts
Recipes
|
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
By "design principles" I mean on a technological level, not design design.
When we really start to do some documentation, I guess we also need to tell people about the philosophy and our thinking behind the components and their API. For example, why did we chose the "Box-principle" or why do we use layout components (#118)?
This issue should be used to collect these things. I'll update the description based on our discussion below.
Structure
Let's plan a structure of the docs first:
INTRODUCTION
X
missing?CONCEPTS
The text was updated successfully, but these errors were encountered: