"HATEOAS for Haunted Houses"
A case-study in using Hypermedia as the Engine of Application State (HATEOAS) architecture to build a flexible control system for a local haunted house on a tight delivery schedule.
www.sanfordtech.xyz/posts/hateoa...

Thanks for the link. I'll keep an eye out for updates!

I'd love to try to build a personal finance app built on ATProto. Apps in that space are very sticky exactly because people value their history so much.

From what I can tell, the protocol is missing the ability to encrypt a person's data repository. That's a hard requirement.

Congratulations on the migration! Signed up for your newsletter.

Here's a complete implementation guide with configs and screenshots:
www.sanfordtech.xyz/posts/aws-ss...

When your security setup enables faster development instead of fighting it, you can focus on shipping features rather than managing access or compromising security.

I've used this at two companies: a fintech handling compliance audits and my own startup managing multiple contributors.

Same setup works whether you're onboarding contractors or handling compliance requirements.

No expensive SSO provider needed.

The magic happens in your local development setup. Instead of hardcoded keys, you get temporary credentials that automatically expire, generated from a single command.

AWS Organizations + IAM Identity Center solve this with two key principles: separate AWS accounts for environment isolation and temporary credentials through SSO.

Each environment gets its own account. Dev work stays in dev, prod stays locked down, billing stays consolidated.

The problem with most startup AWS setups:
❌ Shared root credentials
❌ No isolation between dev/staging/prod
❌ Manual access requests slowing down work

I haven't used it myself, but I was pitched by a vendor using Coast:
www.trycoast.com

They used it to show what experiences their API could bring to my app. It's been my favorite sales call to date.

Not a person, but I learned a lot from this book:
www.refactoringui.com

Just filled out the survey! I'm looking forward to learning more about ElementInternals and Mutually exclusive <details>.

Thanks for the link!

The meta tag support includes standard content and extensions.
The JSON-LD functionality helps your site utilize Google's enhanced search results.

Check it out! Contributions welcome.
github.com/san4d/astro-...

Thanks, man! I've built my startup with Astro, HTMX, Web Components, and a lightweight SQL client (DrizzleJS) and it's been amazing how quickly I can implement features.

I'd like more people to think about whether their app is truly client-side focused.

Fair enough. Daisy has good theming support, which might be helpful.

Whatever tooling you choose, if ClaudeCode struggles try using the Context7 MCP server. It allows Claude to pull a library's most-recent documentation.

I've had a good experience with Astro and ClaudeCode. It outputs static HTML by default and works well with Tailwind. Check out DaisyUI as well, since you're using Tailwind.

Thanks for this. I'll update the post. Playing around with it a bit more, it's an `HTMLUnknownElement` if its parsed as native tag (one word, no hyphen) and a `HTMLElement` otherwise.