Typo in common techniques.

[typesupply]

"@empty — This glyph"

[ldo]

Quite a few other typos.

Seems like there has been no response to this or any other issue since late last year.

[typesupply]

Seems like there has been no response to this or any other issue since late last year.

The issue is that the site is generated by a compiler that doesn't work out of the box on my machine. It's possible to fix it, but requires more time than I have available. The long-term plan is to convert the site to GitHub Pages. In the meantime, I am more than happy to take PRs.

[kennethormandy]

Is that something you’re looking for help with? A couple options would be:

• Use a CI service like Travis to build the static site and deploy it to GitHub Pages or a different static site host, whenever you push changes to the source files. This way, your machine wouldn’t need to actually be able setup to run the site all the time.
• Use Metalsmith (Node.js) which can be setup to use a very similar setup to Pelican, so the project is easier to run locally (I’m making some assumptions obviously) but doesn’t need a complete rewrite
• Some combination of both

Converting to Jekyll shouldn’t be too hard either, but I don’t think there’d be a lot of benefits. You would probably still need to use some custom plugins to rebuild the site, and therefore couldn’t use GitHub’s automatic build feature.

[typesupply]

Is that something you’re looking for help with?

Yeah. I'll take whatever help I can get.

A couple options would be:

Hm. Jekyll was the one that I was looking at. We switched the UFO spec to that + GitHub Pages and I'm extremely happy with it. I can focus on the text* and then everything else just happens. That removes the hurdles between changes and publishing and that means that I can make changes and additions more quickly. If I could have that for this, I'd be super happy. I think the only slightly non-standard thing we used with Pelican was Pygments highlighting. It looks like GitHub Pages can handle that. My problem has been that I just don't have the time or HTML/CSS/Jekyll chops to do the conversion.

*I don't ever run Jekyll locally. I look at the Markdown and if it looks good, I push and then check the site. If something looks wrong, I fix it in the Markdown files. I'm okay with things being borked for a few minutes if it saves me some steps.