lesson |
Writing a readme |
A quick look at writing the correct readme for your portfolio website that’s hosted on GitHub. |
true |
| title |
url |
Writing for the Web |
writing-for-the-web |
|
| title |
url |
Writing checklist |
writing-checklist |
|
| title |
url |
highlight |
Markdown |
markdown |
true |
|
|
| title |
url |
highlight |
Markdown & YAML cheat sheet |
markdown-yaml-cheat-sheet |
true |
|
| title |
url |
highlight |
Writing a readme |
writing-a-readme |
true |
|
|
| url |
repo |
after |
|
portfolio |
*We’re leaving our `coming-soon` repo alone so the page stays online.*
**If you’d like, after you’ve forked the repository you could rename it in the “Settings” tab to something more descriptive, e.g. `thomasjbradley.ca`**
|
|
| title |
before |
Set it up as a hosted website |
There are now two ways you can set your repository up to be hosted on GitHub.
1. Go to the “Settings” for your `portfolio` repo
2. Scroll down to “GitHub Pages” and select “master branch”
3. Then press “Save”
|
|
| title |
before |
youtube |
after |
Writing your “Why” |
When writing about yourself for the Web you want the text to follow the standards we discussed at the start to the class—but you also what your text to have personality.
One way to help reach people and get people to understand your personality—which is really what you want for your portfolio—is to tell them *why* you’re a graphic designer not *what* you are as a graphic designer.
*Watch this video to see it explained a little more thoroughly:*
|
qp0HIF3SfI4 |
You need to write yourself a “why”—to get the right job and work with the right people.
### Poor examples of “what” descriptions
```
Thomas J Bradley
Graphic designer.
```
*Boring…*
```
Thomas J Bradley
I like to design pretty things!
```
*No duh—so does every other graphic designer.*
### Good examples of “why” descriptions
```
Thomas J Bradley, Professor
Learning new stuff kicks ass. I want to inspire the passion for learning and creating in others—the best way to do that is to teach.
```
*Now you can understand a little bit about who I am and why I do what I do.*
```
elizabeth&jane photography
Growing up, my father always had a camera in his hand. He captured everything — there are thousands of images from our lives.
I feel so lucky that I have these moments to look back on: pictures of my parents’ love, images of their happiness, and photos of their joy seeing their kids grow up.
I believe that capturing life stories and moments is so important, not only for you, but for those to whom you mean the most.
```
*Understanding Liz’s personality & why she’s passionate about photography.*
**Write your “why” before moving onto the rest of this lesson.** Your “why” should guide every decision you make about your portfolio website.
*Please call me over and we can read through it and discuss what you’re trying to communicate.*
|
|
| title |
before |
code_lang |
code_file |
code |
notes |
Edit the readme |
We’re going to use [Markdown](/topics/markdown-yaml-cheat-sheet/) to write a simple readme to store in your repository.
The readme should contain this information:
- Your name
- Your “Why”
- Contact information: email, social media, etc.
- Link to Behance, Dribbble, etc.
- Your copyright notice to denote everything is yours.
- Putting an avatar or logo would be good too.
*Basically all the same information that you put on your coming soon page.*
Here’s an example of what your readme should look like:
|
markdown |
README.md |
|
| label |
text |
Type it, type it real good |
Remember the purpose of this lesson is to type the code out yourself—build up that muscle memory in your fingers! |
|
|
|
| title |
before |
Commit & push |
Once you’re happy with the readme content, commit and push to GitHub.
|
|
|