hugo build

Victordgrandis · Jun 6, 2024 · 49928c4 · 49928c4
1 parent 1d347bf
commit 49928c4
Show file tree

Hide file tree

Showing 8 changed files with 36 additions and 77 deletions.
diff --git a/public/categories/index.xml b/public/categories/index.xml
@@ -4,7 +4,7 @@
     <title>Categories on Victor De Grandis Site</title>
     <link>https://victordgrandis.github.io/blog/categories/</link>
     <description>Recent content in Categories on Victor De Grandis Site</description>
-    <generator>Hugo -- 0.126.3</generator>
+    <generator>Hugo -- 0.127.0</generator>
     <language>en-us</language>
     <atom:link href="https://victordgrandis.github.io/blog/categories/index.xml" rel="self" type="application/rss+xml" />
   </channel>

diff --git a/public/index.html b/public/index.html
@@ -2,7 +2,7 @@
 <html lang="en" dir="auto">
 
 <head>
-	<meta name="generator" content="Hugo 0.126.3"><meta charset="utf-8">
+	<meta name="generator" content="Hugo 0.127.0"><meta charset="utf-8">
 <meta http-equiv="X-UA-Compatible" content="IE=edge">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
 <meta name="robots" content="index, follow">
@@ -182,15 +182,15 @@ <h2 class="entry-hint-parent">Creating Shareable PDF Reports with Kotlin and iTe
 
 <article class="post-entry"> 
   <header class="entry-header">
-    <h2 class="entry-hint-parent">How to use React Query on Nextjs
+    <h2 class="entry-hint-parent">Mastering React Query in Next.js
     </h2>
   </header>
   <div class="entry-content">
     <p>React query is a tool for creating hooks for fetching, caching and updating asynchronous data repository.
 Motivation Fetching data from your backend is one of the most performance killers features of any frontend, and it really helps to keep a copy of the fetched data in the browser, but it’s not always possible, or convenient to build a Redux store, so react-query is a good alternative for managing API results without having to do a lot of work for it, and without having to fetch it again every time you need it....</p>
   </div>
   <footer class="entry-footer"><span title='2024-05-20 13:04:27 -0300 -03'>May 20, 2024</span></footer>
-  <a class="entry-link" aria-label="post link to How to use React Query on Nextjs" href="https://victordgrandis.github.io/blog/posts/react-query/"></a>
+  <a class="entry-link" aria-label="post link to Mastering React Query in Next.js" href="https://victordgrandis.github.io/blog/posts/react-query/"></a>
 </article>
 
 <article class="post-entry"> 
@@ -205,20 +205,6 @@ <h2 class="entry-hint-parent">How to use Hotjar JavaScript triggers on Angular
   <footer class="entry-footer"><span title='2024-05-19 16:42:23 -0300 -03'>May 19, 2024</span></footer>
   <a class="entry-link" aria-label="post link to How to use Hotjar JavaScript triggers on Angular" href="https://victordgrandis.github.io/blog/posts/hotjar-angular/"></a>
 </article>
