<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SAGBOT on SAGBOT.com</title>
    <link>/tags/sagbot/</link>
    <description>Recent content in SAGBOT on SAGBOT.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/sagbot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SAGBOT.com</title>
      <link>/posts/sagbot.com/</link>
      <pubDate>Sat, 21 Sep 2024 00:00:00 +0000</pubDate>
      
      <guid>/posts/sagbot.com/</guid>
      <description>SAGBOT.com history SAGBOT.com was launched at the end of 2021. Since its launch, the site has undergone numerous visual evolutions, each marked by frequent updates. However, one common thread runs through all these changes: the project has never been completely finished. Often, I lacked the motivation to work on the front-end, not really having the soul of an artist, nor the pen of a writer, I didn&amp;rsquo;t know what to write to enrich the content.</description>
      <content>&lt;h2 id=&#34;sagbotcom-history&#34;&gt;&lt;em&gt;SAGBOT.com&lt;/em&gt; history&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;SAGBOT.com&lt;/em&gt; was launched at the end of 2021. Since its launch, the site has undergone numerous visual evolutions, each marked by frequent updates. However, one common thread runs through all these changes: the project has never been completely finished. Often, I lacked the motivation to work on the front-end, not really having the soul of an artist, nor the pen of a writer, I didn&amp;rsquo;t know what to write to enrich the content.&lt;/p&gt;
&lt;p&gt;The old versions were essentially made with &lt;strong&gt;HTML/CSS/PHP/JS&lt;/strong&gt; and were often single-page websites (&lt;em&gt;SPA&lt;/em&gt;). And as I said before, they were frequently empty of content, or even still contained fillers (&lt;em&gt;placeholder&lt;/em&gt;) and even in the worst case links leading to &lt;em&gt;404&lt;/em&gt; pages, because they weren&amp;rsquo;t coded yet.&lt;/p&gt;
&lt;p&gt;It got to the point where for months &lt;em&gt;SAGBOT.com&lt;/em&gt; (before finally making this website) looked like this, just a black page with a simple « Welcome to SAGBOT.com » and a little animation that makes the text move.&lt;/p&gt;

  &lt;figure class=&#34;center&#34; &gt;
    &lt;img src=&#34;/posts/sagbot.com/old_sagbot.com.gif&#34;  alt=&#34;Gif Old SAGBOT.com&#34;   /&gt;
    
      &lt;figcaption class=&#34;center&#34; &gt;GIF of the latest version of &lt;i&gt;SAGBOT.com&lt;/i&gt;&lt;/figcaption&gt;
    
  &lt;/figure&gt;


