blogs/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2026-08-29 17:52:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Some more on the birthday post

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2018-07-04 14:34:53 +02:00
committed by GitHub
parent 8da3572409
commit 09fe3ea31d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/news/lets-celebrate-hugos-5th-birthday/index.md
+2 -2
View File
@@ -40,7 +40,7 @@ More numbers:
* 26800+ [stars](https://github.com/gohugoio/hugo/stargazers) on GitHub.
* 444+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors)
* 444+ [contributors](https://github.com/gohugoio/hugo/graphs/contributors). [@bep](https://github.com/bep) is the most active with around 70% of the current code base (line count).
* 235+ [themes](https://themes.gohugo.io/)
* 50% increase in user session on the [gohugo.io](https://gohugo.io/) web sites the last 12 months.[^2]
* Hugo build release binaries for [a myriad](https://github.com/gohugoio/hugo/releases/tag/v0.42.2) of platforms. And since it can also be installed from Chocolatey on Windows, Brew on MacOs, Snap on Linux and `apt-get` on Debian/Ubuntu, it is impossible to give accurate download numbers. But the number is not small.
@@ -66,7 +66,7 @@ Pages from "other data sources"
Upgrade Blackfriday to v2
: [Blackfriday](https://github.com/russross/blackfriday) is the main content renderer in Hugo. It has been rewritten to a more flexible architecture, which should allow us to fix some of the current shortcomings.
We should be able to create a better and easier-to-use data structure from the rendered content: Summary, the content after the summary, footnotes, and a ToC that is actually a tree that can be ranged over in your templates.
We should be able to create a better and easier-to-use data structure from the rendered content: Summary, the content after the summary, the footnotes and the ToC that is a proper data structure that can be ranged over in your templates. Having ToC as a proper data structure also open up a few other potential uses; using it as an index in [Related Content](https://gohugo.io/content-management/related/) would be one example.
This should also enable us to _do more_ with [Custom Output Formats](/templates/output-formats). It is already very powerful. GettyPubs are using it in [Quire](https://github.com/gettypubs/quire) to build [beautiful multi-platform publications](http://www.getty.edu/publications/digital/digitalpubs.html). But it can be improved. For rendering of content files, you are currently restricted to HTML. It would be great if we could configure alternative renderers per output format, such as LaTeX and EPUB.