I like the idea of Jekyll, but I don't like Jekyll itself (I'm pretty sure I have a severe allergic reaction to Ruby).
Something I have yet to see but that I think would be perfect would be a client-side single-page-app that served as a s3-backed static site generator.
Navigate to MyStaticWebsiteGenerator.io (or download it, or self-host it, or clone the repo, it's a simple js-based SPA preferably packaged as a stand-alone ".html" file). AWS credentials (IAM of course) are either stored encrypted in LocalStorage (or Websql or indexeddb or who knows what we are supposed to be using) or queried on demand. It would interact with s3 directly (there is a browser based js api for aws) to manage and modify files directly (multi-user contention and eventual consistency be damned - for small sites it's simply not an issue), and when appropriate, generate/regenerate the static files. Because everything is done client side, the webserver itself never sees or cares about your aws credentials.
Clearly, being a "static site generator", only the admin interface would be JS based, the user-facing generated content would be static. [For some reason every post i've seen doing something remotely similar wants their mostly static content to be rendered at runtime in their js app???]
With prosemirror under active development you should soon be able to have a simple js based WYSIWYG rich text editor that generates nice clean Markdown to feed into your template of choice (à la Jekyll). Your end-users don't need to know markdown or care, they just get a fairly basic rich text editor. Give them a simple interface for defining a website's structure and bob's your uncle.
Sometimes I feel like I'm the only person who thinks this way.
Something I have yet to see but that I think would be perfect would be a client-side single-page-app that served as a s3-backed static site generator.
Navigate to MyStaticWebsiteGenerator.io (or download it, or self-host it, or clone the repo, it's a simple js-based SPA preferably packaged as a stand-alone ".html" file). AWS credentials (IAM of course) are either stored encrypted in LocalStorage (or Websql or indexeddb or who knows what we are supposed to be using) or queried on demand. It would interact with s3 directly (there is a browser based js api for aws) to manage and modify files directly (multi-user contention and eventual consistency be damned - for small sites it's simply not an issue), and when appropriate, generate/regenerate the static files. Because everything is done client side, the webserver itself never sees or cares about your aws credentials.
Clearly, being a "static site generator", only the admin interface would be JS based, the user-facing generated content would be static. [For some reason every post i've seen doing something remotely similar wants their mostly static content to be rendered at runtime in their js app???]
With prosemirror under active development you should soon be able to have a simple js based WYSIWYG rich text editor that generates nice clean Markdown to feed into your template of choice (à la Jekyll). Your end-users don't need to know markdown or care, they just get a fairly basic rich text editor. Give them a simple interface for defining a website's structure and bob's your uncle.
Sometimes I feel like I'm the only person who thinks this way.