sinewalker / sinewalker.github.io Goto Github PK

Initially this site was created with Nikola and the source stored at BitBucket. Mainly because I understood mercurial more than git. I still do, but I'm going to change that.

I need to migrate all the stuff from BitBucket into the right branch on this repo, and reconfigure Nikola's deployments to use github_deploy.

I'd like the menu bar stay visible when the page is scrolled.

There should be a way to make Bootstrap do that, I just have to figure it out.

I like how it looks from the user's viewpoint, but I don't like how it works from the developer's viewpoint.

It's based off https://github.com/sinewalker/Btns which I was never really happy with. I should build something of my own which I can then be unhappy with as well, but at least fully understand. Plus I'll learn some HTML5.

Issue #7 glossed over this, but I need to review all posts and fix their tags to be consistent

Can do this in line with issue #15

I have notes (of varying currentness) in org-mode files within the repo source directly. They belong in the wiki. When I address #1 I should also move these into the wiki here in Github.

The Asciicasts in my post on journalctl have gone missing. I think it may have been when I made a change to the fonts and had a word hiccup in the deploy. Need to look in the git logs to find it FM's work out what happened

I haven't got it Right yet, clearly.

First github_deploy did this:

• ignored or dropped /output/assets, meaning no design for the site
• clobbered /hax so no more matrix rain hack
• removed /jargon

• The slugs are messy
• where the posts go is messy
• I should make use of Nikola Sections, and deprecate Categories
• I should actually document the IA so that it's clear to me where things belong, what I've changed from vanilla Nikola and why I did it.
• There is another domain name I have: milohax.net (also https://github.com/milohax) which I need to consider how I will use in connection with milosophical.me

Nikola 8 changes a few things, mainly for the better. It also breaks my theme customisation.

This would best be done in a separate branch.

One of the changes is a new Bootstrap, but there are useful changes in the way the categories work.

Something about the way Zen-IPython works (see #2) and being based off of Nikola 5 is preventing Nikola from running with conf.py set the way it is. It crashes with a Python stack trace on Nikola 7/Python 3.

• Need to review my settings and get them to work on a bare init of nikola
• Need to review how to create a new Nikola Python virtual env from scratch

There's some detail about setting up openSUSE for use with Python3, Virtualenv and Nikola for my hax-vm project in the Nikola vagrant provisioning script. This should be separated out to a script that builds the virtualenv (in a manner like activate from my dotfiles) after installing the python libraries in an OS-dependent fashion, as shown in the vagrant example.

While I like dark pages, I conceed they're not for everyone, and sometimes it would be helpful to have a dark-text-on-light-background look (when outdoors, or projecting to a screen, for instance).

It should be fairly straightforward to customise the colour variables in custom.css for a light page, based upon this CodePen

Altering the nikola_ipython.css should also be possible, though probably not as DRY, without also changing that to use variables in a similar fashion.

As noted on the Wiki Setup page, it would be useful to have a tool that compares the stock Nikola conf.py in a manner similar to Spacsmacs' (spacemacs/ediff-dotfile-and-template).

Probably use Unix or GNU diff rather than ediff from the command line. Or, why not both?

Especially since I never documented it properly, or fully! This is why #3 exists in the first place.

Once I complete #3 (and #1) I should look into continuous builds with Travis CI -- then maybe I won't have to rebuild whenever I break my PCs.

A few old posts have inline images which load from other websites. I should copy them into the repo and serve from the same place as my site.

Apparently this is a thing in Python3?

Mentioned in "How to Make Mistakes in Python" by Mike Pirnat.

I should verify this, and then update the wiki if it's true.

• Their commit history needs/deserves to be separate from the main line
• Especially for Jargon and Pixels -- they're quite large
• I'd like to be able to pull out the hax code separately and not have the whole blog

I need to learn about Git sub-repos, git checkout --recursive and any changes that may or may not be required to checkout on a new machine and build, plus what to do to bring the blog repo's version up-to-date with the sub-repos.

I want a light-text-on-dark-background theme.

I think I can just tweak the CSS to start with.

Nikola Taxonomy documentation

I'd like at least 3 sections:

1. More personable, reflective posts
2. Current technical topics
3. Section for coding with kids

Also I'd like them reachable from the Site's main menu, which is why I listed in above order...

Also I'd like a different, light theme for the kids section as it will be having pages to project onto a Starboard.

There are numerous problems with this site's Nikola theme Zen-IPython, not least being that the theme itself is deprecated and unsupported.

I want to switch back to the vanilla bootstrap3 theme and then tweak it for colours.

This means configurations for Zen-IPython in conf.py will need to be removed.

https://fonts.google.com/specimen/Titillium+Web?selection.family=Titillium+Web

example: https://blog.klimczyk.pl/2017/05/04/what-to-do-when-programming-sucks/

Some tools I want easy/reliably access to:

• URL decode/encode (probably copy Eric Meyer's, which would be completely legitimate)
• Password generators (like Dinopass.com ... and there is a better one out there)
• Base64
• MD5sum
• Dvorcode
• Morse (for fun)
• and maybe a link database? (fully static, updates via git commit to the database only)

There's a common theme here: nearly all of them are dictionary codecs, I can probably start with one, maybe Morse, and then expand it to others. I'm unsure if I want to use the flipper code, or start fresh.

• Is the background image suitable still?
• there's technical errors in the messages
• it's arguably too long... :-)