Re: [MirageOS-devel] Blog and OPAM-aware static website generator

[Amir Chaudhry <amc79@xxxxxxxxx>]

> On 23 Sep 2015, at 22:33, Dominic Price <dominic.price@xxxxxxxxxxxxxxxx> 
> wrote:
> 
> 
> 
> On 23/09/2015 10:32, Amir Chaudhry wrote:
>> 
>>> On 23 Sep 2015, at 09:20, Gareth Rushgrove <gareth@xxxxxxxxxxxxxxxxx> wrote:
>>> 
>>> On 22 September 2015 at 21:24, Andrew Stuart
>>> <andrew.stuart@xxxxxxxxxxxxxxxxxx> wrote:
>>>> The Pioneer Projects page 
>>>> https://github.com/mirage/mirage-www/wiki/Pioneer-Projects mentions "Blog 
>>>> and OPAM-aware static website generatorâ.
>>>> 
>>>> Anyone interested in generating static websites would gain a great deal 
>>>> from first investigating httrack - itâs the most powerful static site 
>>>> generator although not many people seem to know of it.  httrack can 
>>>> convert most websites into static HTML and then they just need to be 
>>>> compiled into MirageOS.
>>>> 
>>>> https://www.httrack.com
>>>> 
>>> 
>>> I'd see htttrack as more of a spiderering tool, for downloading an
>>> existing site. Like wget but more specialised. It's pretty great.
>>> 
>>> I _think_ this project refers more to generating the HTML in the first
>>> place, often from something like a directory of markdown files. Most
>>> languages have something similar and it's often a great
>>> my-first-running-application place to start with a new language. As
>>> inspiration for that sort of thing:
>>> 
>>> https://gohugo.io/ (Go)
>>> http://blog.getpelican.com/ (Python)
>>> https://sculpin.io/ (PHP)
>>> https://jekyllrb.com/ (Ruby)
>>> http://wintersmith.io/ (JavaScript)
>> 
>> Yes, this project is about creating a pure OCaml static-site generator, but 
>> with the added benefit of being able to extend functionality to make use of 
>> other parts of the OCaml ecosystem (i.e. OPAM).  
> 
> Out of interest, is there a particular reason for wanting a pure OCaml
> tool? I was thinking about a similar tool recently and as a starting
> point I was going to start with something simple that could take the
> output from Jekyll (for example) and wrap it up as a unikernel.

Making a unikernel from the ouput of Jekyll (or any static website generator) 
is pretty straightforward already and can even be done without a local OCaml 
environment (e.g using TravisCI) [1].

Having a pure OCaml version would make it easier to plug into the existing 
toolchain, without requiring different environments (e.g Ruby for Jekyll) or 
complicated hacks. It would then be easier to hook up to other things, in terms 
of automated site generation (Iâm thinking dashboards, projects sites, etc). In 
addition, the process of building the tooling should also lead to a number of 
reusable components too (e.g templating).

Amir

[1] http://amirchaudhry.com/from-jekyll-to-unikernel-in-fifty-lines/


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel