Skip to content

Latest commit

 

History

History
66 lines (53 loc) · 3.85 KB

draft-outline.md

File metadata and controls

66 lines (53 loc) · 3.85 KB
Raw

Draft outline

This is a draft of the course. The topics we'll cover and the order. It will be established and modified based on student needs and how things are going / what people ask for as far as needing things that match the trajectory we're on.

Schedule

This schedule will be modified as we go. Look to it for what we are doing in clas that day / week. This becomes more refined as we get closer to the dates. I modulate based on needing to remediate on concepts of adding concepts based on how far we get that week.

Common issues

Before saying "it doesn't work" with web development in general, please consult this common issues document. It is the solution to 95% of the problems I've seen young web devs have when working with web components, terminal, VS code and javascript/html/css more broadly.

Past weeks

Week 13

Tues

  • There are two projects. You must select a project and state which project you are doing by end of class Tuesday. Read and explore the requirements of each. They are different projects but have similar scopes. One is far more state management heavy as well as very detail oriented in # of requirements. The other is a mix of state management, design, and data structure building on the previous project as far as scope.
  • [project-2a] Character Creator / rpg-me promotional tool
  • [project-2b] Use-cases dashboard comp
  • After making your selection, put in the comments for the issue that you're going to work on the one in question and post a link to the boilerplate hax CLI made repo as your starting point.

Thursday

A reminder of requirements for project creation and submission: PROJECT MUST BE COMPLETED USING THE HAX TOOLING TO ENSURE WE ARE WRITING CODE USING PLATFORM LEVEL WEB COMPONENTS. SUBMISSIONS DONE IN TOOLING AND TECHNOLOGY NOT LIT.DEV BASED WILL NOT BE EVALUATED.

We'll be grouping up based on project selected to answer the following discussion questions:

project-2a Character Creator / rpg-me promotional tool

Sit with 6 people total, not the people you've been collaborating with so that you both get different discussions / perspectives)

  • Where are you starting?

  • What form inputs are you using?

  • What fields are you going to add to your app to manage the relationship between the form and the character?

  • What's the character sizing to be managed responsively?

  • How are you approaching the "stateful" aspect of share links in the URL

  • Any other considerations / unknowns?

  • "we want to make things like 60% of the screen" - rpg-character requires a numerical value for height / width. It can't be % based bc of how SVGs work.

const height = window.innerHeight;
// window width
const width = window.innerWidth;
console.log(height, width);

project-2b Use-cases dashboard comp

  • Where are you starting?
  • Which of the comps are you going off of?
  • What properties need to be accounted for in the data model?
  • What is a good structure for the JSON file?
  • How many unique elements are there to help with scoping?
  • Any other considerations / unknowns?

This will run about 30 minutes and I'd like answers / take aways posted to the thread associated with your project. (adding below this post)

Week 14 - Turkey

end of week 14, Sunday Dec 1 is when check in 1 is due

Week 14,15,16

  • Check ins, review and feedback / critique of submissions associated with Project 2 (TBA)