141–150 of 241 posts
What are people using for hosting? I've thought about using github pages, but css ended up being severely limited.
Earlier quoted context omitted.
It's 2016, if you use a non-JS enabled HTML client you better be used to the breakage.
Sure I'm used to closing the page, because really screw you if you can't display half a dozen paragraphs of text without JS.
Don't let the door hit you on your way out
Than spend time catering to outliers...
Sort of related and shameless plug but I'm building a "comments as a service" application that isn't disqus. My first target market is static sites. Check it out here: http://www.remarkbox.com
Also sort of a related, shameless plug-- I've been working on Formingo ( https://www.formingo.co ), a form processing service for static sites so you can receive your form submissions directly to your email without the need for server side code or your own backend. I've actually had a couple people ask me about comment systems that were an alternative to (and more simple than) Disqus, so it's cool to see someone work…
/submit/12345
Then your system looks up 12345 and sees it means john@example.com.
Anything that supports .docx documents?
I crave simplicity in my life right now and am using markdeep: https://casual-effects.com/markdeep/ I write my documents in markdown and add this tag at the end of my document I "publish it" by copying it to my server and renaming it .html * note: To get started, here is the suggested starter document: https://casual-effects.com/markdeep/starter.md.html
I'm not sure if this counts as a "static website", since the page is not delivered exactly as stored . It requires JavaScript to actually renders the page, which seems like an overkill.
The main question for me is comments. I don't want to use something like Disqus, and to require something like Discourse would cancel the whole point of having a static site generator that I can host on Github Pages or Gitlab pages. Ideally, what I would like to do is to have an hackernews post automatically generated for each post, and to redirect people to the HN post if they want to comment, but I am not sure that…
One of the design goals is to _not_ be disqus.
Sort of related and shameless plug but I'm building a "comments as a service" application that isn't disqus. My first target market is static sites. Check it out here: http://www.remarkbox.com
Also sort of a related, shameless plug-- I've been working on Formingo ( https://www.formingo.co ), a form processing service for static sites so you can receive your form submissions directly to your email without the need for server side code or your own backend. I've actually had a couple people ask me about comment systems that were an alternative to (and more simple than) Disqus, so it's cool to see someone work…
Earlier quoted context omitted.
This statement caught my attention in the article: > It is optimized for speed (Hugo sites can be built in milliseconds) Is that true, or does it just happen to be fast? It seems to me that the performance of a static site generation is irrelevant, and thus time spent on this is really wasted effort. I don't care if it takes several minutes to build.. it'll happen on the CI server in the background, and so long as th…
> It seems to me that the performance of a static site generation is irrelevant, and thus time spent on this is really wasted effort. Another consideration is pages which take a long time to render. When I'm writing about code (which is a lot!) I use a literate programming style, so that code snippets on a page can be executed and have their output embedded in the HTML. This ensures that the code I'm discussing actua…
The main problem for me is that the absolute majority of them target blogs and if you try to adapt them for a more complicated website you gonna dive very deep inside the code or continue constant search. Now I look at hugo as it seems to be a more general-purpose tool that allows to play with structure and content types.
Edit: Just to add, I have multiple needs here that aren't enumerated, one of which is full translation support for the source content to support multi-linguale/multi-locale sites.