Skip to main content
Michael Großklaus


Websites are for users, code is for developers.

When building a website, our primary goal should be to serve the user. We need to write maintainable code that makes it as easy as possible for us and the next developer, but at the same this should never worsen the experience for the user. If code makes it easier for the developer, but worsens the experience for the user, it is bad code.

HTML first, afterwards CSS – and only then JS.

HTML allows us to build an accessible and performant web by default. This can be compromised when using CSS and JS, so we need to use it carefully. Frameworks should always only be used when they not only serve the developer, but also the user while not noticeably worsening the performance.

Design should not harm accessibility.

While design and animation should give a website uniqueness, people will not use a website when it is inaccessible or slow. For that very reason, we need to consider implications on performance and accessibility already when designing a website.

Learning basics before everything else.

HTML, CSS and JS, but also accessibility, performance and user experience need to be learned before diving into frameworks. A developer needs to understand at least the basics, to be able to evaluate what technology is necessary to build something. Using a framework without knowing enough basics can lead to a good developer experience, but a bad user experience.