On Ned, 2015-12-27 at 18:50 -0500, Offray Vladimir Luna Cárdenas wrote: Hiya,
> Seems that the reasons exposed in this tread are: It predated > markdown, so was already used inside the community, and gives us > finer control on the overall markup language, including exporting > formats. Nothing against it, but some features like footnotes are simply 'must' for serious writing, at least in my domain. > Two projects implement this idea Pandoc[2] Yeah, Pandoc is great and it would be cool to have Pillar support for it. > and Grav[3] and both use a combination of markdown and yaml. Grav looks interesting, but I believe I simply want to leave PHP world. :-) > My bet is on pandoc (markdown+yaml) for writing almost anything, with > some advantages over pillar: My main complaint to markdown is that it is not standard, despite many attempts (or extensions). > b. It has support for bibliographic references, footnotes a a more > complete feature set. I wonder how is it that despite being present for so long, it does miss such features... > I have been using Nikola myself and keeping myself under a more > cohesive python environment for making my publishing and > scripting/programming exploration. That changed after knowing > Pharo/Roassal/Moose and now I try to "live inside" these technologies > most of the time for my own interactive documentation and > visualization project[6] and connect with the external world via > standards & formats like Json, cvs, yaml and markdown. That's why now > I'm using grav instead of Nikola for my web publishing. Have you considered to use Pillar markup with Nikola? That's one option I'm considering if Pillar is going to get things liek footnotes etc. > Ecstatic have more powerful things like a logic-less > approach to templating via mustache, that is neutral to the > underlaying language That would be another 'pro' for Pillar markup+Nikola, although I belive Jinja is sufficient for my web needs. Btw, let me say that I'm also inspired with Butterick and was considering to use Racket for my project, but ended up here. :-) > So, while I think that choosing Pharo technologies is better for > making them more mature, tested and used, I also think that is > important to choose proper balance to know which combination of Pharo > technologies and external ones is adequate. I didn't mention, but I was playing with Golang's Hugo for some time which is also nice and, to me, preferrable over PHP. > Ps: Would you mind to share more details about your project. The > questions you're asking for it are pretty interesting. Well, I' considering to write extensive application for Vedic astrology (including calendaring app) which could be used for research purposes, e.g. having ability to seatch for different patterns present in charts stored in local (Sqlite3) databases. There is something similar here: http://saravali.de/maitreya.html but it's written in C++/wx, while I hope to make it with Pharo. Sincerely, Gour -- Whatever action a great man performs, common men follow. And whatever standards he sets by exemplary acts, all the world pursues. -- As a strong wind sweeps away a boat on the water, even one of the roaming senses on which the mind focuses can carry away a man's intelligence. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
