Skip to content
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

design sytems part 2 #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

EmmanuelTheCoder
Copy link
Contributor

summary added

@netlify
Copy link

netlify bot commented Sep 19, 2020

Deploy request for loving-murdock-96760c pending review.

Review with commit 037d672

https://app.netlify.com/sites/loving-murdock-96760c/deploys


## Conclusion
Obviously, there are not just a few things but alot of things to consider in selecting, creating and using a design system especially for important products. We hope this session has opened you up to the need for a design system and how to go about it.
**[Watch the video here](https://frontendweekly.dev/sessions/design-systems-part-2)**.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no need to add the video URL here. The summary would be displayed on the session page


You can reach the host Segun Ola on twitter @segunolalive, Valentino also on twitter ``@_teenoh_`` and Inumidun on instagram @criedblack.

Feel free to share your thoughts.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this.

@@ -0,0 +1,86 @@
# DESIGN SYSTEMS (part 2)

## Front Matter
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Front matter is a syntax for adding metadata to markdown documents. I gave you an example format in the closed PR. It begins with three dashes and ends with three dashes. The metadata is the key-value pair in between.

Here is a sample.

---
hosts: host names here (comma-separated)
summarized_by: your name here
Other fields here
---

* **Summarized by**: Emmanuel Aiyenigba (@EmmanuelCoder on twitter).


**[Watch the video here](https://frontendweekly.dev/sessions/design-systems-part-2)**.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not necessary because the summary would be displayed alongside the videos



## Conclusion
Obviously, there are not just a few things but alot of things to consider in selecting, creating and using a design system especially for important products. We hope this session has opened you up to the need for a design system and how to go about it.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid using terms like simply, obviously, easy in technical documents. These are very subjective terms. What's easy or obvious to one person due to extensive experience might be really difficult for another person.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants