| Did you read the blog post at all? It's a little bit ridiculous how many of the things you mention here were also mentioned there. You:
> I believe that Hugo (and others) take Markdown in precisely their expected format, and layout, with their format of header and, with precisely the correct version of config file and template.. turn it into some really nice looking HTML. Fast. The post:
> Currently, in addition to Hugo’s list pages, every URL must be backed by a content file (Markdown, HTML etc.). This covers most use cases, but we need a flexible way to generate pages from other data sources. Think product catalogues and similar. You:
> I guess - even after 5 years they aren't attempting to call it 1.0 at least. Maybe the other things will get fixed before then. The post:
> Hugo has stuck with the sub-zero versions to signal active development ... But we are closing in on the first major stable version. You:
> Now.. a week later... new minor release time. Does the new release work with your existing config? With your existing theme? The post:
> with a new main release every 5-6 weeks. But we take stability very seriously (breaking things add lots of support work, we don’t like that) and most site upgrades are smooth. Words in a blog post are easy to write, the proof is in the actual use of the software. But equally, to me this post strikes a positive tone about the future of Hugo as more than just a tool that helps you ditch WordPress. A lot of that work will have already started and I'm sure they would welcome your contributions, large or small. |