Skip to main content
This is the reading corner of avrxt’s personal website: practical references for building small websites, understanding failures, and keeping projects maintainable. Start with a problem you have today rather than adopting an entire new stack.

Find a useful next step

Open-source directory

Tools for APIs, diagrams, tests, JSON, search, and secret detection.

Your first contribution

Find a bounded issue and prepare a reviewable change.

Debug an API response

Separate HTTP failures, parsing errors, and browser restrictions.

Search and inspect data

Small ripgrep and jq recipes for everyday work.

Build a useful side project

Scoped ideas with completion criteria and realistic boundaries.

Write a useful bug report

Give maintainers a reproducible example without exposing secrets.

Go deeper

Build notes

Implementation-backed decisions behind the website, profile, and Muzix.

Debugging notebook

Reproduce layout gaps and investigate motion without guessing.

Workflow investigations

Read CI failures and trace stale responses.

Developer recipes

Pagination, cache boundaries, uploads, and confirmation.

Starter downloads

Two small MIT-licensed archives with source and setup instructions.

Accessibility

Forms, keyboard access, contrast, and reduced motion.

Performance lab

A repeatable measurement protocol and honest results worksheet.

Learning paths

Follow a practical sequence toward a demonstrable outcome.

Infrastructure notes

Explore free services, static hosting, Cloudflare email routing, and Gmail SMTP. Provider-dependent guides include official references and a review date. A free tier is a starting budget, not a permanent promise of unlimited service.

Personal context

Read the working principles for the notebook’s approach and the technical log for dated changes. The welcome article and Nxtdev note preserve the original archive. Historical content is kept separate from current instructions. These notes do not imply that every listed project is used by AVRXT or authored by avrxt. External projects retain their own licenses, maintainers, and support channels. If you find a reproducible error in a guide, send a correction through contact.