Development philosophy
The simplest solution is often the best one.
If a website can be built without a database, there may be no reason to introduce one. If a small interaction can be handled without a large JavaScript dependency, there may be no reason to add one.
This does not mean avoiding technology for its own sake. Technology is useful when it provides a meaningful benefit.
The goal is to build what the website needs without adding complexity simply because it is possible.
Performance
Performance is considered during development rather than treated as something to fix at the end.
Images are optimized, unnecessary JavaScript is avoided, and content that can be delivered directly is not unnecessarily moved to the browser.
A fast website means less time for visitors to get annoyed.
Accessibility
Accessibility is part of development from the beginning.
Pelneth uses semantic HTML, appropriate document structure, keyboard-accessible interactions, visible focus states, accessible forms, and other practices based on accessibility guidelines.
Accessibility is not something to add after the website has already been built.
JavaScript
JavaScript is useful, but not everything needs JavaScript.
Pelneth tries to keep client-side JavaScript appropriate to what the website actually does. Content and essential functionality should not depend on unnecessary client-side code.
When JavaScript is needed, it should have a reason to be there.
Choosing the right tools
There is no single technology stack that is appropriate for every website.
A simple website may only need static pages and a small number of external services. Another website may require a database, authentication, or more complex application logic.
Pelneth chooses the tools based on the requirements of the project rather than trying to use the same technology for everything.
Built to be maintained
A website should not only work when it is launched. It should remain understandable and maintainable afterward.
Pelneth prefers straightforward architectures and avoids unnecessary dependencies and complexity where possible.
For websites managed by Pelneth, this also means that improvements can be made over time as better approaches become available.