# Static Site Published articles for Static Site. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Doctave is shutting down DevFeed: [Doctave is shutting down]() Original publisher: [Read original article]() Author: Niklas Begley Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Documentation](), [migration](), [Open Source](), [MkDocs](), [Markdown](), [OpenAPI Specification]() Tags: [blog](), [configuration](), [docs-as-code](), [documentation](), [markdown](), [migration](), [open-source](), [openapi](), [static-site](), [static-site-generator]() ### AI overview Doctave announces that it will shut down on September 14, 2026. Hosted documentation sites, the dashboard, and builds and deploys will stop operating. Users can continue working from their Git repositories and can migrate to the open-source Docapella static site generator, although server-dependent features such as analytics are unsupported. ### Source excerpt After several years of building documentation tooling, we've made the difficult decision to shut Doctave down. The service will stop operating on September 14th, 2026. We have informed all our customers individually, but are also now posting a public message here. On September 14th, Hosted documentation sites will stop being served The Doctave dashboard will no longer be available Builds and deploys will stop running How this impacts you Your content is yours, and it's already in your repository. Doctave was built on docs-as-code precisely so that your Markdown, OpenAPI specs, and configuration live in Git rather than in our database. Nothing needs to be exported from us to keep writing. You own your docs. Where can I move my docs? We have created an open source static site generator, Docapella, that is mostly compatible with existing Doctave projects. The main change you need to make is renaming doctave.yaml to docapella.yaml. Features that require a server, such as analytics, are not supported, but the content model and general look and feel are the same. Thank you To everyone who wrote documentation with Doctave, sent us feedback, filed bugs, or took a chance on a small team building documentation tooling: thank you. We learned an enormous amount from you, and it genuinely mattered to us. If you have questions about the shutdown or need help planning a migration, get in touch at nik@doctave.com. I'll answer every email I can before we wind things down. - Nik & Anton ## This site now runs on Astro, not WordPress DevFeed: [This site now runs on Astro, not WordPress]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-07-19T00:00:00Z Content type: article Language: en Sources: [AS215248 - Notes]() Topics: [Astro](), [WordPress](), [data](), [Web Development](), [Cloudflare](), [Git]() Tags: [astro](), [cloudflare](), [dns](), [git](), [meta](), [network](), [rpki](), [static](), [static-site](), [tooling](), [website](), [wordpress]() ### AI overview The author explains why as215248.net was rebuilt from WordPress as a static Astro site. The site now generates static HTML without a database, PHP, or admin panel, while scripts fetch live network data from services including Globalping, PeeringDB, RIPEstat, RDAP, the NTP Pool, and Tor Metrics. A Git-based process rebuilds and republishes the site daily behind a Cloudflare Tunnel. ### Source excerpt Why I rebuilt as215248.net as a static site, and what it does now -- a live Looking Glass, auto-synced PeeringDB data, and a world map of presence. ## My IndieWeb Journey: A Guide to POSSE on a Hugo Static Site DevFeed: [My IndieWeb Journey: A Guide to POSSE on a Hugo Static Site]() Original publisher: [Read original article]() Author: Tom Published: 2026-01-27T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [IndieWeb](), [Hugo](), [Microformats](), [Giscus](), [GitHub]() Tags: [blog](), [brid-gy](), [building](), [github](), [github-action](), [guide](), [hugo](), [indieweb](), [journey](), [microformats](), [papermod](), [posse](), [static-site](), [syndication](), [web-development](), [webmentions]() ### AI overview A personal guide to applying IndieWeb principles to a Hugo blog through POSSE syndication. It describes cross-posting articles to social networks with a custom GitHub Action, discusses the limitations of comment systems such as Giscus, and emphasizes publishing on an owned site before syndicating elsewhere. ### Source excerpt My journey of integrating IndieWeb principles into my Hugo blog-from microformats to Brid.gy syndication and building a custom Webmention renderer. ## Deploy a Nanoc Static Site to S3 with GitHub Actions DevFeed: [Deploy a Nanoc Static Site to S3 with GitHub Actions]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2024-11-23T00:00:00Z Content type: tutorial Language: en Sources: [Ratn Labs]() Topics: [Amazon S3](), [GitHub Actions](), [Deployment](), [AWS IAM](), [Amazon Web Services]() Tags: [aws](), [aws-s3](), [cloud-devops](), [complete](), [deploy](), [deployment](), [github-actions](), [guide](), [iam](), [policy](), [s3](), [setup](), [static](), [static-site](), [using](), [website](), [workflow](), [yaml]() ### AI overview A step-by-step tutorial explains how to automate deployment of a Nanoc static website to AWS S3 with GitHub Actions. It covers the S3 bucket policy, IAM setup, and the complete workflow YAML. ### Source excerpt A step-by-step guide to automating Nanoc website deployment to AWS S3 using GitHub Actions, including S3 bucket policy, IAM setup, and the complete workflow YAML. ## Optimizing Hugo static site redirects with Cloudflare Pages DevFeed: [Optimizing Hugo static site redirects with Cloudflare Pages]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [GitHub Pages](), [Cloudflare](), [hosting](), [Website]() Tags: [cloudflare](), [cloudflare-pages](), [cloudflare-redirect-rules](), [configuration](), [deploy](), [github-pages](), [hosting](), [how-to](), [hugo](), [hugo-redirects](), [hugo-site-redirects](), [seo](), [static-site](), [static-site-optimization]() ### AI overview This tutorial explains how to generate a redirects file from Hugo aliases, add custom redirects, and deploy it with Cloudflare Pages. It presents the approach as a way to handle more redirects than the author could support with GitHub Pages and Cloudflare's Free plan limitations. ### Source excerpt Learn how to optimize Hugo static site redirects using Cloudflare Pages, overcoming limitations of GitHub Pages and Cloudflare Free plan. ## Adding Mermaid diagrams to Hugo DevFeed: [Adding Mermaid diagrams to Hugo]() Original publisher: [Read original article]() Author: Tom Published: 2024-02-25T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [Markdown](), [Code]() Tags: [code](), [how-to](), [hugo](), [hugo-diagrams](), [hugo-mermaid-integration](), [interactive-diagrams-hugo](), [javascript](), [learn](), [markdown](), [mermaid](), [mermaid-diagrams](), [static-site](), [static-site-diagrams]() ### AI overview A tutorial on adding Mermaid diagrams to Hugo sites by extending Hugo with a custom file and loading Mermaid JavaScript once per page. The diagrams can then be inserted in Markdown files. ### Source excerpt Learn how to add and optimize Mermaid diagrams in Hugo, enhancing your static site with dynamic and interactive diagrams. ## A Journey from Monolith to Micro frontends at Udemy -- Part 2 of 3 DevFeed: [A Journey from Monolith to Micro frontends at Udemy -- Part 2 of 3]() Original publisher: [Read original article]() Author: Hamza ERBAY Published: 2024-01-08T18:30:04Z Content type: article Language: en Sources: [Udemy Engineering]() Topics: [Front end](), [Next.js](), [React](), [Hackathon](), [Web Development](), [GraphQL]() Tags: [architecture](), [collaboration](), [decoupling](), [frontend](), [graphql](), [hackathon](), [hackathons](), [infrastructure](), [micro-frontends](), [next-js](), [performance](), [react](), [static-site]() ### AI overview This second article in a three-part series describes Udemy's hackathon exploration of decoupling its monolithic frontend into micro frontends. It explains the limitations of tightly coupled React components, the choice of Next.js, and criteria used to select the Featured topics page as an initial candidate. ### Source excerpt Transforming Frontend Architecture: A Journey from Monolith to Micro Frontends at Udemy -- Part 2 of 3 By: Chris Nienhuis, Hamza Erbay, Matthew Bise, Nathan Chapman, Seth Hodgson, Trey Briggs, Charles Pham Photo by Hamza Erbay on UnsplashIntroduction In the previous section, we discussed the challenges in our current monolith architecture and the reasons why we are keen on transitioning to a micro frontend architecture. Now, we are going to delve into the hackathon event at Udemy where we explored the idea of decoupling our frontend structure, the preparations we made, and the options we considered for this transformation. If you missed Part 1 of this series, it is located here: Transforming frontend Architecture: A Journey from Monolith to Micro frontends at Udemy -- Part 1... Udemy Hackathon During the Hackathon event at Udemy, which we organize every six months, I had the opportunity to meet some amazing people in 2021. We collaborated on ideas for decoupling the frontend structure, which was a great experience. Our team comprised Chris Nienhuis, Hamza Erbay, Matthew Bise, Nathan Chapman, and Trey Briggs. We would like to thank Seth Hodgson for bringing us together. Preparation Our React components are currently tightly linked to the monolith runtime environment, making it impossible to use them across our various sites or in different rendering environments -- client-side, server-side, or offline via static site generation tools (B2C/B2B, support center, blogs, microsites, etc.). Udemy Monolith's high-level architecture Decoupling the frontend would improve our daily workflow and make it easier to make significant style changes across the apps. After researching modern frontend technologies, we chose Next.js for its strong community support and performance. Then, we worked on the high-level structure for the hackathon. Analyze the inventory The hackathon posed challenges related to our infrastructure and GraphQL integration that needed to be addressed. Our goal was t ## Integrating Spin with Static Site Generators DevFeed: [Integrating Spin with Static Site Generators]() Original publisher: [Read original article]() Author: David Flanagan Published: 2023-06-07T10:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Front end](), [WebAssembly](), [Back end](), [generators]() Tags: [backend](), [frontend](), [generators](), [static](), [static-site](), [webassembly]() ### AI overview The article discusses integrating Spin with static site generators to provide a frontend for a WebAssembly backend. ### Source excerpt Providing a Frontend for Your WebAssembly Backend ## Switching a Personal Blog from WordPress to Hugo DevFeed: [Switching a Personal Blog from WordPress to Hugo]() Original publisher: [Read original article]() Author: Tom Published: 2020-10-24T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [WordPress]() Tags: [hugo](), [hugo-blog-setup](), [hugo-static-site-generator](), [personal](), [personal-blog-management](), [static-site](), [static-site-benefits](), [static-site-generator](), [switching-from-wordpress-to-hugo](), [wordpress](), [wordpress-alternatives]() ### AI overview The author describes moving a personal blog from WordPress to Hugo after years of using WordPress, citing limited time for server maintenance, configuration, updates, and new features. The author plans to share more about the chosen configuration and workflow. ### Source excerpt Learn about the transition from Wordpress to Hugo for managing a personal blog, including reasons for the switch and benefits of using a static site generator. ## Search Box and Cloud Function DevFeed: [Search Box and Cloud Function]() Original publisher: [Read original article]() Published: 2020-04-01T06:45:57Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Firebase](), [Cloud Functions](), [hosting](), [DuckDuckGo](), [Hugo]() Tags: [cloud-functions](), [domain](), [firebase](), [hosting](), [hugo](), [search](), [static-site]() ### AI overview A tutorial showing how to add a search box to a Hugo blog hosted on Firebase Hosting by using Cloud Functions for Firebase and redirecting searches to DuckDuckGo. ### Source excerpt For a blog hosted with Firebase Hosting, it turns out that a little search box is fairly easy to implement by using Cloud Functions for Firebase. ## Adding Staticman Comments DevFeed: [Adding Staticman Comments]() Original publisher: [Read original article]() Author: Travis Downs (travis.downs@gmail.com) Published: 2020-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Performance Matters]() Topics: [GitHub](), [GitHub Pages](), [Bot](), [Pull Request](), [Heroku](), [personal access token](), [hosting](), [repo]() Tags: [blog](), [file](), [github](), [github-pages](), [guide](), [heroku](), [hosting](), [meta](), [personal-access-token](), [pull-request](), [static-site](), [staticman]() ### AI overview A tutorial explaining how to add Staticman comments to a static blog. It covers the submission flow, deploying the API bridge on Heroku, using GitHub pull requests to store comments, and republishing through GitHub Pages. ### Source excerpt Adding static comments to a static blog using staticman. Static. ## Static Page Caching with Craft CMS DevFeed: [Static Page Caching with Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-06-16T04:35:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Caching](), [Content Management System](), [nginx](), [Web Development]() Tags: [backend](), [best](), [cache](), [caching](), [cms](), [content](), [db-based](), [editor](), [friendly](), [frontend](), [generator](), [html](), [insights](), [nginx](), [performance](), [static](), [static-site](), [worlds]() ### AI overview This tutorial explains how to use Nginx FastCGI Cache to add full-page static caching in front of Craft CMS. It contrasts fragment caching with storing complete rendered pages as flat files and discusses performance, concurrency, HTTPS, configuration, and flexibility tradeoffs compared with Varnish and static site generators. ### Source excerpt Get the best of both worlds with static HTML generator performance on the frontend, and a content editor friendly db-based backend ## Blog redesign and new features DevFeed: [Blog redesign and new features]() Original publisher: [Read original article]() Author: Stanko Published: 2016-10-20T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [JavaScript](), [JSON](), [Pull Request](), [GitHub Pages](), [Jenkins](), [GitHub]() Tags: [also](), [blog](), [features](), [github-pages](), [javascript](), [jekyll](), [json](), [new-features](), [pull-requests](), [redesign](), [static-site]() ### AI overview The author describes a redesign of a personal blog and newly added features, including category pages, moderated comments through pull requests, JavaScript fuzzy search over post titles, estimated reading time, and sharing buttons. The article also discusses Jekyll plugins, GitHub Pages limitations on custom plugins, and planned build automation with Jenkins or Travis. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. As you probably noticed I redesigned my blog and added some new features. This is a list of the new stuff. New design Category pages Comments Search Reading time Share buttons New design # My friend Nikola, from MIDA digital agency, helped me a lot with this one. I gave him a basic idea what I wanted, and he came up with this simple but beautiful design. It might go through some smaller changes in the future, but nothing major. Hope you like it. Category pages # These are accessible from the main menu, or by clicking on the category link at the end of the post. Obviosly, they list all of the posts for the selected category. This is the plugin I used: jekyll-archives. Comments # Staticman brings user generated content to the static site generators. You can add their bot to your repo, and then hitting specific endpoint will generate a pull request (or push directly) with the data user entered. My comments are going through pull requests, which enables me to moderate them. Search # Also accessible from the main menu. Search is done by JavaScript and it goes through JSON object with post titles. It uses fuzzy search algorithm, so it will find every title that has all of the letters you entered. Longer word matched will give higher priority to a result. (Try typing SASS for example.) Reading time # At the top of each post, you'll see estimated reading time. It is a very simple plugin I found somewhere on the internet and modified a bit. Here it is: # Outputs the reading time # Read this in "about 4 minutes" # Put into your _plugins dir in your Jekyll site # Usage: Read this in about "page.content | reading_time" module ReadingTimeFilter def reading_time( input ) words_per_minute = 180 words = input.split.size; minutes = ( words / words_per_minute ).floor minutes_label = minutes === 1 ? " minute" : " minutes" minutes > 0 ? "about #{minutes} #{minutes_label}" : "less than 1 minute" end end Liqui ## Why I moved my blog from WordPress.com to Pelican and GitHub Pages DevFeed: [Why I moved my blog from WordPress.com to Pelican and GitHub Pages]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2015-08-02T18:55:00Z Content type: opinion Language: en Sources: [Andrea Corbellini]() Topics: [migration](), [WordPress](), [Content Management System](), [Vim](), [GitHub]() Tags: [blog](), [blogging](), [github-pages](), [migration](), [pelican](), [static-site](), [static-site-generator](), [version-control](), [vim](), [wordpress]() ### AI overview The author explains moving a blog from WordPress.com to Pelican and GitHub Pages after encountering customization, editor, and workflow limitations. They describe using Vim, MathJax, theme customization, version control, and scripts with the static-site setup, while noting that feed URLs changed and that Pelican lacked a preferred theme. ### Source excerpt Today I switched from WordPress.com to Pelican and GitHub Pages. First off, let me say: almost all URLs that were previously working should still work. Only the feed URLs are broken, and this is not something I can fix. If you were following my blog via a feed reader, you should update to the new feed. Sorry for the inconvenience. Having said that ... ## How I created my blog DevFeed: [How I created my blog]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2015-04-25T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Jekyll](), [GitHub Pages](), [Website](), [Markdown](), [Git]() Tags: [blogs](), [git](), [github-pages](), [howto](), [jekyll](), [markdown](), [static-site](), [themes](), [website]() ### AI overview The article explains how the author created a portfolio and blog with GitHub Pages and Jekyll. It covers the requirements for the site, the distinction between static and dynamic websites, Markdown-based posts, local testing, theme customization, and merging two Jekyll themes. ### Source excerpt For quite some months, I've been planning to create a website and start blogging about the things I'm passionate about. Last week, I finally decided to setup a portfolio and blog using GitHub pages and Jekyll.