Menu

Practical frontend reference

Quality by default

Practical standards for building accessible, maintainable, performant websites properly.
Built from real delivery, not theory, and focused on frontend work that survives real teams, real deadlines, and real production systems.

Start with Principles Explore Standards

01 — Context

Why This Exists

Teams rarely struggle because they lack a framework. They struggle when nobody agrees what good frontend looks like.

That shows up as inconsistent code, accessibility gaps, performance regressions, and systems people avoid maintaining.

Frontend Foundations is a practical reference for teams who want repeatable quality—not more opinions dressed up as best practice.

02 — Philosophy

Principles First

Good frontend work starts with good decisions. Before tools, frameworks, or architecture, there are principles.

  • Platform and defaults first—add complexity only when it pays off.
  • Native HTML and behaviour before custom components.
  • Accessibility built in, not bolted on before launch.
  • Performance is part of quality, not a separate phase.
  • Clear, maintainable code beats clever code.

Read the Principles

03 — Reference

Core Standards

Explore All Standards

04 — Implementation

Practical Patterns

Standards explain what good looks like. Patterns show how to build it. Real implementation examples for the frontend problems teams solve every day.

Explore Patterns

05 — Delivery

Review Checklists

Good standards are useful. Good checklists make them repeatable. Use practical code review checklists for HTML, accessibility, performance, JavaScript, and delivery quality.

View Checklists

06 — Trust

Built From Real Delivery

Frontend Foundations is based on years of real frontend delivery across accessibility, performance, design systems, e-commerce, public sector, private sector, and legacy enterprise systems.

This is not theory. It is practical experience shaped into standards people can use. Built for teams who have to ship work, maintain it, and defend it later.

07 — Answers

Frequently Asked Questions

  • What are frontend standards?

    Frontend standards are shared rules for how teams build HTML, CSS, JavaScript, accessibility, and performance consistently. They reduce technical debt and improve delivery quality.

  • Why do coding standards matter?

    Because unclear standards create inconsistent code, accessibility issues, performance problems, and onboarding pain. Good standards make quality repeatable.

  • Is accessibility part of frontend delivery?

    Yes. Accessibility is not an add-on or audit task. It is part of correct frontend delivery from the start.

  • Do modern frameworks replace frontend standards?

    No. Frameworks do not replace engineering judgement. Teams still need standards for quality, accessibility, performance, and maintainability.

  • How do you improve legacy systems safely?

    Usually by improving the areas you touch, reducing risk over time, and avoiding unnecessary rewrites that create new problems. Refactor deliberately. Not emotionally.

08 — Next step

Good frontend work starts with good decisions. Read the principles behind the standards.

Read the Principles