<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Aly</title>
    <description>The latest articles on DEV Community by Aly (@indexphp).</description>
    <link>https://dev.to/indexphp</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2085361%2Ff7adbcbc-c1d8-406a-9ac4-f9a168a12ef5.png</url>
      <title>DEV Community: Aly</title>
      <link>https://dev.to/indexphp</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/indexphp"/>
    <language>en</language>
    <item>
      <title>Why I’m Building an Open-Source Frontend Engineering Handbook</title>
      <dc:creator>Aly</dc:creator>
      <pubDate>Fri, 24 Jul 2026 18:32:25 +0000</pubDate>
      <link>https://dev.to/indexphp/why-im-building-an-open-source-frontend-engineering-handbook-2oj5</link>
      <guid>https://dev.to/indexphp/why-im-building-an-open-source-frontend-engineering-handbook-2oj5</guid>
      <description>&lt;p&gt;Every frontend developer eventually reaches the same point.&lt;/p&gt;

&lt;p&gt;You know React. You know TypeScript. You know how to build components.&lt;/p&gt;

&lt;p&gt;But then you join a real project.&lt;/p&gt;

&lt;p&gt;Suddenly the questions are no longer about writing a component — they’re about engineering.&lt;/p&gt;

&lt;p&gt;How should the project be structured?&lt;br&gt;
Where should authentication logic live?&lt;br&gt;
When is React Context enough?&lt;br&gt;
When should React Query own the data?&lt;br&gt;
How do you prevent a codebase from becoming impossible to maintain?&lt;br&gt;
What makes a frontend application scalable?&lt;br&gt;
How do AI coding tools fit into modern development?&lt;br&gt;
These are the questions I kept asking myself while working on frontend applications.&lt;/p&gt;

&lt;p&gt;The problem wasn’t the lack of information.&lt;/p&gt;

&lt;p&gt;The problem was that the information was scattered across hundreds of blog posts, GitHub repositories, conference talks, documentation pages, and personal notes.&lt;/p&gt;

&lt;p&gt;Tutorials Teach Frameworks&lt;br&gt;
Modern tutorials are excellent at teaching frameworks.&lt;/p&gt;

&lt;p&gt;You can easily learn:&lt;/p&gt;

&lt;p&gt;React&lt;br&gt;
Vue&lt;br&gt;
Angular&lt;br&gt;
Next.js&lt;br&gt;
TypeScript&lt;br&gt;
But very few resources explain what happens after that.&lt;/p&gt;

&lt;p&gt;How do experienced teams actually build production frontend applications?&lt;/p&gt;

&lt;p&gt;How do they organize folders?&lt;/p&gt;

&lt;p&gt;How do they write maintainable code?&lt;/p&gt;

&lt;p&gt;How do they review pull requests?&lt;/p&gt;

&lt;p&gt;How do they optimize performance?&lt;/p&gt;

&lt;p&gt;How do they scale applications from one developer to twenty?&lt;/p&gt;

&lt;p&gt;Those are engineering problems — not framework problems.&lt;/p&gt;

&lt;p&gt;Frontend Engineering Is a Different Skill&lt;br&gt;
Writing React code doesn’t automatically make someone a frontend engineer.&lt;/p&gt;

&lt;p&gt;Frontend engineering includes topics such as:&lt;/p&gt;

&lt;p&gt;Project architecture&lt;br&gt;
Feature-based organization&lt;br&gt;
Authentication and authorization&lt;br&gt;
API design&lt;br&gt;
State management&lt;br&gt;
Data fetching strategies&lt;br&gt;
Performance optimization&lt;br&gt;
Accessibility&lt;br&gt;
Error handling&lt;br&gt;
Testing&lt;br&gt;
CI/CD&lt;br&gt;
Monitoring&lt;br&gt;
Code quality&lt;br&gt;
Documentation&lt;br&gt;
Team conventions&lt;br&gt;
These subjects rarely live in one place.&lt;/p&gt;

&lt;p&gt;AI Has Changed the Way We Build Software&lt;br&gt;
Another reason I started this project is the rise of AI coding assistants.&lt;/p&gt;

&lt;p&gt;Learn about Medium’s values&lt;br&gt;
Today many developers use tools like Claude Code, Codex, Cursor, GitHub Copilot, and others.&lt;/p&gt;

&lt;p&gt;These tools can generate code remarkably well.&lt;/p&gt;

&lt;p&gt;But they work best when a project has:&lt;/p&gt;

&lt;p&gt;a clear architecture,&lt;br&gt;
consistent conventions,&lt;br&gt;
meaningful documentation,&lt;br&gt;
predictable folder structures,&lt;br&gt;
and explicit engineering standards.&lt;br&gt;
In other words, AI benefits from good engineering just as much as humans do.&lt;/p&gt;

&lt;p&gt;That’s why I also want this handbook to cover AI-friendly development practices alongside traditional frontend engineering.&lt;/p&gt;

&lt;p&gt;What I’m Building&lt;br&gt;
I’m building an open-source repository that aims to become a practical handbook for modern frontend engineering.&lt;/p&gt;

&lt;p&gt;Instead of being another collection of links, the goal is to explain why certain engineering decisions are made and when different approaches make sense.&lt;/p&gt;

&lt;p&gt;Some of the planned topics include:&lt;/p&gt;

&lt;p&gt;Frontend Architecture&lt;br&gt;
React &amp;amp; TypeScript&lt;br&gt;
State Management&lt;br&gt;
Authentication&lt;br&gt;
React Query&lt;br&gt;
API Patterns&lt;br&gt;
Performance&lt;br&gt;
Accessibility&lt;br&gt;
Testing&lt;br&gt;
Deployment&lt;br&gt;
AI-assisted Development&lt;br&gt;
Project Documentation&lt;br&gt;
Engineering Best Practices&lt;br&gt;
Production Checklists&lt;br&gt;
The repository is still in its early stages, but it will continue to grow over time.&lt;/p&gt;

&lt;p&gt;Why Open Source?&lt;br&gt;
Because engineering knowledge improves through discussion.&lt;/p&gt;

&lt;p&gt;Every experienced frontend developer has learned lessons that aren’t written in official documentation.&lt;/p&gt;

&lt;p&gt;Some learned them after debugging production outages.&lt;/p&gt;

&lt;p&gt;Some after rewriting an application.&lt;/p&gt;

&lt;p&gt;Some after reviewing thousands of pull requests.&lt;/p&gt;

&lt;p&gt;I hope this repository becomes a place where those lessons can be collected and shared.&lt;/p&gt;

&lt;p&gt;I’d Love Your Ideas&lt;br&gt;
If you’ve spent time building frontend applications, I’m interested in hearing:&lt;/p&gt;

&lt;p&gt;What engineering topic do you think deserves more attention?&lt;br&gt;
What lessons did you learn the hard way?&lt;br&gt;
What do most frontend tutorials completely ignore?&lt;br&gt;
Those ideas can help shape this handbook into something genuinely useful for the community.&lt;/p&gt;

&lt;p&gt;Repository&lt;br&gt;
GitHub&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/ualiyou/frontend-engineering" rel="noopener noreferrer"&gt;https://github.com/ualiyou/frontend-engineering&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you find the project useful, consider starring the repository or contributing ideas. The goal is simple: create a practical reference for frontend engineers that keeps improving over time.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>react</category>
      <category>typescript</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
