Skip to content

Commit 65479da

Browse files
committed
Added a link to Twitter.
1 parent a33b975 commit 65479da

16 files changed

Lines changed: 405 additions & 234 deletions

‎archives.html‎

Lines changed: 20 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@
2424
</head>
2525
<body>
2626

27-
2827
<nav class="navbar navbar-default">
2928
<div class="container">
3029
<div class="navbar-header">
@@ -42,6 +41,11 @@
4241
<li
4342
class="active" ><a href="/archives">Archives</a></li>
4443

44+
<li
45+
>
46+
<a href="/pages/companies">Companies</a>
47+
</li>
48+
4549
<li
4650
>
4751
<a href="/pages/about">About</a>
@@ -53,10 +57,7 @@
5357
</div><!--/.container-fluid -->
5458
</nav>
5559

56-
5760
<div class="container">
58-
59-
6061
<div class="row">
6162
<div class="col-lg-9">
6263
<div id="content">
@@ -94,22 +95,23 @@ <h4>2019 February</h4>
9495
<div id="sidebar">
9596
<h3>Links</h3>
9697
<ul id="links">
97-
<li><a href="https://clojure.org">Clojure Website</a></li>
98-
<li><a href="https://github.com/ClojureTO">GitHub Organization</a></li>
99-
<li><a href="https://www.meetup.com/Clojure-Toronto/">Meetup</a></li>
100-
<li><a href="http://clojure-to.herokuapp.com">Slack</a></li>
98+
<li><a href="https://github.com/ClojureTO" target="_blank">GitHub</a></li>
99+
<li><a href="https://www.meetup.com/Clojure-Toronto/" target="_blank">Meetup</a></li>
100+
<li><a href="http://clojure-to.herokuapp.com" target="_blank">Slack</a></li>
101+
<li><a href="https://twitter.com/ClojureTO" target="_blank">Twitter</a></li>
102+
<li><a href="https://clojure.org" target="_blank">Clojure</a></li>
101103
</ul>
102104

103-
<div id="recent">
104-
<h3>Recent Posts</h3>
105-
<ul>
106-
107-
<li><a href="/posts/2019-03-05-website-contributing">How to Contribute to ClojureTO Website</a></li>
108-
109-
<li><a href="/posts/2019-02-23-website-behind">What is Behind clojureto.github.io</a></li>
110-
111-
</ul>
112-
</div>
105+
<div id="recent">
106+
<h3>Recent Posts</h3>
107+
<ul>
108+
109+
<li><a href="/posts/2019-03-05-website-contributing">How to Contribute to ClojureTO Website</a></li>
110+
111+
<li><a href="/posts/2019-02-23-website-behind">What is Behind clojureto.github.io</a></li>
112+
113+
</ul>
114+
</div>
113115

114116

115117
<div id="tags">

‎authors/Hildeberto Mendonca.html‎

Lines changed: 20 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@
2424
</head>
2525
<body>
2626

27-
2827
<nav class="navbar navbar-default">
2928
<div class="container">
3029
<div class="navbar-header">
@@ -42,6 +41,11 @@
4241
<li
4342
><a href="/archives">Archives</a></li>
4443

44+
<li
45+
>
46+
<a href="/pages/companies">Companies</a>
47+
</li>
48+
4549
<li
4650
>
4751
<a href="/pages/about">About</a>
@@ -53,10 +57,7 @@
5357
</div><!--/.container-fluid -->
5458
</nav>
5559

56-
5760
<div class="container">
58-
59-
6061
<div class="row">
6162
<div class="col-lg-9">
6263
<div id="content">
@@ -93,22 +94,23 @@ <h4>2019 February</h4>
9394
<div id="sidebar">
9495
<h3>Links</h3>
9596
<ul id="links">
96-
<li><a href="https://clojure.org">Clojure Website</a></li>
97-
<li><a href="https://github.com/ClojureTO">GitHub Organization</a></li>
98-
<li><a href="https://www.meetup.com/Clojure-Toronto/">Meetup</a></li>
99-
<li><a href="http://clojure-to.herokuapp.com">Slack</a></li>
97+
<li><a href="https://github.com/ClojureTO" target="_blank">GitHub</a></li>
98+
<li><a href="https://www.meetup.com/Clojure-Toronto/" target="_blank">Meetup</a></li>
99+
<li><a href="http://clojure-to.herokuapp.com" target="_blank">Slack</a></li>
100+
<li><a href="https://twitter.com/ClojureTO" target="_blank">Twitter</a></li>
101+
<li><a href="https://clojure.org" target="_blank">Clojure</a></li>
100102
</ul>
101103

102-
<div id="recent">
103-
<h3>Recent Posts</h3>
104-
<ul>
105-
106-
<li><a href="/posts/2019-03-05-website-contributing">How to Contribute to ClojureTO Website</a></li>
107-
108-
<li><a href="/posts/2019-02-23-website-behind">What is Behind clojureto.github.io</a></li>
109-
110-
</ul>
111-
</div>
104+
<div id="recent">
105+
<h3>Recent Posts</h3>
106+
<ul>
107+
108+
<li><a href="/posts/2019-03-05-website-contributing">How to Contribute to ClojureTO Website</a></li>
109+
110+
<li><a href="/posts/2019-02-23-website-behind">What is Behind clojureto.github.io</a></li>
111+
112+
</ul>
113+
</div>
112114

