On Jan 29, 2016, at 12:04 PM, [email protected] wrote: > > i'd just liked the simplicity of having > everything in the same location, the ability to use vi instead of browser to > edit the page, and the versioning provided by fossil.
Who said you had to give any of that up? 1. Everything in the same location: Your web site build system (Makefiles, Middleman config files, etc.) also lives in Fossil, right alongside the *.md files that are input to that build system. Think of “make synch” in the same spirit as “make install” in a more typical software build system. 2. Ability to use vi: Where did any of what I wrote say you had to use a browser to edit the source files? I happen to use vi for most of my generated static web sites, too. I happen to use a tool much older than Middleman for historical reasons, but as I understand it, Middleman (and presumably many of its competitors) is a command line HTML generation tool, not a web-facing CMS. 3. Versioning. My generated static site sources live in Fossil. I happen to prefer storing the static web sources in a separate repository from the Fossil repo from the repo served vie /code on that same site, but you can do it either way. > given my current workflow, embedded > docs just make sense to me. There’s no reason you can’t do both. You can allow people with login rights on the private code repo to see your *.md files as marked up by Fossil via embedded doc URLs while also using those same *.md files as input to the static HTML generation system. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
