Session recording
Project roadmap review
We’re going to pick right back up with your roadmaps, same groups as last week:
-
Bhroovi, Kirsten, Kritika, Rodrigo, Shaurya, Vera, Wenny
-
Alexis, Angelica, Emily, JC, Rebecca, Sachi
-
Cristina, Dhruvil, Hana, Sabrina, Vicky, Zil
-
Hannah, Hao, Lucy, Sarah, Shaoran, Xinyi
Our structure for today:
-
We’ll each see just half of you—so only a few minutes each, with your roadmap
-
Give us a quick recap of your project and any changes/updates since last week
-
And run us through your week-by-week plan (including today’s work), at a high-level
-
When we are not at your table, you will do the same thing with your group!
-
Send your roadmap document to your tablemates, making sure they can comment
-
Each person should leave a comment in the document—noting something they think is missing or has not been accounted for!
-
We expect to see five comments (six, big group) in each of your roadmaps!
Reconvene!
We’ll share our overall notes/feel for where folks are at, today. Also let’s talk about our overall expectations for the projects:
- Some projects depend on specific technical implementation—you need to know if that works by next week
- Focus on one specific feature—many are too broad/big
- Granularity—all the tasks need to be broken down, “user sees button”
- Re-evaluate that feature alone/itself within a matrix
- Re-do your roadmap with these granular/ranked features
- “Features” can fall off—maybe around content-development, “about” pages, etc. that are less important
- Roadmaps change! Don’t feel like you are beholden—these should evolve as you move forward
Local data
We’re going to round out today with a demo of using local data. This is similar to what we did with Are.na—but now working with a JSON file within your project. You could use this as a model for an “API” of your own data:
-
Remember JSON (JavaScript Object Notation)?
- Before we asked Are.na for data, but you can also include it in your project
- You can write your own JSON files by hand, though the syntax is easy to mess up!
- You could start your data from Google Sheets, and use an extension to export (there is a better add-on, but New School IT doesn’t want us to have nice things)
-
Just like with our Are.na projects, we can generate DOM from this data!
- IRL, you’d probably have some kind of templating framework or library—we’ll talk about these soon!
- We’ll again use aÂ
forEach
loop to go through our array of data - For now, we can use the same template literals/strings, in our JS file
- Using
if
/else
conditional logic to apply a class - This still uses the
fetch
API to get the data—but now from our local file!
For next week
-
Finish leaving your comments in your group’s roadmaps, if you didn’t during class today.
-
Pull down our repo and play around with it—see if its concepts will be helpful in your project!
-
You’ll be moving on to the next phase of your project! Again, this will depend on your roadmap—but we think you should Shift into code. We’d like to see you start building, and aim for some semblance of your features/core idea.
Send us your URLs and update us on your progress: