Introduction#

Important

Today’s activity will require that you create a github account work on this during the introduction. If you have not yet have an account, or make sure you can log in to your existing one.

Intro#

My approach to presenting:

  • conversational, open, active

  • not cram in as much as possible

  • my prep is to cut back, decide what I can skip, not make pretty visuals

  • key ideas so that you can learn more later

While we get started, I invite you to:

  • close your email

  • turn off messaging

  • put down your phone

We will have 4 parts to this workshop:

  • setup (me talking)

  • guided work (I do & you follow)

  • self-paced work ( you work & I help; take breaks as you need)

  • wrap up (I will summarize and answer big questions)

Motivation and content#

Learning goals:

  • core ideas of version control

  • basic idea of a static site generator

Key Takeaways:

  • github flow knowledge

  • a working profile website

Version Control is worth it#

phd comics notfinal.doc

source

  • git keeps track of versions of your work

  • currently the norm; other version control systems are increasingly irrelevant

  • GitHub is the most popular host, but there are others

Why this is a good way to make a website#

  • static sites have fast page load times

  • static sites have low security risks (cannot hack what does not exist)

  • using a generator separates content from style (mostly)

  • someone else writes the HTML/CSS/Javascript

  • you can change the theme in ~100 characters or less

  • responsive (adapts to mobile screens) site without doing the work

  • common accessibility built in with no effort

  • GitHub pages is free!

  • very little of this site is GitHub specific, you can move to a different host pretty easily, with just a little understanding

flowchart TD %% u[You] –> |write| subgraph repo md[Markown Files] end md –> sp{Sphinx} sp –> h[HTML, CSS, Js] h–> ghp[GitHub Pages]