91–100 of 119 posts
Earlier quoted context omitted.
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/
With 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.
Earlier quoted context omitted.
It's a tradition. That's how awesome lists work. See the mother of all awesome lists -> https://github.com/sindresorhus/awesome for more examples. The idea is to keep it as simple as possible e.g. just a single README page. That's all.
Yeah I’m aware of that, but why? You can use GitHub pages with one markdown file; it would be the same contribution workflow but with a nicer end-user interface IMO.
[1] https://github.com/drjekyllthemes/themes [2] https://github.com/planetjekyll/showcase
Recently tried Hugo. The speed is amazingly fast. Much much faster than jekyll.
Hugo is great. The Go template language is somewhat unconventional and does not yet support nested layouts (as do Jekyll, Middleman, etc.), for example. Cheers.
[1] http://staystatic.github.io [2] https://github.com/staystatic/hugo
Shameless plug: Once you're on Jekyll 3, check out http://jekyllthemes.io to upgrade your theme too.
PS: The site is build - of course - with Jekyll and GitHub Pages ;-) and open source [2]. Did you know that you can even use git submodules with GitHub Pages? Works great.
[1] http://drjekyllthemes.github.io [2] https://github.com/drjekyllthemes/drjekyllthemes.github.io
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…
My guess is that various syntaxes for doing basically the same thing fade in and out of popularity randomly and for the most part independent of their feature set, just as different ways of covering the body with cloth fade in and out of popularity. Last year's collection isn't unpopular because it became to hard to use, people want new stuff and they don't want to be associated with old stuff.
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
Some feedback: The cost is a non-starter. The main reason I go through the hassle of writing compilers for my websites is that I want them to be long-lived. Presently, I use Nearly Free Speech as my hosting provider. Their pricing scheme for static sites costs me about $2.50/yr and I can maintain an account balance. My $50 account balance will keep my site online for two decades whereas it would buy me only ten month…
Thanks GH Pages!