My #gopher site is online at gopher://jfm.carcosa.net:70/. It seems to be working fine in lynx and the Floodgap proxy, but weird in the two Android clients I've tried. Maybe something to do with the virtual hosting feature.
@dgold I'll write it up later, but it's a little bit hacky.
The tldr is that I defined a custom output format, then templates for the home page (a gophermap), the section pages (gophermaps), and the content pages (markdown files). I had to configure gophernicus a little specifically for it, too.
The index pages *are* converted to gophermaps, though, and that works pretty well. The site navigation links are there and so are the generated reverse-chronological lists of articles in each section.
I've got #hugo generating a #gopher hole identical to my personal website now. Just a few limitations.
1. I have to do a separate run with --uglyURLs=true, because I don't use that parameter with my regular site. 2. The articles are still in Markdown, and they aren't converted to gophermaps, so to follow the links from an article (not an index page), you basically have to copy and paste into a web browser. 3. The articles aren't word-wrapped at 80 characters unless the Markdown source was.
The popular conception of parenthood is lacking. It's viewed as this time where you become a milquetoast version of yourself who puts job security as highest priority.
This isn't intrinsic to parenthood, though. This is the result of a core problem of capitalism, working class precarity, amplified by the intrinsic higher stakes of parenthood. If your kid's access to needs depends on a job that isn't guaranteed, you need a better system.
@jjg How is the deliverability from your own mail server, and how big is the list you're going to be sending to? Unless it's in the multi-hundreds, or, probably, thousands, I don't think you're going to hit any tripwires that will make your deliverability worse than it is. I'd probably set up something like GNU Mailman just so that people have proper unsubscribe functionality (and maybe archives), but not do anything special on the mail end.
Warm visuals can be accomplished with very little in the way of CSS, but there seems to be this unshakeable infatuation with package managers and frameworks (and then shiny new ones when people get bored with the old ones) that adds so much pointless overhead.