Update _site static files

4 years ago · f05638e823
parent 3a032ae944
commit f05638e823
4 changed files with 86 additions and 1 deletions
--- a/_site/2020/05/19/clue-announcement.html
+++ b/_site/2020/05/19/clue-announcement.html
@ -0,0 +1,57 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <title>New Game: Clue (coming soon) | tait.tech</title>
+  <link rel="stylesheet" href="/assets/css/style.css">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+</head>
+<body>
+  <div id="wrapper">
+    <nav>
+  <input type="checkbox" id="menu">
+  <label for="menu">&#9776;</label>
+  <div class="menu-content">
+    
+      <a href="/" class="nav-link"  >Home</a>
+    
+      <a href="/blog/" class="nav-link"  >Blog</a>
+    
+      <a href="/links/" class="nav-link"  >Links</a>
+    
+      <a href="/ideas/" class="nav-link"  >Ideas</a>
+    
+      <a href="https://github.com/TTWNO/" class="nav-link"   target="_blank" rel="noopener noreferrer" >Code</a>
+    
+  </div>
+</nav>
+
+    <h1>New Game: Clue (coming soon)</h1>
+<h4 class="post-date line-under">Tuesday, May 19 2020</h4>
+
+<div class="article">
+  <p>Ooo! Exciting!
+Today I want to announce a new project I’ll be working on which should be live within the month of May:
+Clue.</p>
+
+<p>The original board game, implemented in an accessible format via the web.</p>
+
+<p>It uses a Node.js backend and standard Javascript/HTML frontend.
+Nothing fancy.</p>
+
+<p>All the code will be hosted here: <a href="https://github.com/TTWNO/clue">https://github.com/TTWNO/clue</a></p>
+
+<p>It will be licensed under the BSD-3 license, meaning it can be used for any reason—even commercially and without source-code disclosure—without prior authorization, but it <em>must</em> acknowledge that I helped build the end product.</p>
+
+<p>Once the project is live, it will be located at: <a href="">Lame Games</a> (currently a dead link).</p>
+
+
+</div>
+
+    <footer>
+  This page is mirrored on <a href="https://beta.tait.tech/2020/05/19/clue-announcement.html">beta.tait.tech</a>.
+</footer>
+
+  </div>
+</body>
+</html>
--- a/_site/blog/index.html
+++ b/_site/blog/index.html
@ -28,6 +28,17 @@

    <table class="post-list">
  
+    <tr>
+      <td>
+        <h3 class="post-title"><a class="post-title-link" href="/2020/05/19/clue-announcement.html">New Game: Clue (coming soon)</a></h2>
+        <span class="post-date">19 May 2020</span>
+        <div class="post-excerpt"><p>Ooo! Exciting!
+Today I want to announce a new project I’ll be working on which should be live within the month of May:
+Clue.</p>
+</div>
+      </td>
+    </tr>
+  
    <tr>
      <td>
        <h3 class="post-title"><a class="post-title-link" href="/2020/05/01/nginx-socket-io-projects.html">How to use NGINX as a reverse-proxy server for a Node.js application using socket.io</a></h2>
--- a/_site/feed.xml
+++ b/_site/feed.xml
@ -1,4 +1,17 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.0.0">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2020-05-08T17:26:32+00:00</updated><id>http://localhost:4000/feed.xml</id><entry><title type="html">How to use NGINX as a reverse-proxy server for a Node.js application using socket.io</title><link href="http://localhost:4000/2020/05/01/nginx-socket-io-projects.html" rel="alternate" type="text/html" title="How to use NGINX as a reverse-proxy server for a Node.js application using socket.io" /><published>2020-05-01T00:00:00+00:00</published><updated>2020-05-01T00:00:00+00:00</updated><id>http://localhost:4000/2020/05/01/nginx-socket-io-projects</id><content type="html" xml:base="http://localhost:4000/2020/05/01/nginx-socket-io-projects.html">&lt;p&gt;Despite the long name of the article, I have a feeling this may apply to more people than I might think.
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.0.0">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2020-05-19T18:32:35+00:00</updated><id>http://localhost:4000/feed.xml</id><entry><title type="html">New Game: Clue (coming soon)</title><link href="http://localhost:4000/2020/05/19/clue-announcement.html" rel="alternate" type="text/html" title="New Game: Clue (coming soon)" /><published>2020-05-19T00:00:00+00:00</published><updated>2020-05-19T00:00:00+00:00</updated><id>http://localhost:4000/2020/05/19/clue-announcement</id><content type="html" xml:base="http://localhost:4000/2020/05/19/clue-announcement.html">&lt;p&gt;Ooo! Exciting!
+Today I want to announce a new project I’ll be working on which should be live within the month of May:
+Clue.&lt;/p&gt;
+
+&lt;p&gt;The original board game, implemented in an accessible format via the web.&lt;/p&gt;
+
+&lt;p&gt;It uses a Node.js backend and standard Javascript/HTML frontend.
+Nothing fancy.&lt;/p&gt;
+
+&lt;p&gt;All the code will be hosted here: &lt;a href=&quot;https://github.com/TTWNO/clue&quot;&gt;https://github.com/TTWNO/clue&lt;/a&gt;&lt;/p&gt;
+
+&lt;p&gt;It will be licensed under the BSD-3 license, meaning it can be used for any reason—even commercially and without source-code disclosure—without prior authorization, but it &lt;em&gt;must&lt;/em&gt; acknowledge that I helped build the end product.&lt;/p&gt;
+
+&lt;p&gt;Once the project is live, it will be located at: &lt;a href=&quot;&quot;&gt;Lame Games&lt;/a&gt; (currently a dead link).&lt;/p&gt;</content><author><name></name></author><summary type="html">Ooo! Exciting! Today I want to announce a new project I’ll be working on which should be live within the month of May: Clue.</summary></entry><entry><title type="html">How to use NGINX as a reverse-proxy server for a Node.js application using socket.io</title><link href="http://localhost:4000/2020/05/01/nginx-socket-io-projects.html" rel="alternate" type="text/html" title="How to use NGINX as a reverse-proxy server for a Node.js application using socket.io" /><published>2020-05-01T00:00:00+00:00</published><updated>2020-05-01T00:00:00+00:00</updated><id>http://localhost:4000/2020/05/01/nginx-socket-io-projects</id><content type="html" xml:base="http://localhost:4000/2020/05/01/nginx-socket-io-projects.html">&lt;p&gt;Despite the long name of the article, I have a feeling this may apply to more people than I might think.
 If you have a Node.js application which needs socket.io connections that you want to pass throgh nginx’s &lt;code class=&quot;highlighter-rouge&quot;&gt;reverse_proxy&lt;/code&gt; directive then this is the article for you!&lt;/p&gt;

 &lt;p&gt;You &lt;em&gt;must&lt;/em&gt; seperate the socket.io sockets and the static resources.&lt;/p&gt;
--- a/_site/sitemap.xml
+++ b/_site/sitemap.xml
@ -37,6 +37,10 @@
 <lastmod>2020-05-01T00:00:00+00:00</lastmod>
 </url>
 <url>
+<loc>http://localhost:4000/2020/05/19/clue-announcement.html</loc>
+<lastmod>2020-05-19T00:00:00+00:00</lastmod>
+</url>
+<url>
 <loc>http://localhost:4000/2020-04-27-quiz-your-friends-xss.html</loc>
 </url>
 <url>