diff --git a/aftershocks-the-palladium-wars-1-fr.html b/aftershocks-the-palladium-wars-1-fr.html new file mode 100644 index 0000000..13cf61f --- /dev/null +++ b/aftershocks-the-palladium-wars-1-fr.html @@ -0,0 +1,61 @@ + + + + + + + Aftershocks (The Palladium Wars #1) + + + + + + + +
+
+
+

+ Aftershocks (The Palladium Wars #1)

+
+ +
+

Book cover of Aftershocks +Write something about the book.

+ +
+ +
+
+ + + + + + + \ No newline at end of file diff --git a/archives.html b/archives.html new file mode 100644 index 0000000..13d38b7 --- /dev/null +++ b/archives.html @@ -0,0 +1,48 @@ + + + + + + + Blog like it's 2002 + + + + + + +
+

Archives for Blog like it's 2002

+ +
+
25-02-2024
+
Aftershocks (The Palladium Wars #1)
+
23-02-2024
+
Setting up a blog with Pelican
+
22-02-2024
+
My learning path
+
24-01-2024
+
The end of Ingenuity
+
+
+ + + + + + + \ No newline at end of file diff --git a/author/fabien.html b/author/fabien.html new file mode 100644 index 0000000..4d3d848 --- /dev/null +++ b/author/fabien.html @@ -0,0 +1,130 @@ + + + + + + + Blog like it's 2002 - Fabien + + + + + + + + +
+

Other articles

+
+
    + +
  1. +
    +

    Setting up a blog with Pelican

    +
    + +
    +

    I will explain here the complete steps to build your static website with Pelican and deploy it on GitHub Pages.

    +

    But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?

    +

    I was looking for:

    +
      +
    • simplicity: Pelican uses markdown syntax in plain text …
    + read more +
    +
  2. + +
  3. +
    +

    My learning path

    +
    + +
    +

    I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!

    +

    It's available here.

    + read more +
    +
  4. + +
  5. +
    +

    The end of Ingenuity

    +
    + +
    +

    NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.

    +

    So one of the main exploration devices of the mission is broken, 225 million km away from Earth. There is of course no …

    + read more +
    +
  6. +
+
+ + + + + + + \ No newline at end of file diff --git a/authors.html b/authors.html new file mode 100644 index 0000000..51f3472 --- /dev/null +++ b/authors.html @@ -0,0 +1,42 @@ + + + + + + + Blog like it's 2002 - Authors + + + + + + + +
+

Authors on Blog like it's 2002

+ +
+ + + + + + + + \ No newline at end of file diff --git a/categories.html b/categories.html new file mode 100644 index 0000000..f7b8126 --- /dev/null +++ b/categories.html @@ -0,0 +1,43 @@ + + + + + + + Blog like it's 2002 - Categories + + + + + + + +
+

Categories for Blog like it's 2002

+ +
+ + + + + + + + \ No newline at end of file diff --git a/category/books.html b/category/books.html new file mode 100644 index 0000000..de5619c --- /dev/null +++ b/category/books.html @@ -0,0 +1,52 @@ + + + + + + + Blog like it's 2002 - Books + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/category/tech.html b/category/tech.html new file mode 100644 index 0000000..a0df60a --- /dev/null +++ b/category/tech.html @@ -0,0 +1,197 @@ + + + + + + + Blog like it's 2002 - Tech + + + + + + + + +
+

Other articles

+
+
    + +
  1. +
    +

    My learning path

    +
    + +
    +

    I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!

    +

    It's available here.

    + read more +
    +
  2. + +
  3. +
    +

    The end of Ingenuity

    +
    + +
    +

    NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.

    +

    So one of the main exploration devices of the mission is broken, 225 million km away from Earth. There is of course no …

    + read more +
    +
  4. +
+
+ + + + + + + \ No newline at end of file diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml new file mode 100644 index 0000000..4ae597a --- /dev/null +++ b/feeds/all.atom.xml @@ -0,0 +1,126 @@ + +Blog like it's 2002https://frica.github.io/blog/2024-02-25T15:00:00+01:00Tech and stuffAftershocks (The Palladium Wars #1)2024-02-25T15:00:00+01:002024-02-25T15:00:00+01:00Fabientag:frica.github.io,2024-02-25:/blog/aftershocks-the-palladium-wars-1-fr.html<p><img src="https://images-na.ssl-images-amazon.com/images/S/compressed.photo.goodreads.com/books/1548541838i/41211815.jpg" alt="Book cover of Aftershocks" width="150" height="auto"> +Write something about the book. </p> +<!-- ![Book cover of Aftershocks](https://images-na.ssl-images-amazon.com/images/S/compressed.photo.goodreads.com/books/1548541838i/41211815.jpg) -->Setting up a blog with Pelican2024-02-23T10:47:00+01:002024-02-23T10:47:00+01:00Fabientag:frica.github.io,2024-02-23:/blog/setting-up-a-blog-with-pelican.html<p>I will explain here the complete steps to build your static website with <a href="https://getpelican.com/">Pelican</a> and deploy it on GitHub Pages.</p> +<p>But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?</p> +<p>I was looking for:</p> +<ul> +<li>simplicity: Pelican uses markdown syntax in plain text …</li></ul><p>I will explain here the complete steps to build your static website with <a href="https://getpelican.com/">Pelican</a> and deploy it on GitHub Pages.</p> +<p>But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?</p> +<p>I was looking for:</p> +<ul> +<li>simplicity: Pelican uses markdown syntax in plain text files, site structure generated is simple and stylish enough</li> +<li>ease of deployment: generating html from the markdown files is done by Pelican</li> +<li>free solution: it can be hosted on GitHub pages, so it's perfect</li> +</ul> +<h2>Installation</h2> +<p>I used Ubuntu WSL on Windows because I had it setup from a Docker course that I followed recently and I quite liked it.</p> +<p>So in the Terminal, type</p> +<div class="highlight"><pre><span></span><code>sudo apt install python3 +sudo apt install pelican +sudo apt install pip +</code></pre></div> + +<h2>Create a project</h2> +<p>Go where you want to create your blog:</p> +<div class="highlight"><pre><span></span><code>mkdir blog +cd blog +pelican-quickstart +</code></pre></div> + +<p>Leave the default values in the quickstart.</p> +<p>Create a file and write a dummy post:</p> +<div class="highlight"><pre><span></span><code>Title: My First Review +Date: 2024-02-23 10:20 +Category: Test + +This is a test. +</code></pre></div> + +<p>Save it under blog/content.</p> +<p>Then run:</p> +<div class="highlight"><pre><span></span><code>pelican content +</code></pre></div> + +<p>Your site has now been generated inside the output/ directory.</p> +<p>If you want to look at your generated site, run:</p> +<div class="highlight"><pre><span></span><code>pelican -l +</code></pre></div> + +<h2>Hosting</h2> +<p>In case you have a GitHub account, you can use the GitHub pages to host the generated website.</p> +<p>Make sure you are in your blog directory and initialize the git repo:</p> +<div class="highlight"><pre><span></span><code>git init +</code></pre></div> + +<p>Commit all your files locally (except the files not needed for the git repo):</p> +<div class="highlight"><pre><span></span><code>echo &quot;output/&quot; &gt;&gt; .gitignore +echo &quot;__pycache__/&quot; &gt;&gt; .gitignore +git add -all +git commit -m &quot;Initialize blog&quot; +</code></pre></div> + +<p><strong>Note:</strong>: the -A adds all unstaged files to the repo.</p> +<p>Setup your GitHub pages locally:</p> +<div class="highlight"><pre><span></span><code><span class="n">pip</span> <span class="n">install</span> <span class="n">ghp</span><span class="o">-</span><span class="kn">import</span> +<span class="nn">ghp</span><span class="o">-</span><span class="kn">import</span> <span class="nn">.</span><span class="o">/</span><span class="n">output</span> <span class="o">-</span><span class="n">m</span> <span class="s2">&quot;Initial upload&quot;</span> +</code></pre></div> + +<p><strong>Note:</strong> ghp-import will itself create your gh-pages branch and a new commit in it.</p> +<p>Go to you GitHub account and create an empty git repository with these properties:</p> +<div class="highlight"><pre><span></span><code><span class="n">Name</span><span class="o">:</span><span class="w"> </span><span class="n">Same</span><span class="w"> </span><span class="k">as</span><span class="w"> </span><span class="n">your</span><span class="w"> </span><span class="n">local</span><span class="w"> </span><span class="n">blog</span><span class="w"> </span><span class="n">directory</span><span class="o">;</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="n">my</span><span class="w"> </span><span class="k">case</span><span class="o">:</span><span class="w"> </span><span class="n">blog</span> +<span class="n">Description</span><span class="o">:</span><span class="w"> </span><span class="n">My</span><span class="w"> </span><span class="n">blog</span> +<span class="n">Gitignore</span><span class="o">:</span><span class="w"> </span><span class="n">None</span><span class="o">;</span> +<span class="n">Licence</span><span class="o">:</span><span class="w"> </span><span class="n">None</span><span class="o">;</span> +<span class="n">Initialize</span><span class="w"> </span><span class="k">with</span><span class="w"> </span><span class="n">README</span><span class="o">:</span><span class="w"> </span><span class="n">No</span> +</code></pre></div> + +<p>Set git remote</p> +<div class="highlight"><pre><span></span><code><span class="n">git</span><span class="w"> </span><span class="n">remote</span><span class="w"> </span><span class="k">add</span><span class="w"> </span><span class="n">origin</span><span class="w"> </span><span class="n">git</span><span class="nv">@github</span><span class="p">.</span><span class="nl">com</span><span class="p">:</span><span class="o">&lt;</span><span class="n">username</span><span class="o">&gt;/</span><span class="n">blog</span><span class="p">.</span><span class="n">git</span> +</code></pre></div> + +<p>Push your gh-pages to GitHub</p> +<div class="highlight"><pre><span></span><code>git checkout gh-pages +git push origin gh-pages +</code></pre></div> + +<p><strong>Note:</strong> +Normally, gh-pages should be set as your default branches now on GitHub.</p> +<p>Wait a few seconds and check your blog on:</p> +<div class="highlight"><pre><span></span><code>https://username.github.io/blog/ +</code></pre></div> + +<p><strong>Warning:</strong> GitHub pages have of course limitations in site size and bandwith but that's good enough for me to write my articles and include some pictures.</p> +<hr> +<p><strong>Optional:</strong></p> +<p>If you want to push your content and not only the generated site on GitHub, run:</p> +<div class="highlight"><pre><span></span><code>git add -A +git commit -m &quot;Initialize blog content&quot; +git push origin master +</code></pre></div> + +<hr> +<p>That's all folks!</p>My learning path2024-02-22T15:00:00+01:002024-02-22T15:00:00+01:00Fabientag:frica.github.io,2024-02-22:/blog/my-learning-path.html<p>I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!</p> +<p>It's available <a href="https://github.com/frica/learning-path/">here</a>.</p>The end of Ingenuity2024-01-24T10:00:00+01:002024-01-24T10:00:00+01:00Fabientag:frica.github.io,2024-01-24:/blog/the-end-of-ingenuity.html<p>NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.</p> +<p>So one of the main exploration devices of the mission is broken, <strong>225 million km away from Earth</strong>. There is of course no …</p><p>NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.</p> +<p>So one of the main exploration devices of the mission is broken, <strong>225 million km away from Earth</strong>. There is of course no way to repair it. Is that an engineering failure, in multi-billion dollar scientific expedition?</p> +<p>Not at all.</p> +<ul> +<li>The device was expected to be a technical demonstration and do 5 flights. It did <strong>72</strong>.</li> +</ul> +<p>➡️ NASA over-engineered the helicopter so it ended up lasting way longer than the mission specs. Carrying on the tradition from Voyager and other probes, NASA JPL engineers did not go for the bare minimum.</p> +<ul> +<li>The incident was disclosed openly on Jan 25th, after the damage was confirmed on Jan 19 after a test flight on the 18th.</li> +</ul> +<p>➡️ NASA is not hiding the issue. NASA is proud of the work achieved and is busy working on the root cause analysis, sharing as much as they know. Even the failure itself is actually a great science result.</p> +<ul> +<li>This actually proved the helicopter to be a standard method for exploring Mars.</li> +</ul> +<p>➡️ May be the case only on Mars (and Titan) but that's already a great confirmation of a badass concept. The science return we're going to get from it will be truly amazing.</p> +<p>NASA's engineering teams truly represent what we should love about technology ❤️</p> +<hr> +<p>Sources:</p> +<ul> +<li><a href="https://www.nasa.gov/news-release/after-three-years-on-mars-nasas-ingenuity-helicopter-mission-ends/">NASA announcement</a></li> +<li><a href="https://www.youtube.com/watch?v=hW5akI5Rnyg">Administrator Bill Nelson announces the end of Ingenuity Mars Helicopter</a></li> +</ul> \ No newline at end of file diff --git a/feeds/books.atom.xml b/feeds/books.atom.xml new file mode 100644 index 0000000..ec504d9 --- /dev/null +++ b/feeds/books.atom.xml @@ -0,0 +1,4 @@ + +Blog like it's 2002 - Bookshttps://frica.github.io/blog/2024-02-25T15:00:00+01:00Tech and stuffAftershocks (The Palladium Wars #1)2024-02-25T15:00:00+01:002024-02-25T15:00:00+01:00Fabientag:frica.github.io,2024-02-25:/blog/aftershocks-the-palladium-wars-1-fr.html<p><img src="https://images-na.ssl-images-amazon.com/images/S/compressed.photo.goodreads.com/books/1548541838i/41211815.jpg" alt="Book cover of Aftershocks" width="150" height="auto"> +Write something about the book. </p> +<!-- ![Book cover of Aftershocks](https://images-na.ssl-images-amazon.com/images/S/compressed.photo.goodreads.com/books/1548541838i/41211815.jpg) --> \ No newline at end of file diff --git a/feeds/tech.atom.xml b/feeds/tech.atom.xml new file mode 100644 index 0000000..5c1462c --- /dev/null +++ b/feeds/tech.atom.xml @@ -0,0 +1,124 @@ + +Blog like it's 2002 - Techhttps://frica.github.io/blog/2024-02-23T10:47:00+01:00Tech and stuffSetting up a blog with Pelican2024-02-23T10:47:00+01:002024-02-23T10:47:00+01:00Fabientag:frica.github.io,2024-02-23:/blog/setting-up-a-blog-with-pelican.html<p>I will explain here the complete steps to build your static website with <a href="https://getpelican.com/">Pelican</a> and deploy it on GitHub Pages.</p> +<p>But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?</p> +<p>I was looking for:</p> +<ul> +<li>simplicity: Pelican uses markdown syntax in plain text …</li></ul><p>I will explain here the complete steps to build your static website with <a href="https://getpelican.com/">Pelican</a> and deploy it on GitHub Pages.</p> +<p>But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?</p> +<p>I was looking for:</p> +<ul> +<li>simplicity: Pelican uses markdown syntax in plain text files, site structure generated is simple and stylish enough</li> +<li>ease of deployment: generating html from the markdown files is done by Pelican</li> +<li>free solution: it can be hosted on GitHub pages, so it's perfect</li> +</ul> +<h2>Installation</h2> +<p>I used Ubuntu WSL on Windows because I had it setup from a Docker course that I followed recently and I quite liked it.</p> +<p>So in the Terminal, type</p> +<div class="highlight"><pre><span></span><code>sudo apt install python3 +sudo apt install pelican +sudo apt install pip +</code></pre></div> + +<h2>Create a project</h2> +<p>Go where you want to create your blog:</p> +<div class="highlight"><pre><span></span><code>mkdir blog +cd blog +pelican-quickstart +</code></pre></div> + +<p>Leave the default values in the quickstart.</p> +<p>Create a file and write a dummy post:</p> +<div class="highlight"><pre><span></span><code>Title: My First Review +Date: 2024-02-23 10:20 +Category: Test + +This is a test. +</code></pre></div> + +<p>Save it under blog/content.</p> +<p>Then run:</p> +<div class="highlight"><pre><span></span><code>pelican content +</code></pre></div> + +<p>Your site has now been generated inside the output/ directory.</p> +<p>If you want to look at your generated site, run:</p> +<div class="highlight"><pre><span></span><code>pelican -l +</code></pre></div> + +<h2>Hosting</h2> +<p>In case you have a GitHub account, you can use the GitHub pages to host the generated website.</p> +<p>Make sure you are in your blog directory and initialize the git repo:</p> +<div class="highlight"><pre><span></span><code>git init +</code></pre></div> + +<p>Commit all your files locally (except the files not needed for the git repo):</p> +<div class="highlight"><pre><span></span><code>echo &quot;output/&quot; &gt;&gt; .gitignore +echo &quot;__pycache__/&quot; &gt;&gt; .gitignore +git add -all +git commit -m &quot;Initialize blog&quot; +</code></pre></div> + +<p><strong>Note:</strong>: the -A adds all unstaged files to the repo.</p> +<p>Setup your GitHub pages locally:</p> +<div class="highlight"><pre><span></span><code><span class="n">pip</span> <span class="n">install</span> <span class="n">ghp</span><span class="o">-</span><span class="kn">import</span> +<span class="nn">ghp</span><span class="o">-</span><span class="kn">import</span> <span class="nn">.</span><span class="o">/</span><span class="n">output</span> <span class="o">-</span><span class="n">m</span> <span class="s2">&quot;Initial upload&quot;</span> +</code></pre></div> + +<p><strong>Note:</strong> ghp-import will itself create your gh-pages branch and a new commit in it.</p> +<p>Go to you GitHub account and create an empty git repository with these properties:</p> +<div class="highlight"><pre><span></span><code><span class="n">Name</span><span class="o">:</span><span class="w"> </span><span class="n">Same</span><span class="w"> </span><span class="k">as</span><span class="w"> </span><span class="n">your</span><span class="w"> </span><span class="n">local</span><span class="w"> </span><span class="n">blog</span><span class="w"> </span><span class="n">directory</span><span class="o">;</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="n">my</span><span class="w"> </span><span class="k">case</span><span class="o">:</span><span class="w"> </span><span class="n">blog</span> +<span class="n">Description</span><span class="o">:</span><span class="w"> </span><span class="n">My</span><span class="w"> </span><span class="n">blog</span> +<span class="n">Gitignore</span><span class="o">:</span><span class="w"> </span><span class="n">None</span><span class="o">;</span> +<span class="n">Licence</span><span class="o">:</span><span class="w"> </span><span class="n">None</span><span class="o">;</span> +<span class="n">Initialize</span><span class="w"> </span><span class="k">with</span><span class="w"> </span><span class="n">README</span><span class="o">:</span><span class="w"> </span><span class="n">No</span> +</code></pre></div> + +<p>Set git remote</p> +<div class="highlight"><pre><span></span><code><span class="n">git</span><span class="w"> </span><span class="n">remote</span><span class="w"> </span><span class="k">add</span><span class="w"> </span><span class="n">origin</span><span class="w"> </span><span class="n">git</span><span class="nv">@github</span><span class="p">.</span><span class="nl">com</span><span class="p">:</span><span class="o">&lt;</span><span class="n">username</span><span class="o">&gt;/</span><span class="n">blog</span><span class="p">.</span><span class="n">git</span> +</code></pre></div> + +<p>Push your gh-pages to GitHub</p> +<div class="highlight"><pre><span></span><code>git checkout gh-pages +git push origin gh-pages +</code></pre></div> + +<p><strong>Note:</strong> +Normally, gh-pages should be set as your default branches now on GitHub.</p> +<p>Wait a few seconds and check your blog on:</p> +<div class="highlight"><pre><span></span><code>https://username.github.io/blog/ +</code></pre></div> + +<p><strong>Warning:</strong> GitHub pages have of course limitations in site size and bandwith but that's good enough for me to write my articles and include some pictures.</p> +<hr> +<p><strong>Optional:</strong></p> +<p>If you want to push your content and not only the generated site on GitHub, run:</p> +<div class="highlight"><pre><span></span><code>git add -A +git commit -m &quot;Initialize blog content&quot; +git push origin master +</code></pre></div> + +<hr> +<p>That's all folks!</p>My learning path2024-02-22T15:00:00+01:002024-02-22T15:00:00+01:00Fabientag:frica.github.io,2024-02-22:/blog/my-learning-path.html<p>I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!</p> +<p>It's available <a href="https://github.com/frica/learning-path/">here</a>.</p>The end of Ingenuity2024-01-24T10:00:00+01:002024-01-24T10:00:00+01:00Fabientag:frica.github.io,2024-01-24:/blog/the-end-of-ingenuity.html<p>NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.</p> +<p>So one of the main exploration devices of the mission is broken, <strong>225 million km away from Earth</strong>. There is of course no …</p><p>NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.</p> +<p>So one of the main exploration devices of the mission is broken, <strong>225 million km away from Earth</strong>. There is of course no way to repair it. Is that an engineering failure, in multi-billion dollar scientific expedition?</p> +<p>Not at all.</p> +<ul> +<li>The device was expected to be a technical demonstration and do 5 flights. It did <strong>72</strong>.</li> +</ul> +<p>➡️ NASA over-engineered the helicopter so it ended up lasting way longer than the mission specs. Carrying on the tradition from Voyager and other probes, NASA JPL engineers did not go for the bare minimum.</p> +<ul> +<li>The incident was disclosed openly on Jan 25th, after the damage was confirmed on Jan 19 after a test flight on the 18th.</li> +</ul> +<p>➡️ NASA is not hiding the issue. NASA is proud of the work achieved and is busy working on the root cause analysis, sharing as much as they know. Even the failure itself is actually a great science result.</p> +<ul> +<li>This actually proved the helicopter to be a standard method for exploring Mars.</li> +</ul> +<p>➡️ May be the case only on Mars (and Titan) but that's already a great confirmation of a badass concept. The science return we're going to get from it will be truly amazing.</p> +<p>NASA's engineering teams truly represent what we should love about technology ❤️</p> +<hr> +<p>Sources:</p> +<ul> +<li><a href="https://www.nasa.gov/news-release/after-three-years-on-mars-nasas-ingenuity-helicopter-mission-ends/">NASA announcement</a></li> +<li><a href="https://www.youtube.com/watch?v=hW5akI5Rnyg">Administrator Bill Nelson announces the end of Ingenuity Mars Helicopter</a></li> +</ul> \ No newline at end of file diff --git a/images/test.jpg b/images/test.jpg new file mode 100644 index 0000000..8af4226 Binary files /dev/null and b/images/test.jpg differ diff --git a/index.html b/index.html new file mode 100644 index 0000000..908e05a --- /dev/null +++ b/index.html @@ -0,0 +1,130 @@ + + + + + + + Blog like it's 2002 + + + + + + + + +
+

Other articles

+
+
    + +
  1. +
    +

    Setting up a blog with Pelican

    +
    + +
    +

    I will explain here the complete steps to build your static website with Pelican and deploy it on GitHub Pages.

    +

    But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?

    +

    I was looking for:

    +
      +
    • simplicity: Pelican uses markdown syntax in plain text …
    + read more +
    +
  2. + +
  3. +
    +

    My learning path

    +
    + +
    +

    I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!

    +

    It's available here.

    + read more +
    +
  4. + +
  5. +
    +

    The end of Ingenuity

    +
    + +
    +

    NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.

    +

    So one of the main exploration devices of the mission is broken, 225 million km away from Earth. There is of course no …

    + read more +
    +
  6. +
+
+ + + + + + + \ No newline at end of file diff --git a/my-learning-path.html b/my-learning-path.html new file mode 100644 index 0000000..53d8164 --- /dev/null +++ b/my-learning-path.html @@ -0,0 +1,60 @@ + + + + + + + My learning path + + + + + + + +
+
+
+

+ My learning path

+
+ +
+

I compiled a list of the online trainings, followed or to follow, free or not. Impressive what the Internet has to offer!

+

It's available here.

+
+ +
+
+ + + + + + + \ No newline at end of file diff --git a/pages/about.html b/pages/about.html new file mode 100644 index 0000000..0aa8033 --- /dev/null +++ b/pages/about.html @@ -0,0 +1,42 @@ + + + + + + + About + + + + + + +
+

About

+ +

Thank you for visiting. Welcome!

+

+ Linkedin
+ GitHub

+
+ + + + + + + \ No newline at end of file diff --git a/pages/assets/github.png b/pages/assets/github.png new file mode 100644 index 0000000..6cb3b70 Binary files /dev/null and b/pages/assets/github.png differ diff --git a/pages/assets/linkedin.png b/pages/assets/linkedin.png new file mode 100644 index 0000000..8bc2d53 Binary files /dev/null and b/pages/assets/linkedin.png differ diff --git a/setting-up-a-blog-with-pelican.html b/setting-up-a-blog-with-pelican.html new file mode 100644 index 0000000..3ed6b4f --- /dev/null +++ b/setting-up-a-blog-with-pelican.html @@ -0,0 +1,154 @@ + + + + + + + Setting up a blog with Pelican + + + + + + + +
+
+
+

+ Setting up a blog with Pelican

+
+ +
+

I will explain here the complete steps to build your static website with Pelican and deploy it on GitHub Pages.

+

But first, why use Pelican and not Wordpress or Dotclear, like back when I started my first blog?

+

I was looking for:

+
    +
  • simplicity: Pelican uses markdown syntax in plain text files, site structure generated is simple and stylish enough
  • +
  • ease of deployment: generating html from the markdown files is done by Pelican
  • +
  • free solution: it can be hosted on GitHub pages, so it's perfect
  • +
+

Installation

+

I used Ubuntu WSL on Windows because I had it setup from a Docker course that I followed recently and I quite liked it.

+

So in the Terminal, type

+
sudo apt install python3
+sudo apt install pelican 
+sudo apt install pip
+
+ +

Create a project

+

Go where you want to create your blog:

+
mkdir blog
+cd blog
+pelican-quickstart
+
+ +

Leave the default values in the quickstart.

+

Create a file and write a dummy post:

+
Title: My First Review
+Date: 2024-02-23 10:20
+Category: Test
+
+This is a test.
+
+ +

Save it under blog/content.

+

Then run:

+
pelican content
+
+ +

Your site has now been generated inside the output/ directory.

+

If you want to look at your generated site, run:

+
pelican -l
+
+ +

Hosting

+

In case you have a GitHub account, you can use the GitHub pages to host the generated website.

+

Make sure you are in your blog directory and initialize the git repo:

+
git init
+
+ +

Commit all your files locally (except the files not needed for the git repo):

+
echo "output/" >> .gitignore
+echo "__pycache__/" >> .gitignore
+git add -all
+git commit -m "Initialize blog"
+
+ +

Note:: the -A adds all unstaged files to the repo.

+

Setup your GitHub pages locally:

+
pip install ghp-import
+ghp-import ./output -m "Initial upload"
+
+ +

Note: ghp-import will itself create your gh-pages branch and a new commit in it.

+

Go to you GitHub account and create an empty git repository with these properties:

+
Name: Same as your local blog directory; in my case: blog
+Description: My blog
+Gitignore: None;
+Licence: None;
+Initialize with README: No
+
+ +

Set git remote

+
git remote add origin git@github.com:<username>/blog.git
+
+ +

Push your gh-pages to GitHub

+
git checkout gh-pages
+git push origin gh-pages
+
+ +

Note: +Normally, gh-pages should be set as your default branches now on GitHub.

+

Wait a few seconds and check your blog on:

+
https://username.github.io/blog/
+
+ +

Warning: GitHub pages have of course limitations in site size and bandwith but that's good enough for me to write my articles and include some pictures.

+
+

Optional:

+

If you want to push your content and not only the generated site on GitHub, run:

+
git add -A
+git commit -m "Initialize blog content"
+git push origin master
+
+ +
+

That's all folks!

+
+ +
+
+ + + + + + + \ No newline at end of file diff --git a/tag/github.html b/tag/github.html new file mode 100644 index 0000000..cedd3a2 --- /dev/null +++ b/tag/github.html @@ -0,0 +1,145 @@ + + + + + + + Blog like it's 2002 - github + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/ingenuity.html b/tag/ingenuity.html new file mode 100644 index 0000000..061277e --- /dev/null +++ b/tag/ingenuity.html @@ -0,0 +1,71 @@ + + + + + + + Blog like it's 2002 - ingenuity + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/learning.html b/tag/learning.html new file mode 100644 index 0000000..12673c8 --- /dev/null +++ b/tag/learning.html @@ -0,0 +1,51 @@ + + + + + + + Blog like it's 2002 - learning + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/pelican.html b/tag/pelican.html new file mode 100644 index 0000000..93cbf88 --- /dev/null +++ b/tag/pelican.html @@ -0,0 +1,145 @@ + + + + + + + Blog like it's 2002 - pelican + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/reading.html b/tag/reading.html new file mode 100644 index 0000000..be46222 --- /dev/null +++ b/tag/reading.html @@ -0,0 +1,52 @@ + + + + + + + Blog like it's 2002 - reading + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/scifi.html b/tag/scifi.html new file mode 100644 index 0000000..5838b7f --- /dev/null +++ b/tag/scifi.html @@ -0,0 +1,52 @@ + + + + + + + Blog like it's 2002 - scifi + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tag/space.html b/tag/space.html new file mode 100644 index 0000000..ca70bd6 --- /dev/null +++ b/tag/space.html @@ -0,0 +1,71 @@ + + + + + + + Blog like it's 2002 - space + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/tags.html b/tags.html new file mode 100644 index 0000000..3410a42 --- /dev/null +++ b/tags.html @@ -0,0 +1,48 @@ + + + + + + + Blog like it's 2002 - Tags + + + + + + + +
+

Tags for Blog like it's 2002

+ +
+ + + + + + + + \ No newline at end of file diff --git a/the-end-of-ingenuity.html b/the-end-of-ingenuity.html new file mode 100644 index 0000000..3f9e4a7 --- /dev/null +++ b/the-end-of-ingenuity.html @@ -0,0 +1,80 @@ + + + + + + + The end of Ingenuity + + + + + + + +
+
+
+

+ The end of Ingenuity

+
+ +
+

NASA's Ingenuity Helicopter won't fly on Mars anymore... The helicopter itself captured this color image showing the shadow of a rotor blade damaged during a rough landing.

+

So one of the main exploration devices of the mission is broken, 225 million km away from Earth. There is of course no way to repair it. Is that an engineering failure, in multi-billion dollar scientific expedition?

+

Not at all.

+
    +
  • The device was expected to be a technical demonstration and do 5 flights. It did 72.
  • +
+

➡️ NASA over-engineered the helicopter so it ended up lasting way longer than the mission specs. Carrying on the tradition from Voyager and other probes, NASA JPL engineers did not go for the bare minimum.

+
    +
  • The incident was disclosed openly on Jan 25th, after the damage was confirmed on Jan 19 after a test flight on the 18th.
  • +
+

➡️ NASA is not hiding the issue. NASA is proud of the work achieved and is busy working on the root cause analysis, sharing as much as they know. Even the failure itself is actually a great science result.

+
    +
  • This actually proved the helicopter to be a standard method for exploring Mars.
  • +
+

➡️ May be the case only on Mars (and Titan) but that's already a great confirmation of a badass concept. The science return we're going to get from it will be truly amazing.

+

NASA's engineering teams truly represent what we should love about technology ❤️

+
+

Sources:

+ +
+ +
+
+ + + + + + + \ No newline at end of file diff --git a/theme/css/fonts.css b/theme/css/fonts.css new file mode 100644 index 0000000..5601507 --- /dev/null +++ b/theme/css/fonts.css @@ -0,0 +1,12 @@ +@font-face { + font-family: 'Yanone Kaffeesatz'; + font-style: normal; + font-weight: 400; + src: + local('Yanone Kaffeesatz Regular'), + local('YanoneKaffeesatz-Regular'), + /* from https://fonts.gstatic.com/s/yanonekaffeesatz/v8/YDAoLskQQ5MOAgvHUQCcLRTHiN2BPBirwIkMLKUspj4.woff */ + url('../fonts/Yanone_Kaffeesatz_400.woff') format('woff'), + /* from https://fonts.gstatic.com/s/yanonekaffeesatz/v8/YDAoLskQQ5MOAgvHUQCcLfGwxTS8d1Q9KiDNCMKLFUM.woff2 */ + url('../fonts/Yanone_Kaffeesatz_400.woff2') format('woff2'); +} diff --git a/theme/css/main.css b/theme/css/main.css new file mode 100644 index 0000000..49de03d --- /dev/null +++ b/theme/css/main.css @@ -0,0 +1,439 @@ +/* + Name: Smashing HTML5 + Date: July 2009 + Description: Sample layout for HTML5 and CSS3 goodness. + Version: 1.0 + License: MIT + Licensed by: Smashing Media GmbH + Original author: Enrique Ramírez +*/ + +/* Imports */ +@import url("reset.css"); +@import url("pygment.css"); +@import url("typogrify.css"); +@import url("fonts.css"); + +/***** Global *****/ +/* Body */ +body { + background: #F5F4EF; + color: #000305; + font-size: 87.5%; /* Base font size: 14px */ + font-family: 'Trebuchet MS', Trebuchet, 'Lucida Sans Unicode', 'Lucida Grande', 'Lucida Sans', Arial, sans-serif; + line-height: 1.429; + margin: 0; + padding: 0; + text-align: left; +} + +/* Headings */ +h1 {font-size: 2em } +h2 {font-size: 1.571em} /* 22px */ +h3 {font-size: 1.429em} /* 20px */ +h4 {font-size: 1.286em} /* 18px */ +h5 {font-size: 1.143em} /* 16px */ +h6 {font-size: 1em} /* 14px */ + +h1, h2, h3, h4, h5, h6 { + font-weight: 400; + line-height: 1.1; + margin-bottom: .8em; + font-family: 'Yanone Kaffeesatz', arial, serif; +} + +h3, h4, h5, h6 { margin-top: .8em; } + +hr { border: 2px solid #EEEEEE; } + +/* Anchors */ +a {outline: 0;} +a img {border: 0px; text-decoration: none;} +a:link, a:visited { + color: #C74350; + padding: 0 1px; + text-decoration: underline; +} +a:hover, a:active { + background-color: #C74350; + color: #fff; + text-decoration: none; + text-shadow: 1px 1px 1px #333; +} + +h1 a:hover { + background-color: inherit +} + +/* Paragraphs */ +div.line-block, +p { margin-top: 1em; + margin-bottom: 1em;} + +strong, b {font-weight: bold;} +em, i {font-style: italic;} + +/* Lists */ +ul { + list-style: outside disc; + margin: 0em 0 0 1.5em; +} + +ol { + list-style: outside decimal; + margin: 0em 0 0 1.5em; +} + +li { margin-top: 0.5em; + margin-bottom: 1em; } + +.post-info { + float:right; + margin:10px; + padding:5px; +} + +.post-info p{ + margin-top: 1px; + margin-bottom: 1px; +} + +.readmore { float: right } + +dl {margin: 0 0 1.5em 0;} +dt {font-weight: bold;} +dd {margin-left: 1.5em;} + +pre{background-color: rgb(238, 238, 238); padding: 10px; margin: 10px; overflow: auto;} + +/* Quotes */ +blockquote { + margin: 20px; + font-style: italic; +} +cite {} + +q {} + +div.note { + float: right; + margin: 5px; + font-size: 85%; + max-width: 300px; +} + +/* Tables */ +table {margin: .5em auto 1.5em auto; width: 98%;} + + /* Thead */ + thead th {padding: .5em .4em; text-align: left;} + thead td {} + + /* Tbody */ + tbody td {padding: .5em .4em;} + tbody th {} + + tbody .alt td {} + tbody .alt th {} + + /* Tfoot */ + tfoot th {} + tfoot td {} + +/* HTML5 tags */ +header, section, footer, +aside, nav, article, figure { + display: block; +} + +/***** Layout *****/ +.body {clear: both; margin: 0 auto; max-width: 800px;} +img { max-width: 100%; } +img.right, figure.right, div.figure.align-right { + float: right; + margin: 0 0 2em 2em; +} +img.left, figure.left, div.figure.align-left { + float: left; + margin: 0 2em 2em 0; +} + +/* .rst support */ +div.figure img, figure img { /* to fill figure exactly */ + max-width: 100%; +} +div.figure p.caption, figure p.caption { /* margin provided by figure */ + margin-top: 0; + margin-bottom: 0; +} + +/* + Header +*****************/ +#banner { + margin: 0 auto; + padding: 0.8em 0 0 0; +} + + /* Banner */ + #banner h1 { + font-size: 3.571em; + line-height: 1.0; + margin-bottom: .3em; + } + + #banner h1 a:link, #banner h1 a:visited { + color: #000305; + display: block; + font-weight: bold; + margin: 0 0 0 .2em; + text-decoration: none; + } + #banner h1 a:hover, #banner h1 a:active { + background: none; + color: #C74350; + text-shadow: none; + } + + #banner h1 strong {font-size: 0.36em; font-weight: normal;} + + /* Main Nav */ + #banner nav { + background: #000305; + font-size: 1.143em; + overflow: auto; + line-height: 30px; + margin: 0 auto 2em auto; + padding: 0; + text-align: center; + max-width: 800px; + + border-radius: 5px; + -moz-border-radius: 5px; + -webkit-border-radius: 5px; + } + + #banner nav ul {list-style: none; margin: 0 auto; max-width: 800px;} + #banner nav li {float: left; display: inline; margin: 0;} + + #banner nav a:link, #banner nav a:visited { + color: #fff; + display: inline-block; + height: 30px; + padding: 5px 1.5em; + text-decoration: none; + } + #banner nav a:hover, #banner nav a:active, + #banner nav .active a:link, #banner nav .active a:visited { + background: #C74451; + color: #fff; + text-shadow: none !important; + } + + #banner nav li:first-child a { + border-top-left-radius: 5px; + -moz-border-radius-topleft: 5px; + -webkit-border-top-left-radius: 5px; + + border-bottom-left-radius: 5px; + -moz-border-radius-bottomleft: 5px; + -webkit-border-bottom-left-radius: 5px; + } + +/* + Featured +*****************/ +#featured { + background: #fff; + margin-bottom: 2em; + overflow: hidden; + padding: 20px; + max-width: 760px; + + border-radius: 10px; + -moz-border-radius: 10px; + -webkit-border-radius: 10px; +} + +#featured figure { + border: 2px solid #eee; + float: right; + margin: 0.786em 2em 0 5em; + max-width: 248px; +} +#featured figure img {display: block; float: right;} + +#featured h2 {color: #C74451; font-size: 1.714em; margin-bottom: 0.333em;} +#featured h3 {font-size: 1.429em; margin-bottom: .5em;} + +#featured h3 a:link, #featured h3 a:visited {color: #000305; text-decoration: none;} +#featured h3 a:hover, #featured h3 a:active {color: #fff;} + +/* + Body +*****************/ +#content { + background: #fff; + margin-bottom: 2em; + overflow: hidden; + padding: 20px 20px; + max-width: 760px; + + border-radius: 10px; + -moz-border-radius: 10px; + -webkit-border-radius: 10px; +} + +/* + Extras +*****************/ +#extras {margin: 0 auto 3em auto; overflow: hidden;} + +#extras ul {list-style: none; margin: 0;} +#extras li {border-bottom: 1px solid #fff;} +#extras h2 { + color: #C74350; + font-size: 1.429em; + margin-bottom: .25em; + padding: 0 3px; +} + +#extras a:link, #extras a:visited { + color: #444; + display: block; + border-bottom: 1px solid #F4E3E3; + text-decoration: none; + padding: .3em .25em; +} + +#extras a:hover, #extras a:active {color: #fff;} + + /* Blogroll */ + #extras .blogroll { + float: left; + max-width: 615px; + } + + #extras .blogroll li {float: left; margin: 0 20px 0 0; max-width: 185px;} + + /* Social */ + #extras .social { + float: right; + max-width: 175px; + } + +/* + About +*****************/ +#about { + background: #fff; + font-style: normal; + margin-bottom: 2em; + overflow: hidden; + padding: 20px; + text-align: left; + max-width: 760px; + + border-radius: 10px; + -moz-border-radius: 10px; + -webkit-border-radius: 10px; +} + +#about .primary {float: left; max-width: 165px;} +#about .primary strong {color: #C64350; display: block; font-size: 1.286em;} +#about .photo {float: left; margin: 5px 20px;} + +#about .url:link, #about .url:visited {text-decoration: none;} + +#about .bio {float: right; max-width: 500px;} + +/* + Footer +*****************/ +#contentinfo {padding-bottom: 2em; text-align: right;} + +/***** Sections *****/ +/* Blog */ +.hentry { + display: block; + clear: both; + border-top: 1px solid #eee; + padding: 1.5em 0; +} +li:first-child .hentry, #content > .hentry {border: 0; margin: 0;} +#content > .hentry {padding: 1em 0;} +.hentry img{display : none ;} +.entry-title {font-size: 3em; margin-bottom: 10px; margin-top: 0;} +.entry-title a:link, .entry-title a:visited {text-decoration: none; color: #333;} +.entry-title a:visited {background-color: #fff;} + +.hentry .post-info * {font-style: normal;} + + /* Content */ + .hentry footer {margin-bottom: 2em;} + .hentry footer address {display: inline;} + #posts-list footer address {display: block;} + + /* Blog Index */ + #posts-list {list-style: none; margin: 0;} + #posts-list .hentry {padding-left: 10px; position: relative;} + + #posts-list footer { + left: 10px; + position: relative; + float: left; + top: 0.5em; + max-width: 190px; + } + + /* About the Author */ + #about-author { + background: #f9f9f9; + clear: both; + font-style: normal; + margin: 2em 0; + padding: 10px 20px 15px 20px; + + border-radius: 5px; + -moz-border-radius: 5px; + -webkit-border-radius: 5px; + } + + #about-author strong { + color: #C64350; + clear: both; + display: block; + font-size: 1.429em; + } + + #about-author .photo {border: 1px solid #ddd; float: left; margin: 5px 1em 0 0;} + + /* Comments */ + #comments-list {list-style: none; margin: 0 1em;} + #comments-list blockquote { + background: #f8f8f8; + clear: both; + font-style: normal; + margin: 0; + padding: 15px 20px; + + border-radius: 5px; + -moz-border-radius: 5px; + -webkit-border-radius: 5px; + } + #comments-list footer {color: #888; padding: .5em 1em 0 0; text-align: right;} + + #comments-list li:nth-child(2n) blockquote {background: #F5f5f5;} + + /* Add a Comment */ + #add-comment label {clear: left; float: left; text-align: left; max-width: 150px;} + #add-comment input[type='text'], + #add-comment input[type='email'], + #add-comment input[type='url'] {float: left; max-width: 200px;} + + #add-comment textarea {float: left; height: 150px; max-width: 495px;} + + #add-comment p.req {clear: both; margin: 0 .5em 1em 0; text-align: right;} + + #add-comment input[type='submit'] {float: right; margin: 0 .5em;} + #add-comment * {margin-bottom: .5em;} diff --git a/theme/css/pygment.css b/theme/css/pygment.css new file mode 100644 index 0000000..fdd056f --- /dev/null +++ b/theme/css/pygment.css @@ -0,0 +1,205 @@ +.hll { +background-color:#eee; +} +.c { +color:#408090; +font-style:italic; +} +.err { +border:1px solid #FF0000; +} +.k { +color:#007020; +font-weight:bold; +} +.o { +color:#666666; +} +.cm { +color:#408090; +font-style:italic; +} +.cp { +color:#007020; +} +.c1 { +color:#408090; +font-style:italic; +} +.cs { +background-color:#FFF0F0; +color:#408090; +} +.gd { +color:#A00000; +} +.ge { +font-style:italic; +} +.gr { +color:#FF0000; +} +.gh { +color:#000080; +font-weight:bold; +} +.gi { +color:#00A000; +} +.go { +color:#303030; +} +.gp { +color:#C65D09; +font-weight:bold; +} +.gs { +font-weight:bold; +} +.gu { +color:#800080; +font-weight:bold; +} +.gt { +color:#0040D0; +} +.kc { +color:#007020; +font-weight:bold; +} +.kd { +color:#007020; +font-weight:bold; +} +.kn { +color:#007020; +font-weight:bold; +} +.kp { +color:#007020; +} +.kr { +color:#007020; +font-weight:bold; +} +.kt { +color:#902000; +} +.m { +color:#208050; +} +.s { +color:#4070A0; +} +.na { +color:#4070A0; +} +.nb { +color:#007020; +} +.nc { +color:#0E84B5; +font-weight:bold; +} +.no { +color:#60ADD5; +} +.nd { +color:#555555; +font-weight:bold; +} +.ni { +color:#D55537; +font-weight:bold; +} +.ne { +color:#007020; +} +.nf { +color:#06287E; +} +.nl { +color:#002070; +font-weight:bold; +} +.nn { +color:#0E84B5; +font-weight:bold; +} +.nt { +color:#062873; +font-weight:bold; +} +.nv { +color:#BB60D5; +} +.ow { +color:#007020; +font-weight:bold; +} +.w { +color:#BBBBBB; +} +.mf { +color:#208050; +} +.mh { +color:#208050; +} +.mi { +color:#208050; +} +.mo { +color:#208050; +} +.sb { +color:#4070A0; +} +.sc { +color:#4070A0; +} +.sd { +color:#4070A0; +font-style:italic; +} +.s2 { +color:#4070A0; +} +.se { +color:#4070A0; +font-weight:bold; +} +.sh { +color:#4070A0; +} +.si { +color:#70A0D0; +font-style:italic; +} +.sx { +color:#C65D09; +} +.sr { +color:#235388; +} +.s1 { +color:#4070A0; +} +.ss { +color:#517918; +} +.bp { +color:#007020; +} +.vc { +color:#BB60D5; +} +.vg { +color:#BB60D5; +} +.vi { +color:#BB60D5; +} +.il { +color:#208050; +} diff --git a/theme/css/reset.css b/theme/css/reset.css new file mode 100644 index 0000000..f5123cf --- /dev/null +++ b/theme/css/reset.css @@ -0,0 +1,52 @@ +/* + Name: Reset Stylesheet + Description: Resets browser's default CSS + Author: Eric Meyer + Author URI: https://meyerweb.com/eric/tools/css/reset/ +*/ + +/* v1.0 | 20080212 */ +html, body, div, span, applet, object, iframe, +h1, h2, h3, h4, h5, h6, p, blockquote, pre, +a, abbr, acronym, address, big, cite, code, +del, dfn, em, font, img, ins, kbd, q, s, samp, +small, strike, strong, sub, sup, tt, var, +b, u, i, center, +dl, dt, dd, ol, ul, li, +fieldset, form, label, legend, +table, caption, tbody, tfoot, thead, tr, th, td { + background: transparent; + border: 0; + font-size: 100%; + margin: 0; + outline: 0; + padding: 0; + vertical-align: baseline; +} + +body {line-height: 1;} + +ol, ul {list-style: none;} + +blockquote, q {quotes: none;} + +blockquote:before, blockquote:after, +q:before, q:after { + content: ''; + content: none; +} + +/* remember to define focus styles! */ +:focus { + outline: 0; +} + +/* remember to highlight inserts somehow! */ +ins {text-decoration: none;} +del {text-decoration: line-through;} + +/* tables still need 'cellspacing="0"' in the markup */ +table { + border-collapse: collapse; + border-spacing: 0; +} diff --git a/theme/css/typogrify.css b/theme/css/typogrify.css new file mode 100644 index 0000000..3bae497 --- /dev/null +++ b/theme/css/typogrify.css @@ -0,0 +1,3 @@ +.caps {font-size:.92em;} +.amp {color:#666; font-size:1.05em;font-family:"Warnock Pro", "Goudy Old Style","Palatino","Book Antiqua",serif; font-style:italic;} +.dquo {margin-left:-.38em;} diff --git a/theme/css/wide.css b/theme/css/wide.css new file mode 100644 index 0000000..88fd59c --- /dev/null +++ b/theme/css/wide.css @@ -0,0 +1,48 @@ +@import url("main.css"); + +body { + font:1.3em/1.3 "Hoefler Text","Georgia",Georgia,serif,sans-serif; +} + +.post-info{ + display: none; +} + +#banner nav { + display: none; + -moz-border-radius: 0px; + margin-bottom: 20px; + overflow: hidden; + font-size: 1em; + background: #F5F4EF; +} + +#banner nav ul{ + padding-right: 50px; +} + +#banner nav li{ + float: right; + color: #000; +} + +#banner nav li a { + color: #000; +} + +#banner h1 { + margin-bottom: -18px; +} + +#featured, #extras { + padding: 50px; +} + +#featured { + padding-top: 20px; +} + +#extras { + padding-top: 0px; + padding-bottom: 0px; +} diff --git a/theme/fonts/Yanone_Kaffeesatz_400.eot b/theme/fonts/Yanone_Kaffeesatz_400.eot new file mode 100644 index 0000000..b3b90db Binary files /dev/null and b/theme/fonts/Yanone_Kaffeesatz_400.eot differ diff --git a/theme/fonts/Yanone_Kaffeesatz_400.svg b/theme/fonts/Yanone_Kaffeesatz_400.svg new file mode 100644 index 0000000..a69669b --- /dev/null +++ b/theme/fonts/Yanone_Kaffeesatz_400.svg @@ -0,0 +1,407 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/theme/fonts/Yanone_Kaffeesatz_400.ttf b/theme/fonts/Yanone_Kaffeesatz_400.ttf new file mode 100644 index 0000000..6f4feb0 Binary files /dev/null and b/theme/fonts/Yanone_Kaffeesatz_400.ttf differ diff --git a/theme/fonts/Yanone_Kaffeesatz_400.woff b/theme/fonts/Yanone_Kaffeesatz_400.woff new file mode 100644 index 0000000..ddccf76 Binary files /dev/null and b/theme/fonts/Yanone_Kaffeesatz_400.woff differ diff --git a/theme/fonts/Yanone_Kaffeesatz_400.woff2 b/theme/fonts/Yanone_Kaffeesatz_400.woff2 new file mode 100644 index 0000000..7b18f7e Binary files /dev/null and b/theme/fonts/Yanone_Kaffeesatz_400.woff2 differ diff --git a/theme/fonts/Yanone_Kaffeesatz_LICENSE.txt b/theme/fonts/Yanone_Kaffeesatz_LICENSE.txt new file mode 100644 index 0000000..c70bcad --- /dev/null +++ b/theme/fonts/Yanone_Kaffeesatz_LICENSE.txt @@ -0,0 +1,93 @@ +Copyright 2010 The Yanone Kaffeesatz Project Authors (https://github.com/alexeiva/yanone-kaffeesatz) + +This Font Software is licensed under the SIL Open Font License, Version 1.1. +This license is copied below, and is also available with a FAQ at: +http://scripts.sil.org/OFL + + +----------------------------------------------------------- +SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007 +----------------------------------------------------------- + +PREAMBLE +The goals of the Open Font License (OFL) are to stimulate worldwide +development of collaborative font projects, to support the font creation +efforts of academic and linguistic communities, and to provide a free and +open framework in which fonts may be shared and improved in partnership +with others. + +The OFL allows the licensed fonts to be used, studied, modified and +redistributed freely as long as they are not sold by themselves. The +fonts, including any derivative works, can be bundled, embedded, +redistributed and/or sold with any software provided that any reserved +names are not used by derivative works. The fonts and derivatives, +however, cannot be released under any other type of license. The +requirement for fonts to remain under this license does not apply +to any document created using the fonts or their derivatives. + +DEFINITIONS +"Font Software" refers to the set of files released by the Copyright +Holder(s) under this license and clearly marked as such. This may +include source files, build scripts and documentation. + +"Reserved Font Name" refers to any names specified as such after the +copyright statement(s). + +"Original Version" refers to the collection of Font Software components as +distributed by the Copyright Holder(s). + +"Modified Version" refers to any derivative made by adding to, deleting, +or substituting -- in part or in whole -- any of the components of the +Original Version, by changing formats or by porting the Font Software to a +new environment. + +"Author" refers to any designer, engineer, programmer, technical +writer or other person who contributed to the Font Software. + +PERMISSION & CONDITIONS +Permission is hereby granted, free of charge, to any person obtaining +a copy of the Font Software, to use, study, copy, merge, embed, modify, +redistribute, and sell modified and unmodified copies of the Font +Software, subject to the following conditions: + +1) Neither the Font Software nor any of its individual components, +in Original or Modified Versions, may be sold by itself. + +2) Original or Modified Versions of the Font Software may be bundled, +redistributed and/or sold with any software, provided that each copy +contains the above copyright notice and this license. These can be +included either as stand-alone text files, human-readable headers or +in the appropriate machine-readable metadata fields within text or +binary files as long as those fields can be easily viewed by the user. + +3) No Modified Version of the Font Software may use the Reserved Font +Name(s) unless explicit written permission is granted by the corresponding +Copyright Holder. This restriction only applies to the primary font name as +presented to the users. + +4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font +Software shall not be used to promote, endorse or advertise any +Modified Version, except to acknowledge the contribution(s) of the +Copyright Holder(s) and the Author(s) or with their explicit written +permission. + +5) The Font Software, modified or unmodified, in part or in whole, +must be distributed entirely under this license, and must not be +distributed under any other license. The requirement for fonts to +remain under this license does not apply to any document created +using the Font Software. + +TERMINATION +This license becomes null and void if any of the above conditions are +not met. + +DISCLAIMER +THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT +OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE +COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL +DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM +OTHER DEALINGS IN THE FONT SOFTWARE. diff --git a/theme/fonts/font.css b/theme/fonts/font.css new file mode 100644 index 0000000..a9eb87e --- /dev/null +++ b/theme/fonts/font.css @@ -0,0 +1,12 @@ +@font-face { + font-family: 'Yanone Kaffeesatz'; + font-style: normal; + font-weight: 400; + src: + local('Yanone Kaffeesatz Regular'), + local('YanoneKaffeesatz-Regular'), + /* from https://fonts.gstatic.com/s/yanonekaffeesatz/v8/YDAoLskQQ5MOAgvHUQCcLRTHiN2BPBirwIkMLKUspj4.woff */ + url('Yanone_Kaffeesatz_400.woff') format('woff'), + /* from https://fonts.gstatic.com/s/yanonekaffeesatz/v8/YDAoLskQQ5MOAgvHUQCcLfGwxTS8d1Q9KiDNCMKLFUM.woff2 */ + url('Yanone_Kaffeesatz_400.woff2') format('woff2'); +}