Frontend Notes

Project Structure

EN

A useful project structure lets a developer locate a feature, change it, test it, and deploy it without guessing which files own which behavior. Organize a project for its current requirements, then refactor when responsibilities become unclear. There is no universally correct folder tree, and renam...

Protocols

EN

In today’s connected world, front-end developers do far more than style web pages and craft user interfaces. They also need to understand the underlying network protocols that shape how data travels between their applications and the servers that power them. By mastering the inner workings of protoc...

Ux

EN

UX, or User Experience, focuses on designing products and services that meet user needs, preferences, and behaviors. The goal is to make important tasks useful, understandable, accessible, and effective; evaluate these outcomes with users rather than assuming any interface is universally intuitive...

Hosting Websites

EN

A website on your computer is not automatically reachable by other people. Hosting makes its files or application available over a network; DNS helps browsers find the hostname's destination; HTTPS protects communication between client and server. These are different concerns, and publishing a page ...

Testing

EN

A frontend is not finished when its first demonstration works. It must still work after a CSS change, a pricing-rule update, a dependency upgrade, or a failed network request. Testing turns the promises a feature makes to its users into checks that can fail when those promises are broken. It reduces...

Css Frameworks

EN

CSS preprocessors and frameworks are two important tools in a web developer's toolbox that can help streamline the process of building websites. CSS preprocessors allow developers to use new functionality that is typically borrowed from another programming language, while frameworks provide pre-writ...

Ui

EN

UI is an important aspect of frontend development, as it deals with the elements that users directly interact with. When designing the UI, it’s important to think about how color choices, overall layout, responsiveness, and interactive elements come together to make the product look appealing and ea...

Javascript Frameworks

EN

A static portfolio, a content website with minimal interactivity, and a client-heavy dashboard have different requirements. Begin with an explicit feature inventory: navigation/routing, persistence, data fetching, authentication boundaries, search requirements, accessibility, localization, bundle co...

Javascript

EN

JavaScript is a programming language that is primarily used for client-side scripting (making web pages interactive). Since NodeJS we can also use JavaScript in server-side scripting (e.g. for APIs)...

Css

EN

CSS work began in 1994; CSS1 became a recommendation in 1996 (W3C history). As pages became application interfaces, developers stretched document-layout tools into column systems. A float-based layout with percentage widths and clearfix rules made sense before dedicated layout systems were available...

Html

EN

HTML began as a way to describe linked scientific documents. That origin explains why headings, paragraphs, links, and forms remain useful foundations even for an application. The HTML Standard's history traces the later expansion into application features. Today HTML is a Living Standard: “HTML5” i...

Additional Resources

EN

This chapter is a directory, not a certification program. The sites below may offer free and paid assets, incompatible versions, or changing terms. When a resource looks useful, open its source and license, run the demo where possible, then test how it behaves in your own layout. Do not treat a beau...

Quizes

EN

Use these expandable questions to test explanations, not just terminology. Before opening an answer, predict the result and try a small browser example. The categories cover HTML, CSS, JavaScript, protocols and hosting. Examples are illustrative; versions, browser support and hosting prices should b...