-
Notifications
You must be signed in to change notification settings - Fork 11
A10
First of all, we want to say fantastic work everyone!
By this point you have:
- Conducted basic user testing
- Interviewed project stakeholders
- Written a creative brief + style guide
- Prototyped a mobile-first design
- Adapted to an iterative feedback cycle
- Written semantic HTML markup
- Communicated with peers across schedules/sections
- Followed best development practices (version control/Git)
- Figured out how to troubleshoot code
- …and made yourself super employable!
🎉 👏
That is no small feat.
This next assignment, like this rest, will build upon A1-A9. By the end of this assignment, your group is expected to have:
- 2 HTML pages (
index.htmland a second) - Navigation that links to page #2
- Semantic code (warnings are ok)
- Real content1
- Properly name assets
- Properly named files
- Link to empty CSS file (
application.css) - Expectation to be using Git and working off of develop/feature branches
1: If your project hasn't received content yet, then just do the best you can to find similar placeholder content.
We will be looking at Git contribution and Slack. Be sure to demonstrate your participation in the project: committing code, code review on commits or pull requests, organizing meetings, gathering design assets, attending office hours, etc…
These things do not go unnoticed.
Don't worry that your page is unstyled. We want to make sure we get the structure nailed down before we introduce CSS to the project.
We are here to help you. It's totally okay (in fact encouraged) to ping us for code review.
This is due Monday, November 9, 2015 at 11:59 pm. It will be worth 100 points.