Website Development Process
Department Head and Applications Project Leads walk through the design with the Lead Designer, takes copious notes and asks for clarification on commonly overlooked things like animation, hover states, content, breakpoints etc.
The Department Head to setup the frontend repo, and create the backend API server. This will allow component development and content population to commerce.
Systems Project Lead to do an initial content population to help programming team during development. It also helps give the main content population effort a template on how to build out the remaining content:
Applications Project Lead to add any packages and common variables to frontend repo.
Applications Project Leads breaks down each component into a list of common components. Then transfer these into GitHub Component Requests issues.
Applications core team and/or freelance team can now select components to build in Storybook and submit for code review.
When components are submitted for review, the Applications Project Leads should review each one (or assign to another developer for cross-reviewing.
Website assembly of built components by the Project Lead.
Get the website deployed to Netlify and ready for the initial design review. Normally this will be using a temporary domain and password protected.
