Re: [Hpr] Static Site Generators - NOT a flat file CMS
Hi Carl, Just press record and read this as is. This is an episode in itself, and that is more likely to solicit feedback. Which you can cover in your third, show. (Your second been "how I got into tech " by way of introduction) (See what I did there :) ) Great idea by the way, and I would like to have a zip file of the directory structure to try it out. Thanks. -- Regards, Ken Fallon http://kenfallon.com http://hackerpublicradio.org/correspondents.php?hostid=30 On 2019-05-10 04:59, Carl Chave wrote: > Hello HPR Community! I'm Carl, but I've been using the name "sodface" > online since about 1996. I've been a computer hobbyist and an IT > worker for many years but I must admit that I'd become a bit > disinterested on the hobby side over the last few years but that > recently turned around when I decided to put Fedora on all my home > machines - it's really lit the fire again and I'm pretty happy about > that. I've been listening to HPR and other linux podcasts and I plan > on recording and submitting an episode for HPR soon. Saying that > before I do it is probably a jinx but I sort of wanted to reply to > this post because it's relevant to the episode I had planned and I > figured this email might also serve as my episode outline. > Additionally, maybe I'll get some feedback that will help shape the > episode or perhaps convince me not to bother with it at all! > > But to the point: > > I had an idea sometime around 2007 or so when I was a moderator and > "webmaster" of an online hardware forum to make my own template driven > site generator. At that time I was using a typical LAMP stack and did > my first proof of concept work with those tools. Just recently, I > discovered the althttpd web server, which is a 44k compiled binary > built from a single file of c code written by D. Richard Hipp, author > of Fossil and SQLite and much more. He actually uses it to serve the > Fossil and SQLite websites so far as I can tell, so it's been proved > in a fairly high traffic context. I started experimenting with it and > it made me revisit my template idea again and reshape it to > incorporate some of the features that althttpd brings to the table. > > Yawn, I know, the last thing the world needs is another website > generator / framework / CMS etc. but I don't really consider my > implementation any of those, it's really more just an idea and an > early stage proof of concept. I'm calling it "Symplate", for symbolic > linked templates. To give it a name feels a bit like I think it's > more than it is but it's easier and more fun to call it something, and > maybe giving it a name will help it to become something after all > these years. > > My design goals were roughly: > -- make it simple but flexible > -- make it feel like Unix / Linux > -- use familiar basic Linux utils > -- don't introduce anything new, like special syntax > -- stick to writing in plain html for the first iterations > -- make it portable, I'm trying to keep it compatible with the BusyBox > implementations of the core Linux utils > -- try to make it self documenting > > The "features" are: > -- global templates that are sym-linked to so changes to the template > are then reflected to all pages that link to them > -- the ability to insert additional templates into the normal flow of > page generation on a per page basis > -- the ability to override global templates as needed on a per page basis > -- Static or dynamic pages with shell variable and process > substitution in the templates > -- Virtual hosts for hosting multiple domains under a single server instance > > The implementation so far: > -- althttpd as a web server gives us virtual host directories, static > html and cgi script, and protected content directories in the public > web root. I'm using all these features in Symplate. > -- And althttpd can just be run on your local machine so you can work > locally and then tar up the directory and put it on the web server. > This might also work for HPR archival purposes? > -- A very basic page directory structure on the server looks like this: > [sodface@sodbook home]$ tree -l > . > ├── index.cgi -> ./-lc/thm/src.sh > └── -lc > ├── 015.tpl > ├── 075.tpl > ├── page.src > └── thm -> ../../-ln/thm/@thm > ├── res > │ ├── css > │ │ ├── modern-normalize.css > │ │ └── symplate.css > │ └── img > ├── src.sh > ├── sym.thm > └── tpl > ├── 000.tpl > ├── 010.tpl > ├── 020.tpl > ├── 030.tpl > ├── 040.tpl > ├── 050.tpl > ├── 060.tpl > ├── 070.tpl > ├── 080.tpl > ├── 090.tpl > ├── 100.tpl > └── 110.tpl > > This is what a home page might like. althttpd has a simple file > search logic it uses when trying to find a page to serve. If the > requested url is say, www.sodface.com/home/ (with a trailing sl
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Hi Mike, This needs to be a CMS for me, not a builder. I need to be able to update and access posts live from anywhere -- even if I only have my cell phone with me. So, I've basically excluded static site generators from the scope of considerationa sync / edit / build / push cycle isn't going to work for me...if it did, something like Hugo, Middleman, Nikola, etc. with Netlify would be an option. The three that are at the head of my list currently are Bolt, October and Grav. Ideally it would be good to see some benchmarks that show how each of these systems scale -- but I haven't been able to find anything like that. George On Mon, Apr 15, 2019, at 2:06 PM, Mike Ray wrote: > > > Nikola will build the index locally, and because it uses rsync to > upload, only new stuff ever gets uploaded. Not stuff that has not changed. > > > On 15/04/2019 19:59, SoundChaser wrote: > > In a bit of irony, I've just spent the last weekend digging around and > > researching CMS'es... I started with database drive systems, and then, > > thanks to LostInBronx and Klaatu (for running their gaming site on Grav) > > looking at flat file CMS's. > > > > The main issue with going the flat file approach is building index pages. > > Every time a new post (show) is added, all of the index pages would > > potentially need to be re-built. > > > > Personally, I am trying to decide what the best approach is for my > > situation where I have ~500 articles that will be growing after I move to a > > new system... A purely flat-file CMS might not be the best > > approach...potentially something that is more of a hybrid system like Bolt > > CMS might be better -- and it might fit HPR's needs too (it does use a > > database, but it only need SQLite, and not Maria or Postgres). > > > > I'd be interested in hearing any input others have on this topic. > > > > George > > > > On Mon, Apr 15, 2019, at 1:43 PM, Ken Fallon wrote: > >> > >> On 2019-04-03 20:36, Ken Fallon wrote: > >>> Hi All, > >>> > >>> Do any of you have a recommendation for a Static Site Generators that > >>> just publishes html files. > >>> > >>> For example takes a page, adds a header and footer from somewhere and > >>> publishes the combined page. > >>> > >>> > >> > >> Hi All, > >> > >> Thanks for the suggestions, which I am working through. > >> > >> The question was in relation to the Hacker Public Radio site, which is > >> essentially a LAMP based site that is entirely database driven. > >> > >> For the vast majority of the site this is unnecessary as the pages are > >> very static and change infrequently if ever. Those could be written to a > >> static html file without a problem. > >> > >> The general goal is that everything could be rsynced from a server to > >> your local machine and you would get access to a daily snapshot of the > >> entire website. This would allow us to have multiple mirrors of hpr > >> around the place in the event of another DDOS. > >> > >> So the php page > >> http://hackerpublicradio.org/eps.php?id=0013 > >> > >> would be written out to a directory accessible via a index.html page under > >> http://localhost/episodes/hpr13/ > >> > >> This fixes the problem of the episode bug, and removes the need for > >> a database query for the page. > >> > >> Unfortunately if ever the header and footer change we need to change > >> each and every exported page. HTML5 had a way to include pages together > >> fixing the problem but for some reason support for that has been dropped. > >> > >> So that is why I was thinking of a flat file CMS. The down side of that > >> is that if there is a change of header, then every single "rendered" > >> html page would need to be downloaded again because the change is > >> incorporated in every single page. > >> > >> However after thinking about it for a while, the people who are helping > >> out by doing this must have the technical expertise to rsync the site > >> locally. So it's safe to assume that they also can follow an instruction > >> page on how to set up a local lamp server. > >> > >> Then we could actually distribute a more or less static html website, > >> but use php to include the header and footer. That would not exclude the > >> need for a flat file cms, but the integration would be more focused on > >> the dynamic content. > >> > >> So I intend to setup a git repo with a index.html page that uses php to > >> include a header and footer. Trying to make the local site at least > >> usable if php or a webserver is not available. > >> > >> I'm not sure if this is even something that would be of interest to > >> people, but if it is, then I will put up links when I have something ready. > >> > >> -- > >> Regards, > >> > >> Ken Fallon > >> http://kenfallon.com > >> http://hackerpublicradio.org/correspondents.php?hostid=30 > >> > >> > >> ___ > >> Hpr mailing list > >> Hpr@hackerpublicradio.org > >> http://hackerpublicradio.org/mailman/li
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Nikola will build the index locally, and because it uses rsync to upload, only new stuff ever gets uploaded. Not stuff that has not changed. On 15/04/2019 19:59, SoundChaser wrote: > In a bit of irony, I've just spent the last weekend digging around and > researching CMS'es... I started with database drive systems, and then, thanks > to LostInBronx and Klaatu (for running their gaming site on Grav) looking at > flat file CMS's. > > The main issue with going the flat file approach is building index pages. > Every time a new post (show) is added, all of the index pages would > potentially need to be re-built. > > Personally, I am trying to decide what the best approach is for my situation > where I have ~500 articles that will be growing after I move to a new > system... A purely flat-file CMS might not be the best approach...potentially > something that is more of a hybrid system like Bolt CMS might be better -- > and it might fit HPR's needs too (it does use a database, but it only need > SQLite, and not Maria or Postgres). > > I'd be interested in hearing any input others have on this topic. > > George > > On Mon, Apr 15, 2019, at 1:43 PM, Ken Fallon wrote: >> >> On 2019-04-03 20:36, Ken Fallon wrote: >>> Hi All, >>> >>> Do any of you have a recommendation for a Static Site Generators that >>> just publishes html files. >>> >>> For example takes a page, adds a header and footer from somewhere and >>> publishes the combined page. >>> >>> >> >> Hi All, >> >> Thanks for the suggestions, which I am working through. >> >> The question was in relation to the Hacker Public Radio site, which is >> essentially a LAMP based site that is entirely database driven. >> >> For the vast majority of the site this is unnecessary as the pages are >> very static and change infrequently if ever. Those could be written to a >> static html file without a problem. >> >> The general goal is that everything could be rsynced from a server to >> your local machine and you would get access to a daily snapshot of the >> entire website. This would allow us to have multiple mirrors of hpr >> around the place in the event of another DDOS. >> >> So the php page >> http://hackerpublicradio.org/eps.php?id=0013 >> >> would be written out to a directory accessible via a index.html page under >> http://localhost/episodes/hpr13/ >> >> This fixes the problem of the episode bug, and removes the need for >> a database query for the page. >> >> Unfortunately if ever the header and footer change we need to change >> each and every exported page. HTML5 had a way to include pages together >> fixing the problem but for some reason support for that has been dropped. >> >> So that is why I was thinking of a flat file CMS. The down side of that >> is that if there is a change of header, then every single "rendered" >> html page would need to be downloaded again because the change is >> incorporated in every single page. >> >> However after thinking about it for a while, the people who are helping >> out by doing this must have the technical expertise to rsync the site >> locally. So it's safe to assume that they also can follow an instruction >> page on how to set up a local lamp server. >> >> Then we could actually distribute a more or less static html website, >> but use php to include the header and footer. That would not exclude the >> need for a flat file cms, but the integration would be more focused on >> the dynamic content. >> >> So I intend to setup a git repo with a index.html page that uses php to >> include a header and footer. Trying to make the local site at least >> usable if php or a webserver is not available. >> >> I'm not sure if this is even something that would be of interest to >> people, but if it is, then I will put up links when I have something ready. >> >> -- >> Regards, >> >> Ken Fallon >> http://kenfallon.com >> http://hackerpublicradio.org/correspondents.php?hostid=30 >> >> >> ___ >> Hpr mailing list >> Hpr@hackerpublicradio.org >> http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org >> >> >> *Attachments:* >> * signature.asc > > Faster moments spent > Spread tales of change > Within the sound > > > ___ > Hpr mailing list > Hpr@hackerpublicradio.org > http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org > -- Michael A. Ray Analyst/Programmer Witley, Surrey, South-east UK "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery https://cromarty.github.io/ http://eyesfreelinux.ninja/ http://www.raspberryvi.org/ ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
In a bit of irony, I've just spent the last weekend digging around and researching CMS'es... I started with database drive systems, and then, thanks to LostInBronx and Klaatu (for running their gaming site on Grav) looking at flat file CMS's. The main issue with going the flat file approach is building index pages. Every time a new post (show) is added, all of the index pages would potentially need to be re-built. Personally, I am trying to decide what the best approach is for my situation where I have ~500 articles that will be growing after I move to a new system... A purely flat-file CMS might not be the best approach...potentially something that is more of a hybrid system like Bolt CMS might be better -- and it might fit HPR's needs too (it does use a database, but it only need SQLite, and not Maria or Postgres). I'd be interested in hearing any input others have on this topic. George On Mon, Apr 15, 2019, at 1:43 PM, Ken Fallon wrote: > > On 2019-04-03 20:36, Ken Fallon wrote: > > Hi All, > > > > Do any of you have a recommendation for a Static Site Generators that > > just publishes html files. > > > > For example takes a page, adds a header and footer from somewhere and > > publishes the combined page. > > > > > > Hi All, > > Thanks for the suggestions, which I am working through. > > The question was in relation to the Hacker Public Radio site, which is > essentially a LAMP based site that is entirely database driven. > > For the vast majority of the site this is unnecessary as the pages are > very static and change infrequently if ever. Those could be written to a > static html file without a problem. > > The general goal is that everything could be rsynced from a server to > your local machine and you would get access to a daily snapshot of the > entire website. This would allow us to have multiple mirrors of hpr > around the place in the event of another DDOS. > > So the php page > http://hackerpublicradio.org/eps.php?id=0013 > > would be written out to a directory accessible via a index.html page under > http://localhost/episodes/hpr13/ > > This fixes the problem of the episode bug, and removes the need for > a database query for the page. > > Unfortunately if ever the header and footer change we need to change > each and every exported page. HTML5 had a way to include pages together > fixing the problem but for some reason support for that has been dropped. > > So that is why I was thinking of a flat file CMS. The down side of that > is that if there is a change of header, then every single "rendered" > html page would need to be downloaded again because the change is > incorporated in every single page. > > However after thinking about it for a while, the people who are helping > out by doing this must have the technical expertise to rsync the site > locally. So it's safe to assume that they also can follow an instruction > page on how to set up a local lamp server. > > Then we could actually distribute a more or less static html website, > but use php to include the header and footer. That would not exclude the > need for a flat file cms, but the integration would be more focused on > the dynamic content. > > So I intend to setup a git repo with a index.html page that uses php to > include a header and footer. Trying to make the local site at least > usable if php or a webserver is not available. > > I'm not sure if this is even something that would be of interest to > people, but if it is, then I will put up links when I have something ready. > > -- > Regards, > > Ken Fallon > http://kenfallon.com > http://hackerpublicradio.org/correspondents.php?hostid=30 > > > ___ > Hpr mailing list > Hpr@hackerpublicradio.org > http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org > > > *Attachments:* > * signature.asc Faster moments spent Spread tales of change Within the sound ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
On 2019-04-03 20:36, Ken Fallon wrote: > Hi All, > > Do any of you have a recommendation for a Static Site Generators that > just publishes html files. > > For example takes a page, adds a header and footer from somewhere and > publishes the combined page. > > Hi All, Thanks for the suggestions, which I am working through. The question was in relation to the Hacker Public Radio site, which is essentially a LAMP based site that is entirely database driven. For the vast majority of the site this is unnecessary as the pages are very static and change infrequently if ever. Those could be written to a static html file without a problem. The general goal is that everything could be rsynced from a server to your local machine and you would get access to a daily snapshot of the entire website. This would allow us to have multiple mirrors of hpr around the place in the event of another DDOS. So the php page http://hackerpublicradio.org/eps.php?id=0013 would be written out to a directory accessible via a index.html page under http://localhost/episodes/hpr13/ This fixes the problem of the episode bug, and removes the need for a database query for the page. Unfortunately if ever the header and footer change we need to change each and every exported page. HTML5 had a way to include pages together fixing the problem but for some reason support for that has been dropped. So that is why I was thinking of a flat file CMS. The down side of that is that if there is a change of header, then every single "rendered" html page would need to be downloaded again because the change is incorporated in every single page. However after thinking about it for a while, the people who are helping out by doing this must have the technical expertise to rsync the site locally. So it's safe to assume that they also can follow an instruction page on how to set up a local lamp server. Then we could actually distribute a more or less static html website, but use php to include the header and footer. That would not exclude the need for a flat file cms, but the integration would be more focused on the dynamic content. So I intend to setup a git repo with a index.html page that uses php to include a header and footer. Trying to make the local site at least usable if php or a webserver is not available. I'm not sure if this is even something that would be of interest to people, but if it is, then I will put up links when I have something ready. -- Regards, Ken Fallon http://kenfallon.com http://hackerpublicradio.org/correspondents.php?hostid=30 signature.asc Description: OpenPGP digital signature ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
It is a little heavy but pandoc can convert markdown (or just about any other format) into html while inserting header/footer text form a file. I use something like this: cat file.md | pandoc -M title:"Documents" -H ../markdown.header -f gfm -t html -o ~/Documents/docs.html >From the pandoc users guide: -H FILE, --include-in-header=FILE|URL Include contents of FILE, verbatim, at the end of the header. This can be used, for example, to include special CSS or JavaScript in HTML documents. -A FILE, --include-after-body=FILE|URL Include contents of FILE, verbatim, at the end of the document body (before the tag in HTML -B FILE, --include-before-body=FILE|URL Include contents of FILE, verbatim, at the beginning of the document body (e.g. after the tag in HTML On Wed, Apr 3, 2019 at 1:38 PM Ken Fallon wrote: > Hi All, > > Do any of you have a recommendation for a Static Site Generators that > just publishes html files. > > For example takes a page, adds a header and footer from somewhere and > publishes the combined page. > > > -- > Regards, > > Ken Fallon > http://kenfallon.com > http://hackerpublicradio.org/correspondents.php?hostid=30 > > ___ > Hpr mailing list > Hpr@hackerpublicradio.org > http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org > ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Ken, I currently have raspberryvi.org in a git repository on a local machine. There is one thing you need to know when setting up a Nikola site to stop the blog from being the front page. I can share that with you if you go for Nikola. Jekyll is used by github.io pages, but don't think it has a stand-alone mechanism for syncing to the remote server, if it is a server other than .github.io. Nikola is very good at that part, you can define multiple places to 'deploy' the site, like this: $ nikola deploy live %$ nikola deploy local I have raspberryvi.org set up so that I can sync it to an Apache server I have running here, or 'live' to poke it to the host server. eyesfreelinux.ninja is the same, and is on one of Josh's machines. The only thing I have found annoying about Nikola is that version changes tend to make the config.py br4eak and it can be necessary to rehash it. But I have now 'frozen' on an older version. There are also Docker images containing Nikola as well and I have considered switching to one of those, as I am now running almost everything in containers. Mike On 04/04/2019 18:21, Ken Fallon wrote: > Top posting for Mike. > > Thanks for all the feedback. > > Actually this is for HPR. I want to have the website statically > available as much as possible, so you can rsync or git clone the repos > and run your own site. > > If we consider each show to be it's own entity that is self contained > but fits in nicely with the rest of the site. > > Each show would be posted into it's own subdirectory which has a > index.html file and other media related to the show. > > Dave has been doing this for some time, see: > http://hackerpublicradio.org/eps/hpr2729/full_shownotes.html > > web-root/index.html > > web-root/episodes/hpr0001/index.html > web-root/episodes/hpr0001/image_for_show.jpg > web-root/episodes/hpr0001/example_script_1.bash > web-root/episodes/hpr0001/video.mp4 > > web-root/episodes/hpr0002/index.html > > Ideally I'd love be able to put the entire site on a usb stick and > browsing to it locally. > > file://opt/Hacker_Public_Radio/web-root/index.html > > So the source would be (for now) the HPR DB, but it could be a git repo, > were shows are pushed ?!? > > Anyway if you want to help out or follow along go to > https://gitlab.anhonesthost.com/ and set up an account. > > Ken > > > On 2019-04-04 19:05, jezra wrote: >> Ken, do you have a preferred input type for the source files? >> >> When it came time for me to pick a static site generator, I specifically >> looked for something that was based on HAML, Markdown, and SASS; because >> I absolutely did not want to write a bunch of raw HTML. >> >> >> jezra >> P.S. eventually I took the Fool's Route and rolled my own :) >> >> >> >> >> On 4/3/19 11:36 AM, Ken Fallon wrote: >>> Hi All, >>> >>> Do any of you have a recommendation for a Static Site Generators that >>> just publishes html files. >>> >>> For example takes a page, adds a header and footer from somewhere and >>> publishes the combined page. >>> > > > > ___ > Hpr mailing list > Hpr@hackerpublicradio.org > http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org > -- Michael A. Ray Analyst/Programmer Witley, Surrey, South-east UK "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery https://cromarty.github.io/ http://eyesfreelinux.ninja/ http://www.raspberryvi.org/ ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Top posting for Mike. Thanks for all the feedback. Actually this is for HPR. I want to have the website statically available as much as possible, so you can rsync or git clone the repos and run your own site. If we consider each show to be it's own entity that is self contained but fits in nicely with the rest of the site. Each show would be posted into it's own subdirectory which has a index.html file and other media related to the show. Dave has been doing this for some time, see: http://hackerpublicradio.org/eps/hpr2729/full_shownotes.html web-root/index.html web-root/episodes/hpr0001/index.html web-root/episodes/hpr0001/image_for_show.jpg web-root/episodes/hpr0001/example_script_1.bash web-root/episodes/hpr0001/video.mp4 web-root/episodes/hpr0002/index.html Ideally I'd love be able to put the entire site on a usb stick and browsing to it locally. file://opt/Hacker_Public_Radio/web-root/index.html So the source would be (for now) the HPR DB, but it could be a git repo, were shows are pushed ?!? Anyway if you want to help out or follow along go to https://gitlab.anhonesthost.com/ and set up an account. Ken On 2019-04-04 19:05, jezra wrote: > Ken, do you have a preferred input type for the source files? > > When it came time for me to pick a static site generator, I specifically > looked for something that was based on HAML, Markdown, and SASS; because > I absolutely did not want to write a bunch of raw HTML. > > > jezra > P.S. eventually I took the Fool's Route and rolled my own :) > > > > > On 4/3/19 11:36 AM, Ken Fallon wrote: >> Hi All, >> >> Do any of you have a recommendation for a Static Site Generators that >> just publishes html files. >> >> For example takes a page, adds a header and footer from somewhere and >> publishes the combined page. >> ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Ken, do you have a preferred input type for the source files? When it came time for me to pick a static site generator, I specifically looked for something that was based on HAML, Markdown, and SASS; because I absolutely did not want to write a bunch of raw HTML. jezra P.S. eventually I took the Fool's Route and rolled my own :) On 4/3/19 11:36 AM, Ken Fallon wrote: Hi All, Do any of you have a recommendation for a Static Site Generators that just publishes html files. For example takes a page, adds a header and footer from somewhere and publishes the combined page. ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Hi Ken: If your server supports Server Side Includes (SSI) then you can add comments to the top and bottom of your pages to include a header and footer. I was doing that for a static site for a while (but then got sucked into the WordPress morass). eg. --> The insert.hti file contains the HTML code I want in the header. If I ever change the contents of that file, then all the pages which have the 'include virtual' comment will update too. Note that some servers don't like the space between the comment indicator and the 'include' command, so they want which I find ugly... I use the .hti extension as an indicator that it's an HTML "include" file, not a complete HTML file with sections. --Bob. On 2019-04-03 2:36 p.m., Ken Fallon wrote: Hi All, Do any of you have a recommendation for a Static Site Generators that just publishes html files. For example takes a page, adds a header and footer from somewhere and publishes the combined page. ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org -- Bob Jonkman Phone: +1-519-635-9413 SOBAC Microcomputer Services http://sobac.com/sobac/ Software --- Office & Business Automation --- Consulting GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Ken, I've read your message, and seen many of the responses (personally I like Nikola too -- but I've not used it for any real projects). But, I'm slightly confused - your subjects says: "NOT a flat file CMS". If you don't need something that will apply CSS styling, and build a navigation framework, then why would you need a site generator? If you are just adding a header and footer to a bunch of files couldn't a simple script just concatenate the files for you... IE something like: for i in *.html do cat header >> out/$i cat $i >> out/$i cat footer.html >> out/$i done / Insert code to push the pages to your server here ***/ George On Wed, Apr 3, 2019, at 1:38 PM, Ken Fallon wrote: > Hi All, > > Do any of you have a recommendation for a Static Site Generators that > just publishes html files. > > For example takes a page, adds a header and footer from somewhere and > publishes the combined page. > > > -- > Regards, > > Ken Fallon > http://kenfallon.com > http://hackerpublicradio.org/correspondents.php?hostid=30 > > > ___ > Hpr mailing list > Hpr@hackerpublicradio.org > http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org > > > *Attachments:* > * signature.asc ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
That's a great option. I've used hugo, snd i recall liking it but yesh i think it had weirdness with markdown. If Jekyll avoids that, id take a look at that. On 4 April 2019 8:25:27 AM NZDT, "Claes Wallin (韋嘉誠)" wrote: >On Thu, Apr 4, 2019, 02:38 Ken Fallon wrote: > >> Hi All, >> >> Do any of you have a recommendation for a Static Site Generators that >> just publishes html files. >> >> For example takes a page, adds a header and footer from somewhere and >> publishes the combined page. >> > >I think most of them would be able to be used like that. The ones I >have >come close to are ikiwiki, Jekyll, Hugo and Styx, and basically, >although >they ship with more advanced frameworks, themes and functionality, ans >support various markups, in the end it boils down to what you >described. >Header, body, footer is simply a barebones theme. > >Probably Jekyll is the simplest, with the least configuration to do. >And >HTML is valid markdown, so you don't have to worry about that either. >IIRC >it doesn't support markdown syntax inside html syntax, so you wouldn't >even >need to worry about any unexpected interference. > >-- > /c > >> ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
On Thu, Apr 4, 2019, 02:38 Ken Fallon wrote: > Hi All, > > Do any of you have a recommendation for a Static Site Generators that > just publishes html files. > > For example takes a page, adds a header and footer from somewhere and > publishes the combined page. > I think most of them would be able to be used like that. The ones I have come close to are ikiwiki, Jekyll, Hugo and Styx, and basically, although they ship with more advanced frameworks, themes and functionality, ans support various markups, in the end it boils down to what you described. Header, body, footer is simply a barebones theme. Probably Jekyll is the simplest, with the least configuration to do. And HTML is valid markdown, so you don't have to worry about that either. IIRC it doesn't support markdown syntax inside html syntax, so you wouldn't even need to worry about any unexpected interference. -- /c > ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
Re: [Hpr] Static Site Generators - NOT a flat file CMS
Podwrite, which i use for gnuworldorder and Commons & Chronicles, does exactly that. Its UI or UX or whatever is a little rough, but im happy to walk you through it. On 4 April 2019 7:36:34 AM NZDT, Ken Fallon wrote: >Hi All, > >Do any of you have a recommendation for a Static Site Generators that >just publishes html files. > >For example takes a page, adds a header and footer from somewhere and >publishes the combined page. > > >-- >Regards, > >Ken Fallon >http://kenfallon.com >http://hackerpublicradio.org/correspondents.php?hostid=30 ___ Hpr mailing list Hpr@hackerpublicradio.org http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org