Skip to content
This repository
  • 2 commits
  • 2 files changed
  • 0 comments
  • 1 contributor
6  git/index.html
@@ -34,9 +34,9 @@
34 34
 
35 35
     <article>
36 36
       <header>
37  
-        <hgroup>
38  
-          <h1>Specific Element</h1>
39  
-          <h2>Subtitle</h2>
  37
+        <hgroup class="hero-unit">
  38
+          <h1>Why Git?</h1>
  39
+          <h2>So you never make a mistake again</h2>
40 40
         </hgroup>
41 41
       </header>
42 42
       <section>
49  git/workflow.html
@@ -2,7 +2,7 @@
2 2
 <html lang="en">
3 3
 <head>
4 4
   <meta charset="utf-8">
5  
-  <title>Git: Specific Element</title>
  5
+  <title>Git: Workflow</title>
6 6
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
7 7
 
8 8
   <!--Brief page description:-->
@@ -34,13 +34,52 @@
34 34
 
35 35
     <article>
36 36
       <header>
37  
-        <hgroup>
38  
-          <h1>Specific Element</h1>
39  
-          <h2>Subtitle</h2>
  37
+        <hgroup class="hero-unit">
  38
+          <h1>Git in Your Workflow</h1>
  39
+          <h2>Keep that command line open</h2>
40 40
         </hgroup>
41 41
       </header>
42 42
       <section>
43  
-        <p>And so it begins...</p>
  43
+        <p>
  44
+          One of the hardest things for Git newcomers is figuring out how Git
  45
+          fits with their workflow.
  46
+        </p>
  47
+        <p>
  48
+          Everyone knows that you have to save files on a computer. Whether its
  49
+          an image or a document, <code>File > Save</code> is a routine thing
  50
+          we do to save our work.
  51
+        </p>
  52
+        <p>
  53
+          Git adds a couple of extra steps to the process of saving work.
  54
+        </p>
  55
+        <p>
  56
+          The basic Git-powered workflow looks something like this:
  57
+        </p>
  58
+        <ol>
  59
+          <li>
  60
+            Make some changes to your file
  61
+          </li>
  62
+          <li>
  63
+            Save your file
  64
+          </li>
  65
+          <li>
  66
+            Tell Git about the file or files you want to commit with
  67
+            <code>git add</code>
  68
+          </li>
  69
+          <li>
  70
+            Tell Git to preserve a snapshot of those files with
  71
+            <code>git commit</code>
  72
+          </li>
  73
+          <li>
  74
+            Make some more changes to your file...then add, the commit
  75
+          </li>
  76
+        </ol>
  77
+        <p>
  78
+          In short, you <b>change</b> your file, you <b>save</b> the file,
  79
+          you <b>add</b> it to a list of files ready for preservation, and
  80
+          then you <b>commit</b> it to your repository.
  81
+          <b>Change. Save. Add. Commit.</b>
  82
+        </p>
44 83
       </section>
45 84
       <footer>
46 85
         <p>Notes, stuff...?</p>

No commit comments for this range

Something went wrong with that request. Please try again.