proofreading

src/diary/entries/201101

@@ -1,23 +1,23 @@
 <!--200930,201130-->
 <h1>october 2020: a blog that works</h1>
 november 1, 2020<br>
-#css #html #python #webdev #website<br>
+#diary <br>
 <br>
 <h2>week 1 </h2><br>
-#bottle #python #regularexpression #website <br>
+#bottle #git #python #regularexpression #webdevelopment <br>
 <br>
 <h3>thursday, october 1 </h3><br>
 <ul>
-<li>blessfrey.me's diary properly displays snippets for all articles: a header taken from the title, a truncated view of the article, the date + a place for social media share links, and a link to the article.</li>
-<li>Cleaning the snippets enough to look okay and not break the page was a challenge. I used regular expressions to remove HTML link + header tags, <a href="https:/git sta/stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags">which is apparently a lost cause Stack Overflow users stand against daily, hourly even</a>. It's not so bad if it's not user content and the content is pretty predictable, right?
-<li><a href="https://pythex.org/">Pythex</a> is useful for checking whether your regular expression will catch your target strings</li>
-<li>First command line git merge. I usually do it on the website. It's really simple - switch to the branch you're merging the second branch into, type '<code>git merge second-branch</code>' (<code>second-branch</code> = name of the second branch obviously), and fix any conflicts.</li>
+<li>Blessfrey.me's diary properly displays snippets for all articles: a header taken from the title, a truncated view of the article, the date + a place for social media share links, and a link to the article. </li>
+<li>Cleaned the snippets enough to look okay and not break the page was a challenge. I used regular expressions to remove HTML link + header tags, <a href="https:/git sta/stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags">which is apparently a lost cause Stack Overflow users stand against daily, hourly even</a>. It's not so bad if it's not user content and the content is pretty predictable, right? </li>
+<li><a href="https://pythex.org/">Pythex</a> has been useful for checking whether regular expressions will catch target strings </li>
+<li>First command line git merge. I usually do it on the website. It's really simple - switch to the branch you're merging the second branch into, type '<code>git merge second-branch</code>' (<code>second-branch</code> = name of the second branch obviously), and fix any conflicts. </li>
 </ul>
 <br>
 <h3>friday, october 2 </h3><br>
 <ul>
 <li>All articles are kept in the same folder. There's really no reason to split them up. If I want to differentiate types of articles, I can use tags or something.</li>
-<li>Set up blog navigation</li>
+<li>Set up blog navigation </li>
 </ul>
 <br>
 <h3>saturday, october 3 </h3><br>
@@ -27,7 +27,7 @@ november 1, 2020<br>
 </ul>
 <br>
 <h2>week 2 </h2><br>
-#bottle #python #website<br>
+#bottle #pagination #python #webdevelopment<br>
 <br>
 <h3>sunday, october 4 </h3><br>
 <ul>
@@ -42,7 +42,7 @@ november 1, 2020<br>
 <br>
 <h3>tuesday, october 6 </h3><br>
 <ul>
-<li>researched + added a robots.txt, sitemap, nofollow links</li>
+<li>researched and added a robots.txt, sitemap, nofollow links. It's probably unnecessary for my website, but it's fun to LARP that Blessfrey.me is a real professional site.</li>
 <li>added social media share links to all snippets that allow you to share the title and a link to Twitter, Facebook, or email. Not sure if Facebook or email work because I don't feel like getting Facebook or connecting email to my browser.</li>
 </ul>
 <br>
@@ -83,3 +83,5 @@ november 1, 2020<br>
 <li>added 'extra' articles, for articles that are unlisted from the main directory. I'm using it to include more GDC talk notes per talk while keeping the GDC talk article general and summarized.</li>
 </ul>
 <br>
+Last Updated June 8 <br>
+<br>