TODO.md

TODO

A running todo list of things we need to do.

• Default layout setup
• Basic page route templates created
• What are we doing about accessibility? Speak with Josh.
• Document storybook in README
• Update wiki with Funkhaus best practices
• Setup z-indexes for the site
• What is the QA process for a component?
• Add Website Development Process to wiki
• Add project Roadmap to wiki
• Add recommended dev environment to wiki (IDE, Prettier etc)
• Create defaults for .env.example
• Create todo.md
• Create components.md
• Design urls to readme
• Recommended packages (TODO show, Vetur (Vue snippets) etc...)
• Basic CSS vars defined
• Storybook installed
• Components directory
• Write Util function to get section name from URI.

Questions for Viget

Answers doc here: https://docs.google.com/document/d/1Oeas8l5lsykkf5H5ch-mVlgx8X3TYQ6VtK8rZ401X2U/edit#heading=h.j3lvkhke0qr

You can reply in the doc, be sure to include an @ mention to notifications if you need further clarification.

Week 1

1. Why does Figma show the body font weight as 600 when it clearly isn't?
2. Are the CSS color values P found correct? Lots of variations that are similar.
3. Is the molecule missing from Research page
4. For dividing lines, where is yellow and blue used?

Week 2

1. Can we be given export SVG permissions in Figma. Or better yet, give us all SVGs in a ZIP?
2. Can we get the homepage header background molecule as one big full SVG. We don't have the skill to assemble them into one SVG. Is it the same one for the shorter headers too?
3. When the main menu is open, is it an overlay of the whole screen? Or 522px height? Or does it push down the page?
4. What is the hover color for the FooterSock links?

Week 3

1. Figma has letter spacing listed as percentage (eg: 1%). This isn't a valid CSS var, how do you want us to translate this to something CSS can work with?