Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Carina Bauman S18 Lions #114

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions .github/PULL_REQUEST_TEMPLATE
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Personal Portfolio Site
Congratulations! You're submitting your assignment!

## Comprehension Questions
Question | Answer
:------------- | :-------------
Did you have to resolve any issues when running the HTML Validator? If so, what were they? |
Why is it important to consider and use semantic HTML? |
How did you decide to structure your CSS? |
What was the most challenging piece of this assignment? |
Describe one area that you gained more clarity on when completing this assignment |
**Optional** |
Did you deploy to GitHub Pages? If so, what is the URL to your website? |
# Personal Portfolio Site
Congratulations! You're submitting your assignment!
## Comprehension Questions
Question | Answer
:------------- | :-------------
Did you have to resolve any issues when running the HTML Validator? If so, what were they? |
Why is it important to consider and use semantic HTML? |
How did you decide to structure your CSS? |
What was the most challenging piece of this assignment? |
Describe one area that you gained more clarity on when completing this assignment |
**Optional** |
Did you deploy to GitHub Pages? If so, what is the URL to your website? |
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
.DS_Store
.DS_Store
.vscode
194 changes: 97 additions & 97 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,97 +1,97 @@
# Personal Portfolio Site

## Introduction

It is 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

We will use HTML & CSS to create a static site whose content is our personal portfolio. Our personal portfolio site should contain information about ourselves and the coding work we've done.

