clo / cl-site public

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-14.

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-14.

@tplotnikov Please review the following proposal of the roles of each of the directories we currently have.

Erik Huelsmann (@ehuelsmann) on GitLab, 2018-10-14.

@dcooper how would we fold the .lisp extension into this proposal?

Dave Cooper (@dcooper) on GitLab, 2018-10-14.

As it is now, the .lisp files are simply expected to be mixed in with .html files in content/. If there are two same-named files, one with type lisp and one with type html, the lisp will take precedence and the html will be ignored (& overwritten, then blown away, during cl-site:make-site).

I'll go ahead and merge this request, then will update the README.md to reflect the above setup (unless there are any objections).

I do think our setup is starting to creep toward a somewhat fragile "Rube Goldberg" type of situation, what with a bunch of files sitting around with a hodgepodge of procedural transformations happening on them. At some point we might want to look at unifying the site model. On the other hand, it will always be good to be flexible and accept a range of content types (html, markdown, lhtml, fragments, full pages), to lower the bar for people wanting to contribute. Anyway, at some point I might play with some kind of unifying model (using Gendl/GWL) - if anyone else has ideas along these lines, please let me know so we're not going off on different tangents.