Skip to content

Latest commit

 

History

History
82 lines (56 loc) · 4.06 KB

README.md

File metadata and controls

82 lines (56 loc) · 4.06 KB
Raw

Personal Portfolio Site

Introduction

It's common for developers to create a website to show off their web-dev skills and document their work and interests. These sites often feature things like:

  • A professional introduction of themselves, careers, and interests
  • A portfolio of projects that they've created and/or collaborated on
  • A blog to share their experiences, thoughts, and/or subject matter expertise
  • Other materials to share any non-coding interests and hobbies
  • A site designed to express themselves

Some Inspiration

Learning Goals:

  • Practice creating semantic HTML
  • Practice applying visual styles with CSS
  • Use both HTML & CSS together to create a comprehensive design

Objective

Use HTML & CSS to create a static site whose content is your portfolio. Your personal portfolio site should contain information about you and the coding work you've done.

Project Requirements

Only Use Static HTML and CSS

You are only permitted to use static HTML and CSS for this project. Preprocessors (haml, erb, sass, less, etc.) and Javascript of any kind are not allowed. All submitted HTML needs to pass as valid HTML through an HTML Validator.

Required Pages

This portfolio site must have the minimum four HTML files:

  1. index.html
  2. about.html
  3. portfolio.html
  4. code-journal.html or hobby-blog.html

Details

index.html must include your name somewhere.

about.html should include some information about you, your interests, background or similar. Only post what you're comfortable sharing.

portfolio.html must include information about the projects you've completed at Ada (or elsewhere) with links to GitHub repo if available, descriptions, images, etc.

code-journal.html or hobby-blog.html should be a page with several articles or blog-style posts about either your journey/observations about programming or a hobby you enjoy.

Required Page Layout

Each page in this project must comply with the following layout requirements:

  • Uses at least one CSS file (likely named style.css)
  • Has the following tags: <header>, <footer>, and <nav>
  • Inside of the <nav>, there are links to all of the other pages

Non-Functional Requirements

The site should follow best practices including:

  • All markup should be semantic, with consideration of hierarchy and accessibility
  • CSS should be concise and well formatted
  • Images and stylesheets should be kept in their own folders, called images and stylesheets, respectively
  • Run your site through an HTML Validator and fix all errors before submitting

Optional Enhancements

  • Create a blog/ or code-journal/ directory. Within this directory...
    • create single html file for each entry in your blog/journal
    • update the nav on the rest of your site to reference each entry as a sublist/subnav.
    • update any tags with path references (img, link, a tags) to accommodate for the entries being in a different directory.
  • Create any number of additional pages or directories.

A Word of Caution

A lot of developers find their initial foray into CSS frustrating. Every browser implements the CSS standard a little (or a lot) differently. Learning to manipulate elements and understand the box model takes time. Layout can be especially challenging to developers new to CSS. For this project, focus on understanding the mechanics and semantics of HTML and CSS, and how the two work together.

Optional: Deploy with GitHub Pages

Want more? Make your site live on the internet! There are a lot of ways to go about hosting a live website, but GitHub provides a way to host static sites for free using your GitHub account. Follow the steps listed here.