### Some Inspiration
- [http://lizabinante.com/](http://lizabinante.com/)
- [http://where.coraline.codes/](http://where.coraline.codes/)
- [http://danisaurus.github.io/](http://danisaurus.github.io/)
- [http://www.fenslattery.com/](https://fenslattery.com/)
- [https://www.heyellieday.com/](https://heyellieday.com/)
- [http://car.oline.codes/](http://car.oline.codes/)

## Learning Goals:
- Practice creating semantic HTML
- Practice applying visual styles with CSS
- Use both HTML & CSS together to create a comprehensive design

## Project Requirements

### Only Use Static HTML and CSS

We should only 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](https://validator.w3.org/).

## Wave 1 - Basic HTML

This portfolio site must have the following HTML files:

- `index.html` must include your name somewhere.

- `about.html` should include some information about you, your interests, background or similar. Only post what you are comfortable sharing.

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

### Layout

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

- Has the following tags: `<header>`, `<footer>`, and `<nav>`
- Inside of the `<nav>`, there are links to all of the other pages

## Wave 2 - Styling

### Required Content

- Uses at least one CSS file (likely named `style.css`)

## Wave 3 - Layout

### Required Content

Present the elements on the page as you see fit by using the following at least once:
* a grid container with a few grid items
* a flexbox container with a few flex items

Both of these containers do not need to be on the same page. Try using one for one page, and the other for another page!

<details>
<summary>If you need some inspiration, here are two common layouts you can replicate</summary>

![Personal Portfolio Wfireframe Example 1](./assets/personal-portfolio_wireframe1.png)

![Personal Portfolio Wfireframe Example 2](./assets/personal-portfolio_wireframe2.png)
</details>
</br>

### 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](https://validator.w3.org/#validate_by_upload) 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](https://pages.github.com/).
# Personal Portfolio Site
## Introduction
It is 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
We will use HTML & CSS to create a static site whose content is our personal portfolio. Our personal portfolio site should contain information about ourselves and the coding work we've done.
### Some Inspiration
- [http://lizabinante.com/](http://lizabinante.com/)
- [http://where.coraline.codes/](http://where.coraline.codes/)
- [http://danisaurus.github.io/](http://danisaurus.github.io/)
- [http://www.fenslattery.com/](https://fenslattery.com/)
- [https://www.heyellieday.com/](https://heyellieday.com/)
- [http://car.oline.codes/](http://car.oline.codes/)
## Learning Goals:
- Practice creating semantic HTML
- Practice applying visual styles with CSS
- Use both HTML & CSS together to create a comprehensive design
## Project Requirements
### Only Use Static HTML and CSS
We should only 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](https://validator.w3.org/).
## Wave 1 - Basic HTML
This portfolio site must have the following HTML files:
- `index.html` must include your name somewhere.
- `about.html` should include some information about you, your interests, background or similar. Only post what you are comfortable sharing.
- `portfolio.html` must include information about several projects you have completed at Ada (or elsewhere) with links to the GitHub repo (if available), descriptions, images, etc.
### Layout
Each page in this project must comply with the following layout requirements:
- Has the following tags: `<header>`, `<footer>`, and `<nav>`
- Inside of the `<nav>`, there are links to all of the other pages
## Wave 2 - Styling
### Required Content
- Uses at least one CSS file (likely named `style.css`)
## Wave 3 - Layout
### Required Content
Present the elements on the page as you see fit by using the following at least once:
* a grid container with a few grid items
* a flexbox container with a few flex items
Both of these containers do not need to be on the same page. Try using one for one page, and the other for another page!
<details>
<summary>If you need some inspiration, here are two common layouts you can replicate</summary>
![Personal Portfolio Wfireframe Example 1](./assets/personal-portfolio_wireframe1.png)
![Personal Portfolio Wfireframe Example 2](./assets/personal-portfolio_wireframe2.png)
</details>
</br>
### 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](https://validator.w3.org/#validate_by_upload) 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](https://pages.github.com/).
Binary file added assets/fireworks.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/trogdor.jpeg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
96 changes: 96 additions & 0 deletions css/style.css
Original file line number Diff line number Diff line change
@@ -0,0 +1,96 @@
a {
text-decoration: none;
color: tomato;
}

a:hover {
text-underline-offset: 3px;
text-decoration: underline wavy 1px;
color: salmon;
}

.about {
display: grid;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay, grid!

grid-template: auto auto / 1fr 1fr;
column-gap: 10px;
row-gap: 10px;
}

.about-section {
background-color: rgba(255, 235, 205, 50%);
padding: 10px;
}

body {
font-family: 'Helvetica Neue', 'Inter', sans-serif;
color: darkslategray;
}

figcaption {
font-family: 'Avenir Next Condensed', 'Arial Narrow', sans-serif;
font-size: 85%;
color: slategray;
font-style: italic;
text-align: center;
padding-top: 5px;
}

footer {
padding: 5%;
font-family: 'Avenir', 'Montserrat', sans-serif;
font-size: 85%;
color: slategray;
opacity: 75%;
text-align: center;
}

h1, h2, h3, h4 {
font-family: 'Avenir', 'Montserrat', sans-serif;
font-weight: 500;
color: slategray;
text-align: center;
}

#my-story {
grid-column: span 2;
}

img {
display: block;
margin: auto;
border-radius: 10px;
}

.navbar {
display: flex;
flex-flow: row wrap;
justify-content: space-around;
padding: 15px;
background-color: whitesmoke;
}

.portfolio {
display: grid;
grid-template: auto auto / 1fr 1fr;
column-gap: 10px;
row-gap: 10px;
}

.portfolio-section {
background-color: rgba(255, 235, 205, 50%);
padding: 10px;
}

.center-text {
text-align: center;
}

.subtitle {
font-style: italic;
font-size: 90%;
line-height: 25%;
}

ul {
list-style: circle;
}
38 changes: 19 additions & 19 deletions feedback.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
# Personal Portfolio Site
## What We're Looking For

Feature | Feedback
:------------- | :-------------
**Baseline** |
Appropriate Git Usage |
Answered comprehension questions |
Page fully loads |
No broken links (regular or images) |
Includes at least 4 pages and styling |
**HTML** |
Uses the high-level tags for organization: `header, footer, main` |
Appropriately using semantic tags: `section, article`, etc. |
All images include alternate text |
**CSS** |
Using class and ID names in style declarations |
Style declarations are DRY |
**Overall** |
# Personal Portfolio Site
## What We're Looking For
Feature | Feedback
:------------- | :-------------
**Baseline** |
Appropriate Git Usage |
Answered comprehension questions |
Page fully loads |
No broken links (regular or images) |
Includes at least 4 pages and styling |
**HTML** |
Uses the high-level tags for organization: `header, footer, main` |
Appropriately using semantic tags: `section, article`, etc. |
All images include alternate text |
**CSS** |
Using class and ID names in style declarations |
Style declarations are DRY |
**Overall** |
Loading