Mascot Company Instructions (Final Project)
Build a multi-page site for a whimsical business named after your mascot - the adjective + animal from your introduction. This is the culmination of the semester's project work, done in two parts: Part A (M14B) claims your concept and sets up the folder; Part B (M15) is the final build. Like the midterm, there are no redos on Part B - and peer reviews matter: you must point out at least 3 specific items your classmate can improve before the due date. You may (and should) use AI extensively, while following everything you've learned.
Part a (M14B) - Concept & Setup
- Your business name is your mascot - the adjective's initial matches your first name, the creature's your last (D.I. von Briesen → Dapper Viper). Happy with it? If not, change it everywhere now.
- Come up with a unique whimsical business idea - skim your classmates' choices on the wiki so you don't duplicate. Think kiosks, food trucks, small shops with limited inventory. "Fried chicken" won't cut it. For inspiration: Dave Eggers' TED talk on 826 Valencia (the pirate store), or Bubba's shrimp list.
- Add your name/url/theme to the wiki page adjacent to the Canvas assignment.
- Make a folder named after your mascot (e.g. saltydog/) - in your course folder or webspace root, your choice - and start the site inside it.
- Link to it from your course site's secondary menu, next to your Hobby link.
Part B (M15) - The Site
- Home (index.html) + at least 4 more pages covering Who / What / When / Where / Why / How in words that fit the business (About, Hours, Products, …). Multi-page, a show/hide SPA like the hobby site, or one long page with a jumping menu - you decide.
- Header and footer are single component files loaded from a components folder on every page (M5B style) - unless you get fancy with one main page that loads all others into main, in which case those pages go in components.
- A consistent, working nav on every page, linking to all pages, in the same position throughout.
- Each page: at least 2 paragraphs and 1 image (more is better), plus all the normal page standards.
- A slogan/tagline (not a mission statement) in the header or footer - italics OR "quotes", not both. Say it out loud? Quotes. More describing? Italics. Use strong/em, never b/i.
- No course links (GitHub, freeCodeCamp, etc.) - but the footer should credit you as designer/developer/coder, in a format of your choice.
- An entirely different look and feel from your course site, hobby site, design firm, and personal home page. Minimize divs/classes; everything validates clean.
- 3 dynamic pieces of JS functionality - DOM interaction, dynamic content loading, an API call, a slideshow, an interactive element… Code should have good names, proper indentation, comments that explain and cite sources.
Submitting
- Part A: confirm in the text area that your concept is on the wiki (for this term).
- Part B: summarize in the text area - the 3 dynamic functionalities you included, what your peers said and how you responded, and a general statement of what AI tools you used and how the work got done.
- Then peer reviews: apply these instructions to at least two classmates who don't already have two reviews, naming at least 3 specific improvements each.