araedavis / code-blog Goto Github PK

• Add footer (?)
• center img and text better vertically

If page is resized to desktop size, nav stays hidden

• Project page h1 should link to project (use reverse colors on hover so project titles stand out)

Home link or icon will return user to landing portion of the page?

Remaining class 7 MVPs 👍
*Use map where you are transforming one collection into another.
*Use templates to avoid repetition of HTML structure. Use map to convert collections of data into collections of DOM nodes.
*Think of a useful way to use reduce. Maybe you want to put some "fun facts stats" in your footer?

On page load, duplicate categories are handled (removed from menu), but if navigated to again, duplicates appear in menu.

When navigating between routes multiple times, mobile nav toggle opens/closes multiple times. Issue not present on fresh page load.

• Darken blue header color slightly?
• Rescale h1 - h4 font sizing

From Class 6 stretch goals - use e-tags to determine if the json file has been changed, and if so, to do a new AJAX request instead of loading from local storage.

Handlebars and Skeleton aren't playing nicely to create a desktop grid of projects.

Create an array of createdOn dates for repositories. Use Array.reduce() to return the oldest date value.

Create a second function(?) to represent date relative to current date (i.e. xx number of days since I started coding)

Add stat to site footer

Try a CSS-only solution?

• adjust font sizing in body p
• adjust column padding/margins

• create package.json file / npm install / don't commit node_modules!
• add node modules to .gitignore
• create server.js file
• create Procfile
• add heroku as remote
• create new heroku app
• set env vars on heroku
• push
• scale dynos

Make sure CSS files are well-organized

First filter category is blank and returns all projects.

Refactor filter handling and routing to allow for category-specific routes.