-
Notifications
You must be signed in to change notification settings - Fork 1
/
index.xml
60 lines (58 loc) · 6.98 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Terminal</title>
<link>https://fortawesome.github.io/culture.github.io/</link>
<description>Recent content on Terminal</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Sat, 09 Apr 2022 21:38:47 -0500</lastBuildDate><atom:link href="https://fortawesome.github.io/culture.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>I_can_has_doc</title>
<link>https://fortawesome.github.io/culture.github.io/posts/i_can_has_doc/</link>
<pubDate>Sat, 09 Apr 2022 21:38:47 -0500</pubDate>
<guid>https://fortawesome.github.io/culture.github.io/posts/i_can_has_doc/</guid>
<description>I CAN HAS DOC? Based on discussions at the last snuggle, we discussed the need for additional documentation. I suggested using the GitHub Pages features as a way that we might improve our documenation and gain some cool features. To quote Mike I thought we could &ldquo;feed two birds with one scone&rdquo; and also document some of our company culture here instead of having to search for interesting culture discussions that happened in slack.</description>
<content><h1 id="i-can-has-doc">I CAN HAS DOC?</h1>
<p>Based on discussions at the last snuggle, we discussed the need for additional documentation. I suggested using the GitHub Pages features as a way that we might improve our documenation and gain some cool features. To quote Mike I thought we could &ldquo;feed two birds with one scone&rdquo; and also document some of our company culture here instead of having to search for interesting culture discussions that happened in slack. To that end, here is a simple example of the GitHub Pages in use.</p>
<h2 id="basic-setup-of-the-site">Basic Setup of the Site</h2>
<ol>
<li>Create a place to store the content, in this case, it is in the culture-awesome repo.</li>
<li>Create a place to host the page, in this case, culture.github.io.</li>
<li>Install <a href="https://gohugo.io/getting-started/quick-start/">Hugo</a>.</li>
<li>Pull down the culture-awesome repo and create a new site.
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>hugo new site culture-blog
</span></span></code></pre></div></li>
<li>Find a dope ass <a href="https://themes.gohugo.io/">theme</a> (in this case we decided on <a href="https://themes.gohugo.io/themes/hugo-theme-terminal/">terminal</a></li>
<li>Clone the theme into the themes folder created when we created a new site
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>git clone https://github.com/panr/hugo-theme-terminal.git themes/terminal
</span></span></code></pre></div></li>
<li>Update the config.toml file (I used the recommended settings <a href="https://themes.gohugo.io/themes/hugo-theme-terminal/#how-to-configure">here</a> with a couple minor tweaks</li>
<li>Create a simple post (the one your currently reading) with&hellip;
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>hugo new posts/i_can_has_doc.md
</span></span></code></pre></div></li>
<li>Write a bunch of stuff in markdown.</li>
<li>Validate everything is working.
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>hugo server
</span></span></code></pre></div></li>
<li>Check it out by navigating to http://localhost:1313</li>
<li>With the initial site setup we need to configure hosting</li>
</ol>
<h2 id="basic-setup-for-hosting">Basic Setup for Hosting</h2>
<ol>
<li>Pull down the culture.github.io repo</li>
<li>We&rsquo;ll make culture-blog a sub-module so we need a main branch and an initial commit (if you want to setup another one of these for yourself one day, otherwise, keep readin')</li>
<li>Use the following command in the culture-blog folder of the culture-awesome repo. This will automatically add our statically generated pages to the GitHub Pages when you run the hugo build commands (again, already complete so just documenting for posterity)
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>git submodule add -b main [email protected]:FortAwesome/culture.github.io.git public
</span></span></code></pre></div></li>
<li>Generate the static files using the name of your theme, in this case terminal
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>hugo -t terminal
</span></span></code></pre></div></li>
<li>Hugo should report that several files and at least one sitemap were created. They should be visible in the /public directory. Additionally if you navigate to the directory and run the following command you should see that the public origin is pointed to our GitHub Page and not the culture-awesome repo
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>git remote -v
</span></span></code></pre></div></li>
</ol>
</content>
</item>
</channel>
</rss>