Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub pages is now running Jekyll 3

github.com

Post reply on HN
Print view View original

81–90 of 119 posts

Re: GitHub pages is now running Jekyll 3

#81

Post by avn2109 »

kevin_thibedeau wrote: post #59
Animats wrote: post #27

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…

That's why I prefer ReST. More powerful syntax out of the box with a standard extension scheme so you don't end up with the mess of all the different incompatible Markdown implementations. With the internal structure exposed as an XML format (rst2xml) it is easy to transform documentation into a wide variety of formats that docutils or Sphinx don't handle directly.

A lot of that sounds good but you lost me at XML.

Re: GitHub pages is now running Jekyll 3

#82

Post by sytse »

frankthedog wrote: post #55
sytse wrote: post #23

Earlier quoted context omitted.

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

Is GitLab pages going to be available to non-enterprise gitlab.com users? If not, may I respectfully request that it is?

Thanks for asking. Right now we have no plans to merge it into GitLab CE. Can I ask what your use case is? How many people are using your GitLab installation and how many static sites are you planning?

Re: GitHub pages is now running Jekyll 3

#83

Post by mrmondo »

Pxtl wrote: post #73
BHSPitMonkey wrote: post #41

Earlier quoted context omitted.

The nice thing about Markdown that doesn't apply to those other formats is that it's designed to read naturally in plaintext. That constraint should (in theory) prevent it from transforming into something prohibitively complicated to write in.

Except for links to images. I can never freaking remember those. Also, the silly space-at-the-end for line breaks.

I always forget the combination of an image with a link and alt text. [![click here)[lol.com/img.png] or something like that, the only other thing that annoys me is when people use underscoring / equals under text to make it a heading rather than #s, otherwise I find markdown a pleasure to write in.

Re: GitHub pages is now running Jekyll 3

#84

Post by kentonv »

Animats wrote: post #80
Pxtl wrote: post #73

Earlier quoted context omitted.

Except for links to images. I can never freaking remember those. Also, the silly space-at-the-end for line breaks.

"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.

Re: GitHub pages is now running Jekyll 3

#85

Post by nness »

Animats wrote: post #27

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's issues are probably more specifically all of the edge-cases that differ from implementation to implementation. Lack of a rigid specification and near-abandonment by its author didn't help.

Re: GitHub pages is now running Jekyll 3

#86

Post by paudel »

bigmanwalter wrote: post #74

I just found out about Lektor the other day. https://www.getlektor.com/ It's like Jekyll meets WordPress, written in Python by Armin Ronacher. He's the guy who wrote the extremely popular Python microframework, Flask. It's a static site generator with a slick React powered admin interface intended for editors (non-programmers) to use. It runs locally like any good static site generator should and runs on Windows, OSX…

This looks cool, definitely gonna try. I think it should support python 3 also.

Re: GitHub pages is now running Jekyll 3

#87

Post by marklgr »

Pxtl wrote: post #73
BHSPitMonkey wrote: post #41

Earlier quoted context omitted.

The nice thing about Markdown that doesn't apply to those other formats is that it's designed to read naturally in plaintext. That constraint should (in theory) prevent it from transforming into something prohibitively complicated to write in.

Except for links to images. I can never freaking remember those. Also, the silly space-at-the-end for line breaks.

> Except for links to images. I can never freaking remember those.

They work like standard Markdown links (text in square brackets, followed by link in parens), except you add a bang in front of it. The bang looks like an upside-down "i", the first letter of "image".

Edit: read too fast; _links_ to images use image instead of text in a link, so you just replace the text with text in square brackets with the syntax of Markdown image. I've never struggled too much with this one, so I don't have any useful mnemonics, sorry.

Re: GitHub pages is now running Jekyll 3

#88

Post by mariusc23 »

kentonv wrote: post #84
Animats wrote: post #80

Earlier 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.

If your editor supports editorconfig[1], you could set it to not strip newlines for .md files. :)

[1] http://editorconfig.org/

Re: GitHub pages is now running Jekyll 3

#89

Post by bshimmin »

Animats wrote: post #27

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…

I once contracted at a company where one of the salaried staff was tasked with implementing Markdown. For some reason, he actually implemented BBCode (I think with a regex he'd found online somewhere). When I tried to explain to him that BBCode and Markdown were, you know, quite different, he got angry with me and started shouting that "Markdown has no standard, so it can be anything you want!"

I left the conversation at that point because I sensed it might turn ugly (it was the afternoon, and he had a penchant for boozy lunches when his boss was out of the office).

Re: GitHub pages is now running Jekyll 3

#90

Post by pizn »

tedkimble wrote: post #18

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?

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
Post reply on HN