Announcing 0.1.0 of Astrolock

Building blocks of Astrolock?

• Hobby site publishing DJ Mixes built in Hexo, which stopped playing nice
  • Auto import from Rekordbox to a page, and uploaded to internet in a few commands
• Found Astro framework, which was easy to rebuild hoppy
  • Had been working React so was easy choice
  • Static HTML generation is a hard requirement, Astro gives that plus more
  • Work on the file system, write your content in markdown really is the best approach for content driven sites

Astrolock is an Astro flavour

• Astro favours “templates” for bootstrapping your site
• Astroplate was best one that original was based off
  • Sorry Astroplate folks, I will change the images soon
• Astro is great but there is too much code in the eyeline of a user wanting to publish content to the web
• Wanted to take a workflow, make it into a simpler workflow (and codify all the needs around it)
• Notable differences
  • astrolock.yaml configuration file
  • Dynamic Collections driven from the astrolock.yaml
  • Supports: text, images and audio at the moment, video is there but not really tested

Good learnings

While the features above are good, the real reasons for Astrolock are to learn or remind myself of technology I generally use in normal life, but don’t practice in my hobby sphere well:

• AWS via Configuration
• Terraform
• Docker
• React
• Bashly (Bash Scripts as a CLI)

One big call out, is a lot of Astrolock was about:

• Vibe Coding (yes, I hate that term too, but someone really needs to come up with a better one)

Improvments needed from Astrolock 0.1.0

• The user-guide and developer-guide probably need some correctsion (workflow and actual detail)
• The user docker distrubtion did work a while back, but the publish to AWS ECR and it’s use is needing tested
• The importer plugins are ideas, more than implementations at the moment