-
-<article class="post-entry"> 
-  <header class="entry-header">
-    <h2 class="entry-hint-parent">How to parallelize Webpack Loaders
-    </h2>
-  </header>
-  <div class="entry-content">
-    <p>Runing webpack on a big project can be an agony for developers and can delay the production builds and CI if is not treated properly.
-My aim here is to present how you can parallelize the webpack loaders and reduce the times to just seconds.
-Motivation Working with a very big project built on angularjs (a monolithic with 5&#43; products inside) and with a custom webpack configuration that managed a lot of different file types, the building time of the app was around 7’ only for webpack tasks....</p>
-  </div>
-  <footer class="entry-footer"><span title='2024-05-18 16:35:24 -0300 -03'>May 18, 2024</span></footer>
-  <a class="entry-link" aria-label="post link to How to parallelize Webpack Loaders" href="https://victordgrandis.github.io/blog/posts/webpack-loaders/"></a>
-</article>
     </main>
 
 <footer class="footer">

diff --git a/public/index.xml b/public/index.xml
@@ -4,7 +4,7 @@
     <title>Victor De Grandis Site</title>
     <link>https://victordgrandis.github.io/blog/</link>
     <description>Recent content on Victor De Grandis Site</description>
-    <generator>Hugo -- 0.126.3</generator>
+    <generator>Hugo -- 0.127.0</generator>
     <language>en-us</language>
     <lastBuildDate>Tue, 28 May 2024 13:00:23 -0300</lastBuildDate>
     <atom:link href="https://victordgrandis.github.io/blog/index.xml" rel="self" type="application/rss+xml" />
@@ -16,7 +16,7 @@
       <description>Motivation Tables are a cornerstone of data presentation in mobile apps. Android&amp;rsquo;s RecyclerView makes it easy to create dynamic tables with large datasets. However, exporting this data to a PDF or other file format for sharing can be challenging. This post will address this challenge by showing you how to leverage Kotlin and iText to automate the creation and sharing of reports from your RecyclerView data, ensuring proper formatting for A4 pages.</description>
     </item>
     <item>
-      <title>How to use React Query on Nextjs</title>
+      <title>Mastering React Query in Next.js</title>
       <link>https://victordgrandis.github.io/blog/posts/react-query/</link>
       <pubDate>Mon, 20 May 2024 13:04:27 -0300</pubDate>
       <guid>https://victordgrandis.github.io/blog/posts/react-query/</guid>
@@ -31,14 +31,5 @@ Motivation Fetching data from your backend is one of the most performance killer
       <description>JavaScript triggers are the most useful feature for using Hotjar HeatMaps in one page applications, because without that you can&amp;rsquo;t create HeatMaps on dynamic content or modals, dropdowns, etc. So i will show you how i made it work on an Angular project. I&amp;rsquo;m making the assumption that you already have an Hotjar account and initialize a project.
 Include Hotjar in your project First we need to include the tracking code in our index.</description>
     </item>
-    <item>
-      <title>How to parallelize Webpack Loaders</title>
-      <link>https://victordgrandis.github.io/blog/posts/webpack-loaders/</link>
-      <pubDate>Sat, 18 May 2024 16:35:24 -0300</pubDate>
-      <guid>https://victordgrandis.github.io/blog/posts/webpack-loaders/</guid>
-      <description>Runing webpack on a big project can be an agony for developers and can delay the production builds and CI if is not treated properly.
-My aim here is to present how you can parallelize the webpack loaders and reduce the times to just seconds.
-Motivation Working with a very big project built on angularjs (a monolithic with 5+ products inside) and with a custom webpack configuration that managed a lot of different file types, the building time of the app was around 7&amp;rsquo; only for webpack tasks.</description>
-    </item>
   </channel>
 </rss>
diff --git a/public/posts/index.html b/public/posts/index.html
@@ -166,15 +166,15 @@ <h2 class="entry-hint-parent">Creating Shareable PDF Reports with Kotlin and iTe
 
 <article class="post-entry"> 
   <header class="entry-header">
-    <h2 class="entry-hint-parent">How to use React Query on Nextjs
+    <h2 class="entry-hint-parent">Mastering React Query in Next.js
     </h2>
   </header>
   <div class="entry-content">
     <p>React query is a tool for creating hooks for fetching, caching and updating asynchronous data repository.
 Motivation Fetching data from your backend is one of the most performance killers features of any frontend, and it really helps to keep a copy of the fetched data in the browser, but it’s not always possible, or convenient to build a Redux store, so react-query is a good alternative for managing API results without having to do a lot of work for it, and without having to fetch it again every time you need it....</p>
   </div>
   <footer class="entry-footer"><span title='2024-05-20 13:04:27 -0300 -03'>May 20, 2024</span></footer>
-  <a class="entry-link" aria-label="post link to How to use React Query on Nextjs" href="https://victordgrandis.github.io/blog/posts/react-query/"></a>
+  <a class="entry-link" aria-label="post link to Mastering React Query in Next.js" href="https://victordgrandis.github.io/blog/posts/react-query/"></a>
 </article>
 
 <article class="post-entry"> 
@@ -189,20 +189,6 @@ <h2 class="entry-hint-parent">How to use Hotjar JavaScript triggers on Angular
   <footer class="entry-footer"><span title='2024-05-19 16:42:23 -0300 -03'>May 19, 2024</span></footer>
   <a class="entry-link" aria-label="post link to How to use Hotjar JavaScript triggers on Angular" href="https://victordgrandis.github.io/blog/posts/hotjar-angular/"></a>
 </article>
-
-<article class="post-entry"> 
-  <header class="entry-header">
-    <h2 class="entry-hint-parent">How to parallelize Webpack Loaders
-    </h2>
-  </header>
-  <div class="entry-content">
-    <p>Runing webpack on a big project can be an agony for developers and can delay the production builds and CI if is not treated properly.
-My aim here is to present how you can parallelize the webpack loaders and reduce the times to just seconds.
-Motivation Working with a very big project built on angularjs (a monolithic with 5&#43; products inside) and with a custom webpack configuration that managed a lot of different file types, the building time of the app was around 7’ only for webpack tasks....</p>
-  </div>
-  <footer class="entry-footer"><span title='2024-05-18 16:35:24 -0300 -03'>May 18, 2024</span></footer>
-  <a class="entry-link" aria-label="post link to How to parallelize Webpack Loaders" href="https://victordgrandis.github.io/blog/posts/webpack-loaders/"></a>
-</article>
     </main>
 
 <footer class="footer">

diff --git a/public/posts/index.xml b/public/posts/index.xml
@@ -4,7 +4,7 @@
     <title>Posts on Victor De Grandis Site</title>
     <link>https://victordgrandis.github.io/blog/posts/</link>
     <description>Recent content in Posts on Victor De Grandis Site</description>
-    <generator>Hugo -- 0.126.3</generator>
+    <generator>Hugo -- 0.127.0</generator>
     <language>en-us</language>
     <lastBuildDate>Tue, 28 May 2024 13:00:23 -0300</lastBuildDate>
     <atom:link href="https://victordgrandis.github.io/blog/posts/index.xml" rel="self" type="application/rss+xml" />
@@ -16,7 +16,7 @@
       <description>Motivation Tables are a cornerstone of data presentation in mobile apps. Android&amp;rsquo;s RecyclerView makes it easy to create dynamic tables with large datasets. However, exporting this data to a PDF or other file format for sharing can be challenging. This post will address this challenge by showing you how to leverage Kotlin and iText to automate the creation and sharing of reports from your RecyclerView data, ensuring proper formatting for A4 pages.</description>
     </item>
     <item>
-      <title>How to use React Query on Nextjs</title>
+      <title>Mastering React Query in Next.js</title>
       <link>https://victordgrandis.github.io/blog/posts/react-query/</link>
       <pubDate>Mon, 20 May 2024 13:04:27 -0300</pubDate>
       <guid>https://victordgrandis.github.io/blog/posts/react-query/</guid>
@@ -31,14 +31,5 @@ Motivation Fetching data from your backend is one of the most performance killer
       <description>JavaScript triggers are the most useful feature for using Hotjar HeatMaps in one page applications, because without that you can&amp;rsquo;t create HeatMaps on dynamic content or modals, dropdowns, etc. So i will show you how i made it work on an Angular project. I&amp;rsquo;m making the assumption that you already have an Hotjar account and initialize a project.
 Include Hotjar in your project First we need to include the tracking code in our index.</description>
     </item>
-    <item>
-      <title>How to parallelize Webpack Loaders</title>
-      <link>https://victordgrandis.github.io/blog/posts/webpack-loaders/</link>
-      <pubDate>Sat, 18 May 2024 16:35:24 -0300</pubDate>
-      <guid>https://victordgrandis.github.io/blog/posts/webpack-loaders/</guid>
-      <description>Runing webpack on a big project can be an agony for developers and can delay the production builds and CI if is not treated properly.
-My aim here is to present how you can parallelize the webpack loaders and reduce the times to just seconds.
-Motivation Working with a very big project built on angularjs (a monolithic with 5+ products inside) and with a custom webpack configuration that managed a lot of different file types, the building time of the app was around 7&amp;rsquo; only for webpack tasks.</description>
-    </item>
   </channel>
 </rss>