jandecaluwe
But Urubu's manual is written using Urubu: http://urubu.jandecaluwe.com/manual/
However, to me the distinctive feature of a blog is not that, but the way entries are ordered (i.e. reverse order by date). For a manual, faq, feature requests,... I need a different ordering scheme, but I am happy with the "one main content" concept.
That having said, there is of course a need combine content in a single page. A layout (aka template) can combine content as needed. It can use other attributes of the page, specified in the front matter. Or it can use the content from other pages. One could put subpages in a subdirectory, and use some filename convention so that a layout can access them.
Urubu has support for pages that are only present for content, and not for being rendered themselves: you can specify a 'null' layout in the front matter.
For an example of feature requests that are ordered by status and number, see http://dev.myhdl.org/meps/
So I need to support content like a manual, a faq, news, feature requests, essays, and yes, also a blog. I also want good navigation support, and an easy way to refer to other project pages. Furthermore, I want programmatorial flexibility, which because of my background means Python and Jinja2 templates.
I wrote this because I didn't find an existing solution that met those requirements. I am not claiming it is "better" in a general sense than anything else - I think it all depends on your requirements and background.
I do use autopulling for some websites, works great indeed.
The distinguishing feature is that the the website structure matches the source structure exactly, which enables a number of other features such as flexible ordering and wiki-links.
Update: I see where the question is coming from - the Quickstart site suggest 2.7 only. Thanks - will update.
I created this project because I needed a generator for a static website - not just a blog.
To accomplish this, the website structure matches the source structure exactly. In a subdirectory, you use the index.md file to specify the content, either explicitly by listing it, or implicitly by specifying the ordering key and direction. A blog would be reverse order by date, but any other scheme is possible.
In addition, this structure makes it possible to refer to other pages in the project using a wiki-like syntax. Basically, Urubu resolves the Markdown syntax for reference links over the project, instead of just within a page. This is a unique feature afaik.
Furthermore, there is support for tags, search, and templating constructs within pages. And it works well with Bootstrap.
It works great for a number of sites that I manage.
Interested to hear your feedback!
Urubu 1.2.0: Templating constructs in pages
A proposal to support the <mark> tag with Markdown
Chisel HDL: the latest instance of a flawed approach
That is how ASICs/FPGAs have been designed by the best teams for the last 2 decades. And it is much more productive than the textual schematic entry you are describing. There is simply no comparison. Synthesis works.
As for your word-playing attempt: "description" stands for a number of things, among those "describing behavior". Just check the Verilog/VHDL LRM or MyHDL manual.
In sharp contrast to what you suggest, logic generation is not the main hardware design problem. And the fact that you think you can beat RTL synthesis by "generating" or "constructing" the logic itself proves one thing: you don't have the slightest idea of the real power of RTL synthesis.
The main problem with hardware design is verification. VERIFICATION. And for that reason, HDLs should not be limited a "fully synthesizable" subuset, but support powerful modeling concepts in the first place. And so far, nothing beats the event-driven paradigm for that purpopse.
The real difference is that in event-driven languages, clock events are explicit, instead of implicit like in Chisel and the whole array of dead HDLs that preceded it. So if history is any guide, Chisel is dead upon arrival.
Thinking software at the RTL level
For parametrizability, you have the full Python power at your disposal. This is also true for conversion, because conversion happens after elaboration of the design.