Gridsome VS Hugo

Gridsome — Jamstack SSG tool for Vue developers

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Among other thoughts, I considered a possibility of migration to a newer tech stack (because I can). Don't get me wrong, I actually love Gridsome (which is underneath my website now). But it's quite obsolete, and it's actually a dead project now.

One downside of Gridsome is that development seems to have stopped if you look at their github. For that reason I've recently switched my Gridsome clients to Nuxt

Yes. https://gridsome.org/ is specifically designed for it and it lets you generate plain HTML files for most of the part. It's good for small projects in Vue which are mostly static.

I definitely think Nuxt is worth learning for more than just a static site. However, there is a Gatsby-like Vue framework that focuses on SSG: https://gridsome.org/

Gridsome

All the Static Site Generators have been in the market for many years. With time, they get new improvements and upgrades as well. While considering SSG frameworks, like Gatsby, Nuxt, Gridsome, Next, and many more have been on the developer’s list for a long time. But when we talk about blazing fast web performance as per core web vital, then we have to do a lot of work in the available frameworks, after connecting a lot of dots (in terms of web performance), but still, we cannot achieve the web performance as per our need if we consider a use case of a large website where 20+ components are in one page.

VuetifyJS, NuxtJS (production framework for Vue JS), Quasar, GridSome, etc.,

name: 🚀 Deploy to prod # Will trigger the workflow on each push to the main branch on: push: branches: - main # Allows you to run this workflow manually from the Actions tab workflow_dispatch: jobs: # The first job will build the hugo site and upload the artifact build: name: 🔧 Build Hugo site runs-on: ubuntu-latest env: HUGO_VERSION: 0.111.2 steps: - name: Install Hugo CLI run: | wget -O ${{ runner.temp }}/hugo.deb https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-amd64.deb \ && sudo dpkg -i ${{ runner.temp }}/hugo.deb - name: Install Dart Sass Embedded run: sudo snap install dart-sass-embedded - name: Checkout uses: actions/[email protected] with: submodules: recursive fetch-depth: 0 - name: Install Node.js dependencies run: '[[ -f package-lock.json || -f npm-shrinkwrap.json ]] && npm ci || true' - name: Build with Hugo env: # For maximum backward compatibility with Hugo modules HUGO_ENVIRONMENT: production HUGO_ENV: production run: | hugo \ --gc \ --minify # We save the result as an artificat so we can use it in the next job - name: Upload artifact uses: actions/[email protected] with: name: release-artifact path: './public' # The second job will deploy the site to the FTP server using the artifact from the first job deploy: name: 🎉 Deploy runs-on: ubuntu-latest needs: build steps: - name: Checkout uses: actions/[email protected] # Download the artifact we just created - name: Download artifact uses: actions/[email protected] with: name: release-artifact path: './public' # This is the path where the artifact will be downloaded to - name: Deploy file uses: wlixcc/[email protected] with: server: ${{ vars.ftp_server }} username: ${{ vars.ftp_username }} ssh_private_key: ${{ secrets.ftp_password }} # or if you only use a password # sftp_only: true # password: ${{ secrets.ftp_password }} port: ${{ vars.ftp_port }} remote_path: '/var/www/app' # This will depend on your server local_path: './public/*' # This is the path where the artifact is located

Nowadays, it never has been easier to build and host a website for having any form of online presence. You don't even need a lot of web development knowledge. There are many tools and resources available that make the process easier than ever. One such tool is Hugo, a fast and flexible static site generator that allows users to create websites quickly and easily. In addition, deploying a Hugo site to a web server can be made even simpler through the use of Github Actions (assuming your code is hosted on github), a powerful automation tool that can be used to automatically deploy a website to a FTP server. In this article, we'll explore how to use Hugo to build a website and then deploy it to a FTP server using Github Actions, providing a step-by-step guide for those looking to get their website up and running quickly and efficiently.

The result of this historical evolution is that the world of static site generators has made amazing progress over the past few years and the Python ecosystem hasn't caught up with it. Nowadays there's a rich ecosystem of different options for static site generation, some of which lean more towards server side generation and simplicity (like Hugo) while others leverage Single Page Application frameworks like React.js or similar (like Docusaurus). On top of that, there are "headless CMSs" that can use some of these SSGs as a backend, offering a more sophisticated authoring experience while offloading the HTML output generation to a different component (like Decap CMS, Ghost, or Forestry).

We are going to use an application called Hugo to generate a static website. You could of course run Hugo on your own machine - but to flex your muscles in Azure, we're going to stand up a VM. You'll then be able to experiment with different ways to host this static website within Azure. First, create a resource group to house the authoring workload:

My blog is a static site hosted in AWS Amplify. There's no dynamic content on it at all. I push Markdown files to the main branch of my site repo in GitHub and Amplify builds it with Hugo. Hugo renders the Markdown as HTML and drops it in an S3 bucket behind a CloudFront distribution.

Hugo is not made for minimum viable blogs. Its advantage in performance only becomes important for bigger websites or blogs with thousands of articles. But especially for bigger websites it should be possible to auto-generate a good archive. However the developers of Hugo stubbornly refuse to fix this very important 8 year old issue: https://github.com/gohugoio/hugo/issues/448

If you don't feel like you need to create it from scratch (as in: if you want to have a static blog or website, and you don't mind if you didn't code every little aspect of it), I'd recommend using a generator like Jekyll, Gatsby or Hugo. And even if you don't directly use them, you can learn a bit on how they do this sort of implementation.

Hey thanks for looking :) hugo has a lot more moving parts, and a lot more dependencies [0]. bearclaw is written to be simple and easy to understand without instructions or learning any new paradigms about templating or frontmatter or other markup languages.

[0] https://github.com/gohugoio/hugo#dependencies

I had some expectations with lightweight alternatives to WP. Played some time ago with hugo (https://gohugo.io/), just wanted to set up a simple blog, couple of static pages, that i could extend any time I want.