Checkpoint
Checkpoint A and B
Checkpoint A: Plan/In Progress
Elements of design
Currently, we are working on the layout of the site for design. Our site is extremely design heavy and backend heavy, but I stress the design a lot because it matters more for what we are doing. Last trimester’s project was design-based, but ours is even more so (although backend is equally important). We are trying to make a kids video content platform and we want to ensure that the layout of the site is very organized and super easy to use (especially for small children). For these reasons, we need to think about user accessibility and inclusiveness as much as possible and think about how a child could use our platform.
Evidence of design asset ownership:
Right now, we haven’t got any external assets but we are most likely going to use the template code that is already given to us by the teachers. Any external assets and tools will be listed and updated regularly. Other design assets include a draft we made but that is completely ours (well, we did use Canva).
Checkpoint B: Plan/Code Ready
[Not needed now]
Design Assets
Get comfortable with the design step. Spend the time and effort to go from uncomfortable ‘till you get started to get a little feel. Iteration starts with discomfort.
Story Mapping and Test Planning
Story Mapping and Test Planning
Design Screens
Use tools to design screens before implementation is Figma or Canva or simple Markdown/HTML/CSS screens