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

Day 4 #4

Open
jendiamond opened this issue Jun 29, 2018 · 0 comments
Open

Day 4 #4

jendiamond opened this issue Jun 29, 2018 · 0 comments

Comments

@jendiamond
Copy link
Member

jendiamond commented Jun 29, 2018

DAY 4 - WEEK 2

Monday July 2 2018

“when you don't create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.”
~ Why The Lucky Stiff

Concept & Link Description What are we learning?
Stand Up --- Agile
Terminal Talk
Terminal practice
Install Git Version Control
Push to GitHub Version Control
Create a Navbar HTML/CSS relative / external links
Retro --- Agile

If you haven't already:

  • Install Git

  • Add all your files and directory to your local Repo

    • $ git add .
  • Commit all your files and directory to your local Repo

    • git commit -m 'First commit'`
  • Get Chrome Browser


Git Tutorial

https://tutorialzine.com/2016/06/learn-git-in-30-minutes


Create a git repository by typing.

$ git init

Do each of these commands one at a time...

git status
git add .
git status
git commit -m 'Initial commit'
git status

This chart shows what each command means. This is your git workflow. Which means EVERY TIME we ask you to commit to git and GitHub in this tutorial you should follow these steps. It is a good habit to follow all these steps.

Your Git Workflow :)
git status Check status
git add . Add everything to the repository
git status Check status
git commit -m 'Your comment' Commit everything (-m means message)
git status Check status*

Again I will say, every time you commit, follow these steps. It's good practice and it will help you from getting messed up when things get more complex.
Where it says Your comment this is where you write in what you commit contains. It should note what you did. These comments are meant for you to remember what you did so make them very meaningful.
They are also public for everyone to read for ever. ;) A Note About Git Commit Messages


  1. Create all your code
  2. Create a repo locally
  3. Create a repo on Github with NO README
  4. Create a branch called gh-pages
    • $ git checkout -b gh-pages
  5. Do Git Workflow
  6. Push to Github
    • $ git push origin gh-pages

https://www.thinkful.com/learn/a-guide-to-using-github-pages/start/existing-project/project-page/existing-repo/


Create a Navbar

https://www.w3schools.com/Css/css_navbar.asp


Link all your pages


https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide
http://girldevelopit.github.io/gdi-featured-js-intro/#/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant