Technical notes

This page gathers technical reflections on structure, simplicity, autonomy and long-term system sustainability.

Technical articles on web development, software architecture and the design of simple, durable and autonomous systems.

This is not a news feed, and not a collection of tutorials. It is a space to document a way of designing systems: clear, predictable, and maintainable over time.

Why this section exists

Palks Studio builds structured technical tools. Behind each tool, there are architectural decisions and trade-offs (simplicity, dependencies, readability, autonomy).

These notes explain those decisions, define principles, and make the design logic explicit.

Factur-X EN16931: why your invoice is probably not compliant

PDF/A-3, XSD, Schematron: three compliance levels most e-invoicing solutions fail to fully validate.

Read the note

• A reflection on the complexity that strengthens a system, and the kind that slowly makes it fragile and unreadable.
• Why real-time can unnecessarily complicate simple systems
• VS Code environment: local control and project stability
• Static website architecture: performance, SEO and controlled structure
• Local chatbot architecture: control, logic and predictable systems