Learning note / Reflections on my studies
Web Technology
Web study brings several layers together: the page a person interacts with, the data behind it, and the requests connecting them. I like seeing how a small decision in one layer changes the experience in another.
Structure before decoration
I think of HTML as the structure of an interface, CSS as its presentation, and JavaScript as the behavior that responds to people and data. Keeping those responsibilities understandable makes the page easier to work on.
A form, link, or heading also needs to mean the right thing, rather than only look right.
The request is part of the interface
An interface has more states than a finished screen. A request may be loading, return no results, or fail. I need to decide what the user can understand and do in each of those situations.
That is where frontend and backend thinking meet: the shape of a response affects the components that consume it.
From web foundations to company websites
I connect these foundations to my React maintenance work and the Nutras website. Frameworks help organize implementation, while the underlying questions remain practical: can someone navigate, find the information, and use the page on their device?
What I take forward
- Give content meaningful structure.
- Design loading, empty, and error states.
- Keep the user's task visible while choosing tools.