4 ms·

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

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 https://www.staticwebsitemanager.com Are there any features the community would love to see offered in a Jekyll-based CMS?

technion 11y ago
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 the drafts feature would "publish this blog, but don't update the front page to link it". I could look at it knowing the URL, and get it right first.
- JorgeGT 11y ago
  As a fellow Windows user (at least at home) with a Jekyll blog deployed on GitHub pages, I would recommend using a web IDE such as c9.io or koding.com. They are little VPSs with sudo access (and a private web server) so you can test "locally" there and then git push once you're ironed out bugs. In your Windows machine you only need a web browser.
- tedkimble 11y ago
  That's my main use case. I've got my personal blog [1] setup as a Static Website Manager repository and connected to my personal AWS S3 bucket. 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. [1]: http://www.theodorekimble.com http://www.theodorekimble.com
- WorldMaker 11y ago
  At least Jekyll 3 is much, much easier to install in Windows than 2 was.
bnj 11y ago
Something that's possible with some static engines but not really catered to is the ability to include the contents of other markdown files into a page- ----page---- # Title << contents of /markdown/file >> << second file >> << third file >> Useful if you have lots of sections that you want to combine in different ways, and update them all at the same time...
mojavelinux 11y ago
AsciiDoc support would be brilliant. There's a gem for that. (See https://github.com/asciidoctor/jekyll-asciidoc https://github.com/asciidoctor/jekyll-asciidoc). Many people ask about it. GitHub has been reluctant to adopt.
pizn 11y ago
Oh...I like this. I code a project that can help me to write and publish my Jekyll blog on Github. https://github.com/pizn/eevee https://github.com/pizn/eevee

technion 11y ago

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 the drafts feature would "publish this blog, but don't update the front page to link it". I could look at it knowing the URL, and get it right first.

JorgeGT 11y ago
As a fellow Windows user (at least at home) with a Jekyll blog deployed on GitHub pages, I would recommend using a web IDE such as c9.io or koding.com. They are little VPSs with sudo access (and a private web server) so you can test "locally" there and then git push once you're ironed out bugs. In your Windows machine you only need a web browser.
tedkimble 11y ago
That's my main use case. I've got my personal blog [1] setup as a Static Website Manager repository and connected to my personal AWS S3 bucket. 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. [1]: http://www.theodorekimble.com http://www.theodorekimble.com
WorldMaker 11y ago
At least Jekyll 3 is much, much easier to install in Windows than 2 was.

bnj 11y ago

Something that's possible with some static engines but not really catered to is the ability to include the contents of other markdown files into a page- ----page---- # Title << contents of /markdown/file >> << second file >> << third file >> Useful if you have lots of sections that you want to combine in different ways, and update them all at the same time...

mojavelinux 11y ago

AsciiDoc support would be brilliant. There's a gem for that. (See https://github.com/asciidoctor/jekyll-asciidoc https://github.com/asciidoctor/jekyll-asciidoc). Many people ask about it. GitHub has been reluctant to adopt.

pizn 11y ago

Oh...I like this. I code a project that can help me to write and publish my Jekyll blog on Github. https://github.com/pizn/eevee https://github.com/pizn/eevee