Fix link formatting for real

LiptonB commented 4 years ago

I'm sorry, I didn't have a dev environment set up and thought I could make a quick fix, but I actually made it stop showing up as a link at all. I'm not sure why the syntax isn't being processed the way I expect, and at some point I'd like to make the code of this page less fragile, but for now here's a fix that I've actually tested.

sparagi commented 4 years ago

Obviously I just gave it a sniff test as well, mostly because I wasn't clear on how to do anything more useful. How would I actually check it?

LiptonB commented 4 years ago

What I did was set up jekyll based on this doc: https://jekyllrb.com/docs/. Of course instead of creating a new blog (step 3) I used this repo. Also, I was doing this on Fedora, and I had to run (checks bash history) bundle install --path vendor/bundle between steps 4 and 5 to get it to work, though I'm not sure if that's always required.

I've done some thinking about a workflow that would allow you to preview the build automatically. Unfortunately, github pages only permits you to build one branch as the site, and even keeping a separate repository for development would be a little awkward because of the CNAME file - if it's in both repos they'll both try to host on www.octotrike.org and only the one with the right DNS records will actually work. Current ideas include:

Separate dev repo that does not have the CNAME file, and slightly annoying git workflows to keep it that way - I believe if new code always goes into dev and you always merge from dev -> production and never the other way around this could be made to work
Dev branch in the main repo, use free CI like https://circleci.com/ or https://travis-ci.org/ to build a preview of the dev branch, then merge into the master branch if it looks good. This seems like less of a hassle to use but has more moving parts and I would need to test that the CI can actually build a preview you can look at in a web browser.

sparagi commented 4 years ago

I'm merging without testing myself, because I don't want to hold up bug fixes any longer than I already have. I'm going to create a ticket about a preview system & workflow so everyone can use it. In my dreams, more people contribute to the site on a regular basis, and this would help (e.g. I might notice the footer copyright in PR #3).

octotrike / octotrike.github.io

Fix link formatting for real #4