jambonrose / django-unleashed.com Goto Github PK

The cloud infrastructure is currently outside of version control. That should be changed.

Some tool evaluation is necessary. I'd like to use Troposphere, but that involves introducing Python and Troposphere as a dependency. On the other hand, I could simply use a JSON file for the CloudFormation config, but that makes me unhappy as well, as hand-hacking JSON is prone to error.

Given that this is already a CloudFormation template, I think it'd be best to avoid Terraform, despite the fact that running on several clouds could be fun.

Having a professional copyeditor constantly reminds me how much help I need when writing.

While this site will never actually have the benefit of a copyeditor, having a spellchecker integrated with the CI will likely go a long way.

https://github.com/segabor/Hunspell Seems like a good place to get started.

Most deploy tools allow for assets to have a single setting for the cache header. That seems silly.

The fonts and images on the site are not about to change, so a year-long cache header is fine.

However, the home page links and the errata list change inconsistently a few times a year. Putting a month-long cache on the HTML is therefore desirable.

Not sure that tools are available in Ruby. Some investigation required.

With Jekyll, I need to use {% highlight %} in the Markdown, not Markdown's ``` syntax.

A linter to prevent my from making this mistake (repeatedly) would be great.

The website is not even rank A in accessibility, which is really shameful.

The site should aim to be AA or AAA (if possible).

Does it make sense to add microformats, detailed at http://schema.org/docs/gs.html, to this site?

Some evaluation required.

All infrastructure is running on us-east-1. Whoops.

Furthermore: cross-region replication should be enabled.

To allow readers to better link to errata items, it'd be helpful is the site provided a link/paragraph icon next to each title, allowing people to click/select the anchor link that scrolls the page to the error.

/
/index.html
/errata
/errata/index.html

The paths above should be inferred and invalidated in CloudFront after a deploy.