I've been learning web development as a hobby and enjoy improving through small projects. I'm comfortable with the basics of HTML, CSS, and JavaScript, but I haven't built many larger or production-level websites yet. I'm considering Astro for my next projects because I like its focus on performance and simplicity. What should I prioritize alongside learning Astro—TypeScript, accessibility, responsive design, UI/UX, SEO, APIs, performance, Git, or something else? I'd especially like advice from people who have been at a similar stage: what helped you improve most, and what do you wish you had learned earlier? I have a day job, so I can realistically spend about one or two hours a day and would rather build a solid foundation over the course of a year than rush through everything.
5 Answers
Start with accessibility and responsive design because they make nearly everything you build more usable. Semantic HTML, keyboard navigation, readable contrast, and layouts that work on different screen sizes are valuable regardless of the framework. TypeScript would be a good next step, especially since Astro supports it well, but you’ll learn faster by building real projects instead of studying every topic in isolation.
If your HTML, CSS, and JavaScript fundamentals are reasonably solid, focus on building something from start to finish rather than working through a checklist of concepts. UI design and responsive layouts naturally overlap, and accessibility will come up as you build. Astro handles a lot of performance concerns well, so you probably don’t need to optimize prematurely. TypeScript is useful once your projects become more complex, while APIs can be treated as a separate topic to learn when a project needs them.
I’ve done a few small frontend projects before, but then spent time learning more about system architecture and stopped practicing frontend work. I’m returning to it now and want to take a slower, more practical approach.
Learn Git early. Commit regularly, use clear commit messages, and practice viewing history and reverting changes before you really need those skills. You will eventually break a project, and version control turns that from a disaster into a small, recoverable mistake. Since Astro projects are mostly straightforward files, it’s a good environment for learning Git without too much extra complexity.
Don’t assume that being comfortable with the basics means you’ve mastered them—JavaScript in particular has a lot of depth. A useful test is to complete an entire project without relying on copied code or step-by-step videos. Documentation and examples are fine, but make yourself understand and write the solution. If possible, build something for a real person or organization with actual requirements. Working through feedback, revisions, bugs, and deadlines will teach you far more than isolated exercises.
I appreciate the honesty. I do feel fairly comfortable with HTML and CSS, but JavaScript definitely needs more practice. I’m not in a rush because of my day job, so I’ll aim for one or two hours a day and give myself about a year to build projects properly and learn from the mistakes.
Build one complete, real site and publish it. Deployment, routing, forms, content, errors, and maintenance teach lessons that tutorials often skip. Astro is a good choice because it keeps the underlying web technologies visible instead of hiding everything behind a large abstraction. Along the way, prioritize semantic HTML, responsive design, accessibility, and understanding how the browser works. TypeScript can wait until you’re comfortable with the basics and your projects start benefiting from stronger type checking.
That makes sense. I’m planning to build a couple of complete sites so I can learn each concept when I actually run into a problem. I’ll probably add TypeScript once I’m comfortable with the Astro basics.