Hacker News new | ask | show | jobs
by vintagedave 1104 days ago
> I made my own static site builder (typical HN!) and it's just a python package

Same! I designed the look of my site, and then wrote Python to generate it, though instead of Jinja I even wrote my own templating library. The goal of reinventing the wheel was to learn Python through writing a non-trivial, useful app and libraries.

I haven't quite mustered up the courage to publish the source, yet, though: being a learning exercise I'm painfully aware some of the code is not as good as it should be. And I'm still learning what makes Python code Pythonic.

> What happened to "I'll edit this .html file and FTP it up..."

A SSG _is_ that, these days. My SSG generates my own site design. If I tweak the site's look and feel, I do that once and re-run the SSG. I wouldn't want to have to do that across multiple HTML files.

My process is:

* Write Markdown

* Run the SSG script

* FTP it up (overwriting previous contents; I have dated backups of every version, and the most recent run of the SSG is the canonical version.)

I entered the site in the competition, since it's no-Javascript, pure HTML & CSS, minimal, manuscript-style typographic focus, with articles on design, management, and the just plain miscellaneous. Very much going for the 'old-school personal site about whatever someone finds interesting' feeling, and hopefully some bits will be of interest to HN people too, maybe. https://daveon.design if you're interested!

2 comments

Mine replaces Craft CMS and its twig templating system, so Jinja made a lot of sense.

It also converts and resizes images, processes SCSS, and a few other things that suit my workflow.

Editing source-controlled files in a familiar text editor is blissful.

Readable (just) in Seamonkey although some of the text is overwriting other text. Fully readable in links on the command line. Well done.
Thankyou! I'll check SeaMonkey. I've tested only Firefox, Chrome and Safari (and desktop and mobile) so far. Really glad to hear it works in links! That's awesome.

There should be a reasonable amount of accessibility markup too (in how it's structured plus some specific accessibility items) for screen readers as well.

Try palemoon perhaps.

Seamonkey is an old school fork of Netscape before they pulled out Firefox. I suspect the CSS rendering is marginal CSS 2.

I use Seamonky on OpenBSD i386 arch as Firefox no longer supported. I am using deliberately low spec computers for personal surfing.

The links render shows the 'skip to main content' link which is always a good sign that accessibility has been addressed.

If you have a few minutes to kill, I'd love to know how allaboutberlin.com feels on such a device. I sometimes choose convenience over coverage, but I still try to make the website accessible.
Thinkpad T42, 1Gb ram, slackware 14.2, seamonkey 2.53 with noscript legacy plugin operating.

Loads fast, looks clean, content seems to be available - each of the 'cards' opens a page with a graphic, a table of contents in a contrasting grey colour and then text giving information. There is then a 'classified ads' section with links at the bottom.

Looks identical on my 'normal' machine with Firefox 102-esr and ublock origin and more ram/faster processor &c.

A quick look in the text mode browser links in a uxterm window showed that text content was available. The home window links show as two rows of text links - works ok.

I'm on a pretty fast G4 'mobile broadband' connection in UK with around 2.5Mb/sec (probably the old Thinkpads wifi limit) and around 45 mSec latency from ping.

Just one observation:

https://allaboutberlin.com/ works fine

https://www.allaboutberlin.com/ gives a page not found.

This reply is not very timely - I'm not logged in on HN that often!

Not the person you asked, but I just opened it on Firefox on Mac. That website is _blazing fast_. It opened in a fraction of a second. Really good job!