Static Site Generators
staticsitegenerators.net
staticsitegenerators.net
"Site about statis site generators taken down by static site generator scaling issues."
The downtime was caused by the YAML file having invalid syntax so it would not parse. Whenever a modification to the YAML file is made, a github post hook is sent to the server telling it to regenerate the website.
Normally this happens smoothly without anyone noticing any downtime, while maintaing awesome performance.
In this case because of the bad YAML, DocPad crashed, as it was told to, and the logs showed the error.
I was sleeping at the time so did not notice the issue.
The latest version of the website now handles this gracefully, using the latest successful data if the YAML is bad, as well as showing an error message.
Now I'd been building websites for a while, so I'd already gone organically through the whole 'hey let's use php to cut my pages up into reusable modules', 'I can automate this thing here', 'plugins are awesome!', and 'hey what's this MVC thing'.
But for people starting from less, a static site generator might be more explicit and less complex to learn with.
The mere fact that there's often a 'build' step that converts your stuff to plain html, javascript and css, I find, makes beginners feel like they understand things a little better.
http://web.archive.org/web/20010519223318/http://users.ox.ac...
I think all the content was in handwritten HTML, but the generator knew enough to be able to do the navigation links and sitemap and so on.
That way search and comments (and especially moderation for comments) would be easier to handle, but still it would be easy on the server.
For my own site I created something like this, https://github.com/Harri/Spage , but instead of DB, I used another set of flat files (serialized arrays containing the page content + some meta data) for management purposes.
Both Drupal and Wordpress have modules/plugins that produce static pages:
* Drupal: https://drupal.org/project/boost
* Wordpress: https://wordpress.org/plugins/wp-super-cache/
They're both quite mature and the standard practice for websites that get a lot of anonymous traffic using their respective CMSes.
An alternative (or supplement) to them would be something like Varnish: https://www.varnish-cache.org
http://leonstafford.com/wordpress-static-html-output-plugin/
https://github.com/stucchio/Stiletto
No idea if it works with the latest django, I haven't used it since roughly 1.4.
http://github.com/skx/e-comments/
As used on http://tweaked.io/
The hardest part is that we are going to have a build server that rebuilds the stale parts of the site every hour or so - I don't think that's been done with Middleman before, so we're building that from scratch.
I'll post the details on https://tech.bellycard.com when we're done with it.
It renders to static files by default (as well as compiling+compressing assets etc) and you can define any number of separate outputs in multiple formats (e.g. HTML, JSON, Javascript, XML, RSS etc) which will also be rendered at the same time.
Plus a whole world of other features, some I consider to be relatively revolutionary. </IMHO>
It works well but lacks, (really, really seriously) lacks, documentation.
So you get the best of both worlds.
The CMS is a crutch. It has its place in certain organizations. But it is overkill for many use cases.
In truth, however, we shouldn't be pitting the SSG against the CMS. I believe the next leap of content creation is a mixture of both SSG and classical CMS. Check out the following links:
https://github.com/thyb/contentify https://www.contentful.com/ https://prismic.io/
There is a convergence about to happen between "dynamic" content and the SSG. It could be called CMS as an API.
https://pythonhosted.org/Frozen-Flask/ https://github.com/bendoan/bendoan.me
That's probably the easiest way to get Haskell up and running. Then it's a simple matter of using cable to install other libraries, including Hakyll.
Either way I will revisit this now there is a new Debian stable, and I can install the package natively without using cabal.
Last weekend, she asked for help with her website, and I was shocked to find out they still look like they're out of the late 90's. She does all of her editing with a 2006 copy of dreamweaver in WYSIWYG mode.
I'm a huge fan of Jekyll, but she is scared by the Liquid/markdown syntax. I was thinking of moving her to Visual Studio for Web or KompoZer. Anyone know a better HTML editor with WYSIWYG mode and modern, beautiful templates or can recommend one of these all 243 generators?
We're launching in about a month. Basically, we're a static site generator with a CMS. You don't even use YAML or front-matter. Just build your forms with a local GUI, then pass yoursite.com/cms/ over to your Mom so she can edit in a wysiwyg (or markdown...whatever). Design with normal css/html and Django style templating.
I built it because I loved static site generators (some great tools in that list), but they were all worthless for me as soon as I needed to pass the site off to non-hacker friends. I wanted it to be easy on me and easy on them. Using firebase and ember, we were able to load the entire CMS off a static server (we still need a server to regenerate on changes though).
And before you ask, yes we're trying to figure out how to make it self-hostable. It's a little harder for us, since we use a bunch of separate services (firebase, elastic search, google image resizing...etc) to make it so you don't need to install much locally, just Node. Small team at the moment, trying to avoid VC investment and went straight to Kickstarter.
For everyone else who just likes SSGs and don't need a CMS, I'm a big fan of Harp and Cactus. The later because I came from a Django background.
If you're looking at a WYSIWYG from a design standpoint you might like something like http://macaw.co/
The HTML it spits out is basically a bunch of absolutely-positioned divs, apparently in whatever order things were edited in. That means that a box, a headline within that box and text following that headline are all in completely separate locations within the file. Completely unmaintainable unless you also have their software for further edits.
It's currently offline but I can send you the code.
Looks like Mailpin (http://mailp.in) is what your mother needs.
Does she know how to send email? If yes, then she just sends a mail to p@mailp.in, and the mail she sends become a web page like this: http://mailp.in/c8cN1BEb
1) http://lifehacker.com/mailpin-creates-quick-easy-hosted-web-...
Rather than offering extensive formatting options, it supports blocks for different types of content. This should make it easier to integrate into well-designed template without fear that the user will break it by abusing formatting, while still allowing to arrange the content freely.
It seems like it would be easy to integrate it with some simple back-end:
> The content of the editor is stored as markdown inside a JSON object, with the structure and the contents of the post serialized inside of it.
And, albeit it's not strictly on-topic, seems like you might be interested in just using a website builder. I don't know about pricing in this area of business, though. From the top of my head I remember http://www.weebly.com is one of these.
Personally I like and use `lazygal`: http://sousmonlit.zincube.net/~niol/playa/oss/projects/lazyg... Source: https://bitbucket.org/niol/lazygal
It's live and maintained. I also contributed some code fixes and theme to it.
It's been about 10 years since I last used it, but looks like it's still basically the same thing; reads your photos directory, creates html pages with thumbnails and links to bigger pictures based on the directory structure. Can display EXIF data next to the images if you want.
But it's pretty simple. You just have to recursively go over the folder, and get each photo. Make sure there is a thumbnail, and build your HTML.
Some generators (e.g. gostatic) can track changes and dependencies, rebuilding just what changed.
:p
I have some concerns about its architecture in that it's too integrated with git repositories, but it looks like a great place to start from.
http://pelican.readthedocs.org/en/latest/plugins.html#how-to...
Same idea, but staticgen.com is a little easier to navigate but don't think it's quite as comprehensive.
Stay tuned :)
https://github.com/jaspervdj/static-site-generator-comparison/
as an underlying list, too? Maintaining a listing is pretty tedious with all the SSGs out there. I can set up web hooks and whatever to push to your servers if the listing changes.https://github.com/greghendershott/frog
Fun little list :D
- Aren't Jekyll and Octopress basically the same thing?
- Really impressed at how fast Metalsmith is growing. Might have to give it a try soon.
- For now I give my vote to Middleman.
I don't know why but using a single binary is awesome!
https://github.com/wtracy/hablog
That said, it was only ever intended as a toy project, so it probably doesn't belong here.
http://kephra.de/blog/Make_here_CMS.html http://kephra.de/src/Make-here-CMS-shar.txt
The idea is, that a minimal static site generator can be done by a recursive Makefile and a here script.
https://shop.fogcreek.com/default.asp?sCategory=CITYDESKINDE...
The only big difference that makes Zas stand out is its more Unix-like spirit in how it handles extension through commands as plugins.
I'll check the list in the future and try to adquire some more "skills" for Zas.
Specifically a online-CMS that generates static html uploaded to a CDN. The target market is businesses who need to know their content is "uncrashable" and "infinitely scalable". The price point would be >$100/mo.
Get in touch with me if you are interested in that idea.
So yes, this is a feature and not a product as evinced by the numerous plugins and projects that take existing dynamic web application software and can produce static sites (Flask Freeze, Drupal's plugin, I think even WordPress has one).
[EDIT] Which means, what's to stop the existing "site builder" companies from doing the same? They don't sell the feature (static builder from a dynamic site), they sell the product (build yourself a site), and people buy it. The "background benefit" is a slightly faster site and who does that really matter to? Not the customer. The service - reduction of bandwidth and server resources; the could easily introduce the feature, cut resources, and keep the margin.
The technical side is not particularly difficult aside from dealing syncing and maybe failover. What is trickier is probably the CMS side because building a CMS is like the definition of feature creep. Eventually people want/get every feature under the sun, even if that doesn't really scale.
You probably have an interesting business there, but managing customer expectations and finding the happy balance in terms of investment is tricky.
Also, the customer acquisition side of the business is somewhat tough, but worth solving.
Good luck!
http://imakesnowflakes.com/vodka-introduction.html
I made it because I found the existing ones unnecessarily complicated, for doing something trivial as converting a bunch of markdown files into html.
I rarely need the full featureset of Markdown and would prefer a simple editor that gets me half way there, while still ultimately outputting Markdown for storage/use in something like a static site generator.
It's a bit primitive, but I guess that's the point. Be sure to hit the "Return markdown text" checkbox.
¹ https://github.com/rhythmus/markdown-resources/blob/master/m...
² https://github.com/quilljs/quill/issues/74#issuecomment-4294...
https://github.com/jaspervdj/static-site-generator-comparison/commit/610b1b35742a281a84bfb18cf026842d1b92bf67 https://github.com/jaspervdj/static-site-generator-comparison/commit/96f23ed30db97067feb42b2f9100ec48c2596eb6http://codecondo.com/7-static-site-generators-for-building-w...
only featured stuff that the majority of developers use.
I suppose it wouldn't be to hard to use any of the existing static site generators and either 'repackage' them with specific assumptions, or write a module that implements them...
It's a static site generator all made with Ruby on Rails and AngularJS for the front.
http://staticgen.com is a decent alternative
(Note: I use Ultra Simple Site Maker for my own website, but I wouldn't recommend you do at the moment. It's not very flexible right now.)
Does anyone else use it?