&lt;h2 id=&#34;current-version&#34;&gt;Current version&lt;/h2&gt;
&lt;p&gt;The current version is no longer based on the same technologies and has no longer the same purpose. As the &lt;em&gt;SAGBOT&lt;/em&gt; project has evolved and become more personal, &lt;em&gt;SAGBOT.com&lt;/em&gt; has become a personal website. At present, it&amp;rsquo;s becoming a blog where I&amp;rsquo;ll be posting articles on IT or even the evolution of the project, like this one.&lt;/p&gt;
&lt;h3 id=&#34;design&#34;&gt;Design&lt;/h3&gt;
&lt;p&gt;First of all, I have to ask myself « How do I want &lt;em&gt;SAGBOT.com&lt;/em&gt; to be? ». After some thought, and even discussion with friends, I came to the conclusion that &lt;em&gt;SAGBOT.com&lt;/em&gt; should become a blog about my passion; computing, to be more in line with my career plan, which is to become a teacher-researcher (see &lt;a href=&#34;https://www.sagbot.com/fr/about&#34;&gt;About&lt;/a&gt;). Given that in the world of research, article writing is commonplace.&lt;/p&gt;
&lt;p&gt;Once I had the subject, it was time to put it into shape. First of all, the monopage was a thing of the past, as it was incompatible with the idea of a blog. The writing had to be simple to implement. Having to recode a &lt;strong&gt;HTML&lt;/strong&gt; page for each article would have been a hindrance, and the site would have ended up like the others, &lt;u&gt;empty&lt;/u&gt;. Having mastered &lt;strong&gt;LaTeX&lt;/strong&gt; and &lt;strong&gt;Markdown&lt;/strong&gt;, and knowing the power of their syntaxes, I wanted to create articles using these languages.&lt;/p&gt;
&lt;p&gt;One of the greatest advantages of &lt;strong&gt;LaTeX&lt;/strong&gt; is the freedom it gives you, as well as the numerous packages enabling customized page layout (&lt;em&gt;Tikz&lt;/em&gt;, etc.). Unfortunately, this advantage can become a drawback, complicating the compatibility of all packages in a &lt;strong&gt;HTML&lt;/strong&gt; page generator. For these reasons, I&amp;rsquo;ve chosen to use &lt;strong&gt;Markdown&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Being an admirer of the &lt;strong&gt;Rust&lt;/strong&gt; programming language, I initially wanted to make this site with one of the following libraries: &lt;a href=&#34;https://github.com/wooorm/markdown-rs&#34;&gt;markdown-rs&lt;/a&gt;, &lt;a href=&#34;https://github.com/wooorm/mdxjs-rs&#34;&gt;mdx-rs&lt;/a&gt;. When I asked about &lt;a href=&#34;https://mdxjs.com/&#34;&gt;&lt;strong&gt;MDX&lt;/strong&gt;&lt;/a&gt;, it seemed the perfect candidate for making the articles, as this &lt;strong&gt;Markdown&lt;/strong&gt; format allows you to use &lt;strong&gt;JS/JSX&lt;/strong&gt; in a &lt;strong&gt;Markdown&lt;/strong&gt; document. However, in discussions with friends who also have websites, they advised me not to use &lt;strong&gt;MDX&lt;/strong&gt;, but instead to use &lt;strong&gt;Markdown&lt;/strong&gt;-based website builder tools such as &lt;a href=&#34;https://gohugo.io/&#34;&gt;&lt;strong&gt;Hugo&lt;/strong&gt;&lt;/a&gt; or &lt;a href=&#34;https://www.getzola.org/&#34;&gt;&lt;strong&gt;Zola&lt;/strong&gt;&lt;/a&gt;. They were much more suited to my needs, and I didn&amp;rsquo;t even have to redo the whole thing. One of my friend even had a website created with &lt;strong&gt;Hugo&lt;/strong&gt; and was very happy with it.&lt;/p&gt;
&lt;p&gt;After reading the documentation for both tools, &lt;strong&gt;Hugo&lt;/strong&gt; seemed simpler and more in tune with what I wanted to do. That&amp;rsquo;s why I ended up using &lt;strong&gt;Hugo&lt;/strong&gt;. As mentioned at the beginning of this article, I&amp;rsquo;m not an artist, so I use a &lt;a href=&#34;https://themes.gohugo.io/themes/hugo-theme-terminal/&#34;&gt;Hugo Terminal&lt;/a&gt; theme made by &lt;a href=&#34;https://radoslawkoziel.pl/&#34;&gt;panr&lt;/a&gt; and made available to everyone, with colors generated by the &lt;a href=&#34;https://panr.github.io/terminal-css/&#34;&gt;Terminal.css&lt;/a&gt; tool.&lt;/p&gt;
&lt;h3 id=&#34;articles&#34;&gt;Articles&lt;/h3&gt;
&lt;p&gt;As I said before, the articles that will appear on &lt;em&gt;SAGBOT.com&lt;/em&gt; will be about computing, and will cover a wide range of topics that I like. The aim will be to write articles from time to time, in the hope that people will find them interesting. To make these articles accessible, they will all be translated into English, as this is an international language.&lt;/p&gt;
&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;
&lt;p&gt;The creation of &lt;em&gt;SAGBOT.com&lt;/em&gt; has been a common thread ever since I discovered computing. Throughout my learning process, whether academic or self-taught. I&amp;rsquo;ve tried to bring every bit of knowledge to life on this site.&lt;/p&gt;
&lt;p&gt;Adopting &lt;strong&gt;Hugo&lt;/strong&gt; as my website generator was an important decision, facilitating article management and ensuring scalability. This transition underlines the importance of choosing the right tools for a long-term project vision. Finally, the integration of themes gave &lt;em&gt;SAGBOT.com&lt;/em&gt; a visual identity, despite my self-perceived lack of artistic ability.&lt;/p&gt;
&lt;p&gt;In the future, &lt;em&gt;SAGBOT.com&lt;/em&gt; will continue to grow as a resource dedicated to computing and the evolution of my larger &lt;em&gt;SAGBOT&lt;/em&gt; project. I&amp;rsquo;m excited to share more knowledge, thoughts and discoveries with an audience.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m grateful for the support and advice received throughout development, which has been instrumental in overcoming obstacles and bringing this project to fruition.&lt;/p&gt;
&lt;p&gt;Now all I have to do is write articles!&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&#34;thank-you&#34;&gt;Thank you&lt;/h3&gt;
&lt;p&gt;I would like to thank &lt;a href=&#34;https://renauxv.fr/&#34;&gt;&lt;em&gt;T. RENAUX VERDIERE&lt;/em&gt;&lt;/a&gt; and &lt;a href=&#34;https://github.com/oiimrosabel&#34;&gt;&lt;em&gt;Mirabelle S. P.&lt;/em&gt;&lt;/a&gt; for their advice throughout the research and creation of this website. Special thanks to &lt;em&gt;T. RENAUX VERDIERE&lt;/em&gt; and &lt;em&gt;Jade P.&lt;/em&gt; for proofreading this article and the other pages of the website.&lt;/p&gt;
</content>
    </item>
    
  </channel>
</rss>