113115

114116
<div id="tags">

‎cryogen.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ http://clojureto.github.io
1212
Website of the Clojure Community Living or Working in Toronto, Ontario, Canada.
1313
</description>
1414
<lastBuildDate>
15-
Wed, 06 Mar 2019 22:03:37 -0500
15+
Sun, 17 Mar 2019 22:57:17 -0400
1616
</lastBuildDate>
1717
<generator>
1818
clj-rss

‎feed.xml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ http://clojureto.github.io
1212
Website of the Clojure Community Living or Working in Toronto, Ontario, Canada.
1313
</description>
1414
<lastBuildDate>
15-
Wed, 06 Mar 2019 22:03:37 -0500
15+
Sun, 17 Mar 2019 22:57:17 -0400
1616
</lastBuildDate>
1717
<generator>
1818
clj-rss
@@ -28,7 +28,7 @@ http://clojureto.github.io/posts/2019-03-05-website-contributing
2828
How to Contribute to ClojureTO Website
2929
</title>
3030
<description>
31-
&lt;p&gt;The wind is blowing at 85km/h outside, followed by rain and snow with low visibility. I couldn't find anything more interesting to do other than contributing to ClojureTO website. The goal today is to write a recursive article that explains how to contribute to this website by publishing itself.&lt;/p&gt;&lt;h3 id=&quot;pre-requisites&quot;&gt;Pre-requisites&lt;/h3&gt;&lt;p&gt;That's what I need to be able to contribute:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Git&lt;/strong&gt;: as a technical person, I have the habit of versioning the work I do. Git is the tool I use for that. This is also the tool needed to manage and publish the website.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;GitHub&lt;/strong&gt;: ClojureTO uses GitHub Pages as a hosting service. In short, when we push content to a repository it gets published on the website. To synchronize content with GitHub I need a GitHub account and Git.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Leiningen&lt;/strong&gt;: this is the portal to enter in the Clojure World. A Swiss knife to manage Clojure projects. I use it to tests the changes I make in the website. I was also used it to create the website in the first place.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Cryogen&lt;/strong&gt;: this tool, in combination with Leiningen, built this entire website. We explained how we did it in a &lt;a href='https://clojureto.github.io/posts-output/2019-02-23-website-behind'&gt;previews article&lt;/a&gt;. Now, I need it to produce the content, define the layout, the style, and the navigation.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Passion for Clojure&lt;/strong&gt;: to write such long and rich content, a good deal of time and knowledge is required. My passion for Clojure motivates me to do it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Community Driven&lt;/strong&gt;: a genuine intention to share knowledge and help others is also required.&lt;/li&gt;&lt;/ol&gt;&lt;h3 id=&quot;forking&amp;#95;the&amp;#95;repository&quot;&gt;Forking The Repository&lt;/h3&gt;&lt;p&gt;Not everybody is a good friend of a ClojureTO's co-organizer to claim push privileges. So, I need to start by forking &lt;a href='https://github.com/ClojureTO/clojureto-website'&gt;clojureto-website&lt;/a&gt;. I click on the &lt;strong&gt;Fork&lt;/strong&gt; button and get a new repository in my account. My contributions will remain there until it's time for a pull request.&lt;/p&gt;&lt;p&gt;&lt;img src=&quot;/img/fork-clojureto-website.png&quot; alt=&quot;Forking clojureto-website repository&quot; /&gt;&lt;/p&gt;&lt;p&gt;I clone the repository locally so I can start contributing:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;$ git clone https://github.com/htmfilho/clojureto-website.git&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&quot;cryogen&amp;#95;basics&quot;&gt;Cryogen Basics&lt;/h3&gt;&lt;p&gt;Understanding Cryogen is discovering ways of contributing. Its &lt;a href='http://cryogenweb.org'&gt;website&lt;/a&gt; covers all details. In summary, those with design skills could jump into &lt;code&gt;resources/templates/themes&lt;/code&gt; and redefine how the content is presented, improve navigation, readability, harmonize colors, shapes. I personally have no talent there, so I care more about content, which is located at &lt;code&gt;resources/templates/md&lt;/code&gt;. The one place that should not be touched at all is the folder &lt;code&gt;resources/public&lt;/code&gt;. Those files are replaced whenever the files in the previously mentioned folders are modified and saved.&lt;/p&gt;&lt;h3 id=&quot;writing&amp;#95;the&amp;#95;contribution&quot;&gt;Writing the Contribution&lt;/h3&gt;&lt;p&gt;I wish I could write the content in Clojure, but that's not practical. So, I stick to &lt;a href='https://daringfireball.net/projects/markdown/'&gt;Markdown&lt;/a&gt;, a format supported by Cryogen. Markdown eliminates the pain of writing content in HTML by offering a minimalist markup language for web authoring. All the content in Markdown, including this article, is located at &lt;code&gt;resources/templates/md&lt;/code&gt;. I can write &lt;strong&gt;pages&lt;/strong&gt;, which are more institutional, and &lt;strong&gt;posts&lt;/strong&gt;, which represent facts, perspectives, experiences, and discoveries.&lt;/p&gt;&lt;p&gt;Apart from Markdown, there is a caveat. At the top of a page or post, there is a Clojure-like map where we define values expected by the theme. For a page, there is something like this:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;{:title &amp;quot;About&amp;quot;
31+
&lt;p&gt;The wind is blowing at 85km/h outside, followed by rain and snow with low visibility. I couldn't find anything more interesting to do other than contributing to ClojureTO website. The goal today is to write a recursive article that explains how to contribute to this website by publishing itself.&lt;/p&gt;&lt;h3 id=&quot;pre-requisites&quot;&gt;Pre-requisites&lt;/h3&gt;&lt;p&gt;That's what I need to be able to contribute:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Git&lt;/strong&gt;: as a technical person, I have the habit of versioning the work I do. Git is the tool I use for that. This is also the tool needed to manage and publish the website.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;GitHub&lt;/strong&gt;: ClojureTO uses GitHub Pages as a hosting service. In short, when we push content to a repository it gets published on the website. To synchronize content with GitHub I need a GitHub account and Git.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Leiningen&lt;/strong&gt;: this is the portal to enter in the Clojure World. A Swiss knife to manage Clojure projects. I use it to tests the changes I make in the website. I was also used it to create the website in the first place.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Cryogen&lt;/strong&gt;: this tool, in combination with Leiningen, built this entire website. We explained how we did it in a &lt;a href='/posts/2019-02-23-website-behind'&gt;previews article&lt;/a&gt;. Now, I need it to produce the content, define the layout, the style, and the navigation.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Passion for Clojure&lt;/strong&gt;: to write such long and rich content, a good deal of time and knowledge is required. My passion for Clojure motivates me to do it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Community Driven&lt;/strong&gt;: a genuine intention to share knowledge and help others is also required.&lt;/li&gt;&lt;/ol&gt;&lt;h3 id=&quot;forking&amp;#95;the&amp;#95;repository&quot;&gt;Forking The Repository&lt;/h3&gt;&lt;p&gt;Not everybody is a good friend of a ClojureTO's co-organizer to claim push privileges. So, I need to start by forking &lt;a href='https://github.com/ClojureTO/clojureto-website'&gt;clojureto-website&lt;/a&gt;. I click on the &lt;strong&gt;Fork&lt;/strong&gt; button and get a new repository in my account. My contributions will remain there until it's time for a pull request.&lt;/p&gt;&lt;p&gt;&lt;img src=&quot;/img/fork-clojureto-website.png&quot; alt=&quot;Forking clojureto-website repository&quot; /&gt;&lt;/p&gt;&lt;p&gt;I clone the repository locally so I can start contributing:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;$ git clone https://github.com/htmfilho/clojureto-website.git&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&quot;cryogen&amp;#95;basics&quot;&gt;Cryogen Basics&lt;/h3&gt;&lt;p&gt;Understanding Cryogen is discovering ways of contributing. Its &lt;a href='http://cryogenweb.org'&gt;website&lt;/a&gt; covers all details. In summary, those with design skills could jump into &lt;code&gt;resources/templates/themes&lt;/code&gt; and redefine how the content is presented, improve navigation, readability, harmonize colors, shapes. I personally have no talent there, so I care more about content, which is located at &lt;code&gt;resources/templates/md&lt;/code&gt;. The one place that should not be touched at all is the folder &lt;code&gt;resources/public&lt;/code&gt;. Those files are replaced whenever the files in the previously mentioned folders are modified and saved.&lt;/p&gt;&lt;h3 id=&quot;writing&amp;#95;the&amp;#95;contribution&quot;&gt;Writing the Contribution&lt;/h3&gt;&lt;p&gt;I wish I could write the content in Clojure, but that's not practical. So, I stick to &lt;a href='https://daringfireball.net/projects/markdown/'&gt;Markdown&lt;/a&gt;, a format supported by Cryogen. Markdown eliminates the pain of writing content in HTML by offering a minimalist markup language for web authoring. All the content in Markdown, including this article, is located at &lt;code&gt;resources/templates/md&lt;/code&gt;. I can write &lt;strong&gt;pages&lt;/strong&gt;, which are more institutional, and &lt;strong&gt;posts&lt;/strong&gt;, which represent facts, perspectives, experiences, and discoveries.&lt;/p&gt;&lt;p&gt;Apart from Markdown, there is a caveat. At the top of a page or post, there is a Clojure-like map where we define values expected by the theme. For a page, there is something like this:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;{:title &amp;quot;About&amp;quot;
3232
:layout :page
3333
:page-index 0
3434
:navbar? true}&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;I would emphasize &lt;code&gt;:page-index&lt;/code&gt;, which defines the order the page appears in the navigation, and &lt;code&gt;:navbar?&lt;/code&gt; to include the page in the top menu. For this post in particular, I used this:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;{:title &amp;quot;How to Contribute to ClojureTO Website&amp;quot;

0 commit comments

Comments
 (0)