Static site generator without posts

Is there a static site generator that does not do posts (blogs/weblogs)? Certainly static site generators like Jekyll and Hugo can be used to generate a typical website without any posts. If there is such a thing as one that does not even support posts then I am interested.

GitHub Pages support Jekyll; I do not know if it supports other static site generators. GitLab Pages supports many others and that is how I learned about static site generators.

Static site generators are new to me but I think that the way Jekyll and Hugo work is that they have built-in support of a default menu of posts but not other types of pages. I think it would be useful for a static site generator to have built-in support of a default menu of pages, not posts. As I said, static site generators can work, I just am interested in knowing if there is something designed in a manner more consistent with my needs.

If you’re looking into static site generation you may want to look into Netlify as well. Super easy to set up, connected to GitLab or GitHub. It’s easy to get started, it supports custom domains including free SSL. I use it for my own blog and I’m really happy with it.

Thank you. I am using Netlify for one site. It is of course not a static site generator; I know you know that. I know you are suggesting it as one possible use of static site generators.

For some of my sites I just need something simple so GitHub Pages and GitLab Pages (I assume) are enough. For sites that I need more for I intend to use ASP.Net Core with Razor pages in the IBM Cloud.

1 Like

The project in my profile provides an editor to build pages using a content editor to drag and drop components like markdown, html snippets, form elements, data sources (rest apis), and embed external applications using webpack 5 module federation. Once pages are created are pre-rendered to static html and deployed as a static site. An example of the which is the projects demo site hosted as a static github repo: https://github.com/ng-druid/ng-druid.github.io. This achieved using Angular server-side rendering in combination with pre-rendering https://angular.io/guide/prerendering.

Furthermore, I recently discovered this gem which is a Blazor Angular hybrid rapid development solution which does something very similar https://www.radzen.com/. This project provides a desktop Razor application to drag and drop components and deploy a static html Angular site. While this is a very powerful the downside is it isn’t open source and not extensible. Take a look at the demos just to grasp how neat this is https://www.radzen.com/demos/.

Hi Samuel,

A good one that is very generic is https://astro.build/ it aims to only add in JS when required making it very quick and light weight. I have used it to build a number of static websites for example https://www.theinkbureau.com.au/

Most static site tools can be used for website but they do love to use blog in the tutorial as it seems to be very common.

Anyway I hope this helps you.

I am currently looking at Node.js. It has a build-time generation feature that I think qualifies. I am only beginning to learn it. It does however seem to not have the weblog features built-in; I am sure there are ways to add that for those that that need it.

I prefer to avoid JavaScript (that is a different topic) and I assume I do not need heavy use of JavaScript to use Node.js. And at least JavaScript is more common than the languages used by most static site generators.

I said JavaScript is a different topic because I know discussions often drift off-topic.

So I will just say that it is my understanding that JavaScript running on a server is not always node.js. Node.js is software written in JavaScript.

They share the same internal engine. The only difference is one runs in a browser and other on server.

Actually NodeJS is cross platform server side framework. You might know as it is best suited for I/O bound and Data Streaming Applications, it uses Google Chrome’s JavaScript V8 Engine for above mentioned purposes So it’s independent of browser and platform.

I still have not tried that but I hope to. I assume you are correct that it is worth trying.

I gave up on Node.js; the tutorial I was using does not describe creation of a site that can be used in DigitalOcean as a static site.

I tried How to deploy Blazor WebAssembly to DigitalOcean App Platform and managed to get it to work. I like WebAssembly and Blazor is consistent with my familiarity with .Net and such.

I got frustrated with inadequate support from IBM for their Cloud so I will try DigitalOcean for now. For now I intend to use Blazor in static sites in DigitalOcean and use a DigitalOcean Droplet for full ASP.Net sites.

In this post I describe how you can prerender all the pages in a Blazor WebAssembly app, without requiring a host app. That means you can still host your Blazor WebAssembly as static files using GitHub Pages or Netlify, without requiring a backend server .

That is fascinating. I didn’t know blazor has pre-rendering.

After my last reply I found about a dozen tutorials describing how to use Blazor for GitHub Pages.

Would you mind sharing some links. I’m interested in evaluating Blazor as an Allie fior building eco-friendly websites. If it can be used in the way you say it can be using pre-rendering to static pages.

Does Astro provide support for webpack 5 module federation? Can I create a Astro micro-frontend and host it in a shell Angular, React, Vue parent app that supports module federation via web pack 5.

See How to deploy ASP.NET Blazor WebAssembly to GitHub Pages. I was able to create a static site using that tutorial. Everything I know I found by searching.

An advantage and disadvantage of Astro is the variety of templates supported by Astro. It is fantastic to have many choices but intimidating when we know nothing about all the choices. I tried to do research on the selections, such as React, Preact and Svelte, but there were no clear choices. Some descriptions of React say it creates single-page applications but not all descriptions say that. Reviews and comparisons always emphasize what the author considers important and consistent with the topic I specified for this discussion, it is not clear what templates are best if we do not want blogs/posts support. The second important feature for me is useful navigation and the third is a simple layout, not huge headers and stuff intended to be impressive that inhibit function.

Cloudflare Pages supports Astro and that is something I might try but it is difficult to decide which template to invest time into.