easy-hugo-blog
ruby-slim
| easy-hugo-blog | ruby-slim | |
|---|---|---|
| 1 | 1 | |
| 0 | 0 | |
| - | - | |
| 10.0 | 4.1 | |
| over 1 year ago | 9 months ago | |
| HTML | Ruby | |
| Apache License 2.0 | 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.
easy-hugo-blog
-
We Should Have Markdown Rendered Websites
I've create a Hugo blog Template used to create a Hugo blog quickly:
https://github.com/openpress/easy-hugo-blog
ruby-slim
-
We Should Have Markdown Rendered Websites
I like Markdown and use it at work, but I think Asciidoc is a better markup language because it is more consistent and has support for more things than Markdown does (e.g., better table support, callouts, tips, etc.).
I currently use 11ty with the Asciidoc plugin for building websites. This setup is nice because I only have to fiddle with HTML and CSS during the design phase. Once that's done, nearly all my website maintenance is done in Asciidoc. Easy!
I don't think I'd want to directly write an entire website in either Markdown or Asciidoc. I think, eventually, doing so would result in these markup languages becoming as cluttered and weird as the HTML/DOM/JavaScript/CSS mess is now.
I think a better step to improving HTML and CSS would be to have the browsers support Slim (https://github.com/deepin-community/ruby-slim) and Sass out of the box instead. That would make my design phase less wordy and redundant while keeping my Asciidoc experience nice and tidy.
What are some alternatives?
Zato - ESB, SOA, REST, APIs and Cloud Integrations in Python
raito - Mini Markdown Wiki/CMS in 8kb of JavaScript
madness - Instant Markdown Server
mdx - Markdown for the component era