Web developmentBart Nagel
I've been doing this for over 20 years and I've learnt a thing or two.
Content management
I'm familiar with a long list of content management systems, used both traditionally and headless. I've also built CMSes from scratch, and I've built plenty of sites which don't need one at all.
Targeting modern browsers
I like to use modern standards, which means primarily targeting modern browsers, with graceful degradation and fallbacks where needed for older target browsers. This keeps the code leaner, faster, and more maintainable, which means a better experience both for the developer and the visitor.
What's included
HTML, Javascript, and CSS done right
Whether it's React, Vue, Angular, Pug, or plain HTML...
...whether it's Typescript or Javascript...
...whether it's Sass, Less, PostCSS, or plain CSS...
...whether it's component libraries like Material or Bootstrap, utility libraries like Tailwind, or the traditional cascade...
...whether it's static, dynamic, or client-side...
...whether data is all static, comes from a CMS, from the users themselves, or from umpteen different APIs...
...It all boils down to HTML, Javascript, and CSS.
Whichever stack I'm using, you're going to get flexibility, reusability, and performance, with clean code and clear documentation.
Reusable components
Where possible I like to encapsulate components so they can be mixed and matched in any context.
Concise and flexible styles
A lot of CSS output these days is spaghetti. I try my best to keep things concise by taking advantage of modern styling properties, while targeting totally flexible viewport sizes, and taking into account the user's configuration and preferences.
Accessibility
While I don't pretend to be an accessibility expert, I take accessibility seriously and follow all the best practices I know. Everyone should be able to access the information you are presenting.
Performance
Nobody likes a slow website. I measure performance and make all the improvements I can. I provide advice to keep things fast as time goes on.
Automated testing
I highly recommend allocating budget to writing automated tests.
Unit tests cover the most critical pieces of low-level logic.
Acceptance tests ensure that critical action paths the user wants to take when viewing the website are still working.
Every time there is a code change, the tests are run, so new issues are noticed right away.
Example work
Bart's other services
Starting at$150 /hr
Tags
CSS
HTML5
JavaScript
Fullstack Engineer
Web Developer
Service provided by
Bart Nagel Vancouver, Canada
- 5.00
- Rating
Web developmentBart Nagel
Starting at$150 /hr
Tags
CSS
HTML5
JavaScript
Fullstack Engineer
Web Developer
I've been doing this for over 20 years and I've learnt a thing or two.
Content management
I'm familiar with a long list of content management systems, used both traditionally and headless. I've also built CMSes from scratch, and I've built plenty of sites which don't need one at all.
Targeting modern browsers
I like to use modern standards, which means primarily targeting modern browsers, with graceful degradation and fallbacks where needed for older target browsers. This keeps the code leaner, faster, and more maintainable, which means a better experience both for the developer and the visitor.
What's included
HTML, Javascript, and CSS done right
Whether it's React, Vue, Angular, Pug, or plain HTML...
...whether it's Typescript or Javascript...
...whether it's Sass, Less, PostCSS, or plain CSS...
...whether it's component libraries like Material or Bootstrap, utility libraries like Tailwind, or the traditional cascade...
...whether it's static, dynamic, or client-side...
...whether data is all static, comes from a CMS, from the users themselves, or from umpteen different APIs...
...It all boils down to HTML, Javascript, and CSS.
Whichever stack I'm using, you're going to get flexibility, reusability, and performance, with clean code and clear documentation.
Reusable components
Where possible I like to encapsulate components so they can be mixed and matched in any context.
Concise and flexible styles
A lot of CSS output these days is spaghetti. I try my best to keep things concise by taking advantage of modern styling properties, while targeting totally flexible viewport sizes, and taking into account the user's configuration and preferences.
Accessibility
While I don't pretend to be an accessibility expert, I take accessibility seriously and follow all the best practices I know. Everyone should be able to access the information you are presenting.
Performance
Nobody likes a slow website. I measure performance and make all the improvements I can. I provide advice to keep things fast as time goes on.
Automated testing
I highly recommend allocating budget to writing automated tests.
Unit tests cover the most critical pieces of low-level logic.
Acceptance tests ensure that critical action paths the user wants to take when viewing the website are still working.
Every time there is a code change, the tests are run, so new issues are noticed right away.
Example work
Bart's other services
$150 /hr