docs
Hexo
docs | Hexo | |
---|---|---|
8 | 28 | |
1,375 | 38,653 | |
-0.1% | 0.6% | |
9.8 | 8.2 | |
2 days ago | 8 days ago | |
Python | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
Question: Best affordable host to have multiple domains?
I can recommend https://linode.com, their documentation is excellent https://www.linode.com/docs/ and ready made images also https://www.linode.com/docs/marketplace/
- Looking to get into designing and maintaining websites. Do you guys have any course recommendations so I can be knowledgeable about all things websites?
- Ask HN: Classic Self-managed web app hosting resources
-
I want to set up a simple blog page, securely.
>In other words, let the machine do your thinking for you No, this was idiotic. A generator tool like Hugo doesn't "think" for you. it's a tool, used by a thinking person. Even if someone new to HTML publishing happens to adopt Hugo, they are going to learn things. By the sounds of it, it's likely they will learn things you have not. They will still learn about HTML and CSS. They may optionally learn about optimizing their HTML and CSS, if it matters for performance of their finished product. Not all sites are the same, after all. The output of Hugo is static HTML (and CSS, js if used, images and other supporting files). The input of Hugo is also static - a collection of HTML templates, CSS and, usually, Markdown text files as the primary content store. Creatively used, Hugo sites can appear as feature-rich as many database-driven sites and in a manner that you simply could not do armed with only an editor, unless your site is only a handful of pages. Any Hugo site can be configured to generate other representations of the site, too, automatically. You probably think that's nonsense, but then again you probably also do not publish a hand--crafted [Atom](https://spf13.com/index.xml) or RSS feed to go along with your hand-crafted HTML. Hand-crafted does not automatically mean better. Even the simplest Hugo site implementation typically makes use of categories or tags (or both) to help readers find other relevant content. Inserting a new page into an existing hierarchy of categories and/or tags is trivial. Edit a file; tag it. The navigation structure is rebuilt, in milliseconds, whether there are five pages or five hundred. [Steve Francia's site](https://spf13.com/) provides examples of these facets in use. With Hugo you can also produce large documentation sites/subsites, and even more importantly, maintain them. The [Let's Encrypt documentation site](https://letsencrypt.org/docs/) is a textbook case study. It's too bad the `vim` project DOES NOT use a tool like Hugo, because then its documentation would stand a chance of being current instead of: > The [VimDoc project](https://www.vim.org/docs.php) has links to various types of Vim documentation. The online, hyperlinked copy of the documentation is currently outdated. Send in the drones to edit. "Currently" has lasted a long time! Another example: [Linode's documentation site](https://www.linode.com/docs/) is generated by Hugo (according to the meta attribute inside, v0.83). You can see the source code for all their documentation, including the site theme and Hugo specifics, here https://github.com/linode/docs. Shocking, isn't it? A tool being used for productivity! You portray using a productivity tool like Hugo as being somehow lazy. That's ridiculous. It's a powerful tool that happens to scale from the simplest of use cases to the complex, and for every use case, makes it possible to produce far richer sites than is possible completely by hand. And all of that without a database or need for a runtime language on a server, or client. A generated Hugo site has no need for PHP includes or other helpers. It can run on the simplest HTTP server; it's just static content. It's a tool, like an editor is a tool, to make an author more productive.
- Akamai to Acquire Linode
-
SSGs through the ages: The ‘Reinvention’ era
Hugo has seen success with corporate customers, including 1Password, Linode Digital.gov, KeyCDN, and Let’s Encrypt, to name just a few. Bjørn Erik Pedersen took over as the lead maintainer in 2015 and continues to lead Hugo’s thriving community.
-
Markdown Linting
Besides the official Vale style guides Buildkite, Linode, and Write The Docs have rules online that you can copy into your repo or use as inspiration for your own rules.
-
Download all of Linode documentation
- https://github.com/linode/docs
Hexo
-
Ask HN: Looking for lightweight personal blogging platform
A lot of great suggestions here and some stuff I’ve never heard of before!
Throwing my own suggestion into the ring, as I was just looking into this last week.
I started setting up a blog using Hexo. It’s another Node based SSG that uses markdown and supports tags. It has a lot of neat plugins that people have developed, too.
I like it so far!
https://github.com/hexojs/hexo
-
Hexo, WebFinger and better discoverability
In my case, the latter is not possible because this blog is a static site, generated via Hexo and hosted on GitHub. It simply lacks a modifiable active server component.
-
Top ten popular static site generators (SSG) in 2023
Hexo — best lightweight SSG
-
Nuxt 3 - showcase your sites
Previously I've used Nuxt2 and even sooner - hexo.io
-
Building a static blog using Jekyll & Strapi
To make their creation easier, numerous open-source static websites generators are available: Jekyll, Hugo, Gatsby, Hexo, etc. Most of the time, the content is managed through static (ideally Markdown) files or a Content API. Then, the generator requests the content, injects it in templates defined by the developer and generates a bunch of HTML files.
-
Running a blog on GithubPages with Markdown storage
https://gohugo.io/ written in go, support md https://hexo.io/ written in node
-
Comparing Static and Dynamic Websites
Hexo's
-
who is self-hosting a static website and what are you using to build it?
I'm currently using Hexo, I write articles in markdown, commit them to a git repository and push them to Github. I then have a Github Action to bundle the static website and publish it on Github Pages, so I get free hosting 👌
-
Deploy your blog via let.sh
There are also many alternatives for selecting Static-Side Generating blog framework such as Hexo, Gatsby, Next.js (more details here). We will pick Hexo as our framework because it is a fast, simple & powerful blog framework.
-
What I'm Learning in 2022
Some alternatives I'm considering learning instead of Gatsby are Jeckyll or Hexo.
What are some alternatives?
Sculpin - Sculpin — Static Site Generator
Hugo - The world’s fastest framework for building websites.
markdownlint - A Node.js style checker and lint tool for Markdown/CommonMark files.
Ghost - Independent technology for modern publishing, memberships, subscriptions and newsletters.
markdownlint - Markdown lint tool
Jekyll - :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
Openly - A Vale linter style that aims to replicate Grammarly in an open-source, privacy-friendly way
Pelican - Static site generator that supports Markdown and reST syntax. Powered by Python.
vale - :pencil: A markup-aware linter for prose built with speed and extensibility in mind.
GrapesJS - Free and Open source Web Builder Framework. Next generation tool for building templates without coding
vale-styles - Checks for Vale based on popular style guides
astro - The web framework for content-driven websites. ⭐️ Star to support our work!