Add design principles #14
Conversation
| <hr> | ||
|
|
||
| <h2> Dos and Don’ts</h2> | ||
| <p><b>DO:</b> consider these principles when actively making your design decisions. This is the best time to leverage them.</p> |
There was a problem hiding this comment.
Nit: I think that <strong> is preferred over <b> nowadays.
| @@ -14,6 +14,10 @@ const routes = [ | |||
| path: '/getting-started', | |||
| component: () => import('@/views/HomePage.vue') | |||
| }, | |||
| { | |||
| path: '/design-principles', | |||
There was a problem hiding this comment.
This'll work perfectly fine for a top-level page! However, if you prefer MDX, you could always create a directory content/design-principles with an index.mdx file in there and just write Markdown. That strategy would remove the need to write a custom Vue component, and also eliminate the need to add the router entry manually. Just a callout!
There was a problem hiding this comment.
The linter prefers that we always give Vue components multi-word names, such as DesignPrinciples. It's probably not a lint rule we need to keep as an error, but for the time being the quickest fix (to get the build/lookaside running) would be to just rename this I think!
| @@ -164,6 +58,7 @@ const NAV_ITEMS = [ | |||
| { title: 'Release Notes' }, | |||
| { title: 'About Prism' }, | |||
| { title: 'Getting Started', path: '/getting-started' }, | |||
| { title: 'Design Principles Toolkit', path: '/design-principles' }, | |||
There was a problem hiding this comment.
Went ahead and resolved this merge conflict.
Added design principles as per confluence document created originally by Holly Reynolds and Joe Dreimann