Chapter 01Field guide
The surface is where the system becomes usable.
The interface layer turns data, logic and services into something a person can see, understand and act on. HTML, CSS and JavaScript are the foundation, and responsive design is part of the work.
At the user interface layer, full stack developers are expected to understand HTML, CSS and JavaScript. They should be able to create responsive websites and web apps that look good and work well on multiple devices. The surface is not decoration. It is the place where the system earns trust.
What the layer owns
The interface layer owns structure, presentation and interaction. It decides how content is ordered, how it adapts to a screen and what happens when a person clicks, types, scrolls or waits. It also carries the system's accessibility, whether that is treated as a first concern or an afterthought.
The core three
HTML gives the page meaning and structure. CSS controls layout, type, color and the way the page responds to different viewports. JavaScript adds behavior, state and communication with the rest of the system. Each one has a job, and keeping those jobs distinct makes the interface easier to change.
Responsive by default
A full stack developer should be able to create responsive websites and web apps that work well across devices. That means the layout should be designed for narrow screens, wide screens and the sizes in between. It should also survive long labels, large text and real content that does not match a mockup.
Frameworks in view
Full stack developers should have an understanding of frameworks like React, Angular and Vue. A framework can organize components, state and routing, but it does not remove the need to know the browser platform underneath. The best choice is the one that fits the team, the product and the life of the code.
The framework is not the foundation. HTML, CSS and JavaScript remain the shared language beneath every interface.
A useful checklist
- Use semantic structure so the page makes sense without visuals.
- Test the keyboard path, not only the pointer path.
- Design for small screens before adding the large screen detail.
- Separate interface state from server data where the boundary matters.
- Keep components understandable without a hidden layer of context.
Where the layer connects
The interface sends requests into the web layer and receives data back from the application layer. When those contracts are clear, the surface can change without forcing a rewrite of the system beneath it.
02 / Continue Web: follow the request into the systemReference shelf
Build a stronger surface.
Documentation for the three core technologies and the frameworks named in this chapter.