GitHub pages is now running Jekyll 3
101–110 of 119 posts
Re: GitHub pages is now running Jekyll 3
#102Earlier quoted context omitted.
Is GitLab pages going to be available to non-enterprise gitlab.com users? If not, may I respectfully request that it is?
No way. Asking for free stuff when you don't need it or can buy it cannot be respectful.
No one was asking for it to be free. Currently it's tracked as a feature for enterprise users. They have 3 paid plans for non-enterprise users, and I'm certain many of those non-enterprise folks would love it.
Re: GitHub pages is now running Jekyll 3
#103Absolutely love Jekyll and GitHub Pages for hosting project documentation and personal websites. Just wish GH Pages would support SSL. :(
Hey, you can use https://kloudsec.com to do that. You can even get a custom domain with SSL (via LetsEncrypt) going for it. Here's what you need to do: * Set a CNAME record for your Github Page: https://help.github.com/articles/setting-up-a-custom-domain-... * Add custom domain to Kloudsec * Update custom domain to Kloudsec's Anycast CDN IP * Enable "One-click Encryption" plugin to automatically provision a LE cert.…
When I ran into a small issue, I used the instant chat applet inside the Kloudsec control panel, and Steven quickly discovered the problem (I simply needed to remove the two A records pointing to GitHub pages, leaving only the Kloudsec A record).
Everything is working flawlessly so far, in regards to having TLS/SSL for custom domain hosted on GitHub pages. I especially like the option to enable HSTS for the domain's SSL. I wish GitHub Pages' own SSL on username.github.com offered that option.
All in all, painless plus quick, and without the unclean feeling that comes with Cloudflare's free SSL option. Additionally, I'm impressed with Steven's quick and quality assistance via chat and email.
edit: I've now noticed that there are large blocks of Javascript injected into my one-page test website. Ostensibly for the Speed Booster CDN plugin; I'll update after confirming the JS is gone upon disabling all plugins aside from the One-Click Encryption plugin.
edit2: Confirmed. Speed Booster plugin was source of JS injection. I suppose that's the drawback to a CDN who doesn't also host your DNS. Ironically, due to test site being small and static, disabling the Speed Booster plugin to remove all the JavaScript increased page load speeds.
Still, this doesn't detract from Kloudsec's simple deployment of LetsEncrypt SSL certificates for custom domains hosted on GitHub pages.
Re: GitHub pages is now running Jekyll 3
#104Earlier quoted context omitted.
"Also, the silly space-at-the-end for line breaks." I thought it was two spaces at end of line for a line break. Or did the one-space-at-end-of-line argument win?[1] [1] http://meta.stackexchange.com/questions/40976/what-is-the-re...
I... never knew this. And since my editor strips newlines on save (and no, I will not turn that feature off), I guess I can't use it. Oh well. It kind of scares me that I might inadvertently strip the newlines out of someone else's markdown that I'm editing, though.
Intriguing: significant white space on the right-hand side. At least you can see the significant whitespace in Python.
I also have my editor configured to strip trailing whitespace but also to highlight it. People can be very sloppy leaving (insignificant) whitspace lying around in code.
Re: GitHub pages is now running Jekyll 3
#105Good 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…
Re: GitHub pages is now running Jekyll 3
#106Earlier quoted context omitted.
If your editor supports editorconfig[1], you could set it to not strip newlines for .md files. :) [1] http://editorconfig.org/
But I want to strip newlines from .md files.
There were some systems back in the DOS/early UNIX era which had significant EOL whitespace. Spaces at the end of a line are still significant following a "\" in shell files. Some early word processors under DOS had significant whitespace at EOL, but tended to display something like a paragraph mark when it mattered.
Python had tab/space trouble at beginnings of lines, but the compiler was finally fixed so that it emits an error if tabs and spaces are mixed in a way which makes indentation visually ambiguous. That was a neat solution to the problem.
Leading tabs in makefiles were a mistake. The author of "make" once wrote that he put that in, and then, the next day, realized it was a bad idea. But he already had a user base of three users and didn't want to change it and break their code.
I thought this idea was dead and buried. Sometimes, they come back.
Re: GitHub pages is now running Jekyll 3
#107With this change, Github has made Rouge the only (and mandatory?) highlighter supported. This is a problem for sites that disable Jekyll highlighting in favor of using something like highlight.js. It appears right now that there is no way to disable Rouge which is causing conflicts with my sites that use javascript highlighting.
FYI: You can disable Rouge - just set the Kramdown highlighter to nothing in the Jekyll _config.yml. That's all.
You are attempting to use the 'none' highlighter, which is currently unsupported on GitHub Pages. Your site will use 'rouge' for highlighting instead.
Re: GitHub pages is now running Jekyll 3
#108Earlier quoted context omitted.
But I want to strip newlines from .md files.
That's why significant end of line whitespace is a terrible design feature. You can't see it. It might get deleted accidentally. There were some systems back in the DOS/early UNIX era which had significant EOL whitespace. Spaces at the end of a line are still significant following a "\" in shell files. Some early word processors under DOS had significant whitespace at EOL, but tended to display something like a parag…
, and you add an extra blank line to denote a paragraph break.
Re: GitHub pages is now running Jekyll 3
#109Earlier quoted context omitted.
That's why significant end of line whitespace is a terrible design feature. You can't see it. It might get deleted accidentally. There were some systems back in the DOS/early UNIX era which had significant EOL whitespace. Spaces at the end of a line are still significant following a "\" in shell files. Some early word processors under DOS had significant whitespace at EOL, but tended to display something like a parag…
For what it's worth, GitHub Flavored Markdown changes this to be more TeXy: any newline in text renders as a , and you add an extra blank line to denote a paragraph break.
Re: GitHub pages is now running Jekyll 3
#110Earlier quoted context omitted.
If your editor supports editorconfig[1], you could set it to not strip newlines for .md files. :) [1] http://editorconfig.org/
But I want to strip newlines from .md files.