stevenmaude / stevenmaude.github.io Goto Github PK

It's outdated. Would be useful to include a list of other things I've written.

Pages would be slightly cleaner without it, though it's nice to have a way of seeing what else is on the site.

Following getpelican/pelican-themes#659 and getpelican/pelican-themes#660, issue for my usage is that I need to make some tweaks to the Bootswatch theme.

Notes I have from previously:

## Theme customiser
DONE:
Cosmo
Change font size to 22px
Change fonts to Source Sans and Source Code
Set line height to 1.454545454
Pagination button colours: pagination-color rgb(50, 50, 50)
pagination-hover-color: rgb(0, 0, 0)
In theme.less:
@import url("https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,700");
Change code font to "Liberation Mono", Cousine, Consolas
Replace bootstrap-live-customizer URL with .. (Glyphicons)

GitHub now support HTTPS for custom domains 🎉 — doesn't work right now properly for this site, because it's trying to load mixed content. I suspect the site just needs rebuilding and the Pelican config changing to use https for the URL.

Currently, the ordering is taken from the Markdown file. Perhaps alphabetical ordering makes more sense.

Have issues relating to codehilite when running with the newest major version of Python Markdown.

ModuleNotFoundError: No module named 'codehilite(css_class=highlight)'

2.6.11 works fine.

It defaults to some difficult-to-read font colour.

Probably not applicable as my theme fork is too modified.

These should templated in relatively, not explicitly written out as www.stevenmaude.co.uk (what would happen if the site moved domain?). There are a few of these.

Requires being done just before updating the site again, as you need a new commit to republish.

Now on pelican==3.7.1; blockers for this are changes the PAGES variable to pages in the theme and replacing MD_EXTENSIONS in configuration with new MARKDOWN setting.

Hesitant to do the tweak for the theme before trying to merge in new commits to the theme, see #88.

There are cases where the Markdown may be written with lists and multiple paragraphs where the output may consist of multiple lists.

• pelican-alias

Would be nicer if they didn't for consistency as all other pages — as far as I know — now don't have that. It is a small issue as the (important) article and fixed page (e.g. about) links no longer have .html at the end, and these are the ones which anyone would actually link to.

Following StevenMaude/blog-config#43, it is possible to build the site on GitHub Actions. It would be better to use that to automatically publish to remove a couple of manual steps.

There are several commits made to the "official" repository of the theme that would be nice to have. However, it's a pain because I originally forked the theme to add changes to try and improve readability and:

• this theme is now part of the pelican-themes repository, not the standalone repository it once was (which made it relatively easy to merge in new commits);
• there may be conflicting changes.

One approach is git filter-branch to get the commits from the theme alone extracted from the pelican-themes repository into a separate repository, then cherry pick my own commits from my forked version of the theme and attempt to apply each of my commits to that new version of the theme.

So that e.g. https://stevenmaude.uk works, and add to Google Webmaster Tools too.

Check posts for this.

Some thoughts:

• Hugo is faster than Pelican and seems to have overtook it in popularity and development activity, judging from a quick glance on GitHub.
• The theme used right now is Bootstrap 3 based and unlikely to be migrated to a newer version of Bootstrap as there isn't an active maintainer or team pushing development of this theme.
• Moving theme might require substantial changes, and therefore changing theme and blog engine might be sensible to do at the same time, to avoid having to repeat work in future.

TODO:

• Find a suitable Hugo blog theme.
• Investigate how much work might be needed to port across the source content.