51–60 of 119 posts
Absolutely love Jekyll and GitHub Pages for hosting project documentation and personal websites. Just wish GH Pages would support SSL. :(
The cost is probably negligible for typical blogs, portfolios, etc. Amazon's new free certificate service might also be a bonus.
OK, a standard dialect of Markdown. In the beginning was RUNOFF from MIT, which originally had about the power of Markdown. More features were added, and it became nroff, then troff, the ditrofff, and macro systems were added on top of it. It became too hard to use for casual work. Then there was TeX, which was a saner approach to what troff did. Macro systems were added on top of it. It became too hard to use for ca…
[1]: https://daringfireball.net/projects/markdown/syntax (see "Inline HTML")
Good news. We're using Jekyll 3 at Static Website Manager [1], but we're moving to support older specific versions as well as custom Gemfiles. [1]: https://www.staticwebsitemanager.com Are there any features the community would love to see offered in a Jekyll-based CMS?
My Jekyll work flow tends to involve: Write a blog. Publish. Recognise horrid markdown bugs. Go and fix already published blog. I appreciate there are better workflows, but as a Windows user I'm not going to install Jekyll to publish locally and test, nor is my blog big enough to justify a test environment. The "drafts" feature basically just takes a draft and publishes it. What would really make life easier is it th…
Whenever I need to make a little change I can edit locally in my editor of choice, commit and push to SWM where I can preview the changes before merging to my production bucket (all without installing Jekyll locally).
If I don't have my machine, I can also just login, edit the text and then follow the same preview/merge to deploy workflow.
Good news. We're using Jekyll 3 at Static Website Manager [1], but we're moving to support older specific versions as well as custom Gemfiles. [1]: https://www.staticwebsitemanager.com Are there any features the community would love to see offered in a Jekyll-based CMS?
----page----
# Title
>
>
>
Useful if you have lots of sections that you want to combine in different ways, and update them all at the same time...
Earlier quoted context omitted.
That's.. not the same.
In case SSL support is essential to you please know that we'll looking to bring it to _GitLab_ Pages in a few months https://gitlab.com/gitlab-org/gitlab-ee/issues/134
OK, a standard dialect of Markdown. In the beginning was RUNOFF from MIT, which originally had about the power of Markdown. More features were added, and it became nroff, then troff, the ditrofff, and macro systems were added on top of it. It became too hard to use for casual work. Then there was TeX, which was a saner approach to what troff did. Macro systems were added on top of it. It became too hard to use for ca…
Markdown specifically allows and recommends inline HTML for anything more complex than writing prose [1] [1]: https://daringfireball.net/projects/markdown/syntax (see "Inline HTML")
Good news. We're using Jekyll 3 at Static Website Manager [1], but we're moving to support older specific versions as well as custom Gemfiles. [1]: https://www.staticwebsitemanager.com Are there any features the community would love to see offered in a Jekyll-based CMS?
Earlier quoted context omitted.
I'm working on a static hosting service. We are working on SSL and making that easy. Would you be interested in trying the beta? http://www.statichosting.co
Nice. One way you could distinguish your service from all other options (S3, Github Pages), is to support the history API for single page webapps. I'm hosting a static site on EC2 instead of S3 because I need URLs to fallback to index.html. Literally for this one nginx rule: location / { try_files $uri /index.html =404; } Also, I'd like to try the beta of your service, just signed up. My email is in my profile. Thank…
OK, a standard dialect of Markdown. In the beginning was RUNOFF from MIT, which originally had about the power of Markdown. More features were added, and it became nroff, then troff, the ditrofff, and macro systems were added on top of it. It became too hard to use for casual work. Then there was TeX, which was a saner approach to what troff did. Macro systems were added on top of it. It became too hard to use for ca…