1 views collected around this technical thread.
Discover how Hugo, the lightning‑fast Go‑based static site generator, enables you to quickly create multilingual, high‑performance websites with built‑in asset processing, theme support, and simple command‑line workflows, and learn step‑by‑step installation and usage instructions for Mac, Windows, and Linux.
This guide explains why the author chose VitePress for a personal blog, walks through creating a VitePress project, configuring essential files, and deploying the site to GitHub Pages using a GitHub Actions workflow, including troubleshooting tips for build failures and CSS issues.
This article walks through installing Node.js and Docsify, initializing a project, customizing the sidebar, navbar, and cover page, adding useful plugins, and deploying the Docsify site with Nginx, highlighting its speed and simplicity compared to other static site generators.
This guide explains how to use the VuePress Hope theme to create feature‑rich project documentation and blog sites, covering installation, configuration of navigation, sidebars, icons, site information, home pages, code highlighting, and category/tag support.
This article explains how to add a Gitalk-based comment feature to a Docsify‑generated documentation site, covering Gitalk fundamentals, GitHub OAuth app setup, integration steps, custom JavaScript tweaks for URL handling, common pitfalls, and a detailed appendix of configuration parameters.
This guide explains how to version‑control Hugo blog posts on GitHub, set up a GitHub Actions workflow that builds and publishes the static site, and mirror the generated pages to Gitee for faster access, covering branch strategy, CI/CD steps, and required code snippets.
This guide explains how to embed dynamic comments into a static Hugo blog by leveraging Hugo's getJSON function, the Waline comment service, and Vercel deploy hooks to fetch, render, and update comment data during site builds, achieving fast, cache‑friendly performance without sacrificing user experience.
This article explains how to verify Baidu indexing for a Hexo‑based blog, create a Baidu webmaster account, add HTML verification tags, generate and submit sitemaps, and enable automatic push so the site is reliably crawled and listed by Baidu.
This tutorial explains how to install Node.js and docsify-cli, initialize a docsify project, customize the navigation bar, cover page, search and code highlighting, and finally deploy the documentation site to GitHub Pages or a cloud server using Nginx, while providing troubleshooting tips.
This guide walks you through using Docsify to create a lightweight, dynamic documentation website for the SpringBoot-based mall project, covering installation, project initialization, sidebar and navigation customization, search, code highlighting, copy‑code features, and deployment via GitHub Pages.
This guide walks developers through selecting VuePress for a centralized documentation portal, installing it globally or locally, configuring navigation and build scripts, generating static files, deploying them on an Ubuntu server with Nginx, and automating updates via Jenkins, cron jobs, and Docker.
This article chronicles the author’s journey from fragmented knowledge‑base tools to adopting MDWiki—a pure front‑end, Markdown‑driven wiki that can be deployed on any web server, integrated with GitHub Pages, and extended with comments, analytics, and custom build pipelines.
This article explains how to automatically generate API documentation using apidoc, host the resulting static files on GitHub Pages, configure the repository settings to serve the docs folder, and obtain a public URL that front‑end developers can access without manual file transfers.
This article explains how to construct a static‑site CMS using GitHub repositories for content, code, and a Travis‑CI‑driven builder, detailing the architecture, deployment pipeline, and the Grunt‑based static generation process for front‑end developers.
The article explains how web front‑end optimization, including static site generation, relies on improving browser‑server performance by addressing CPU, storage, and especially network bottlenecks, and argues that front‑end engineers should view themselves as browser‑application experts rather than just HTML/CSS/JS coders.