WebExpress

Posts

WebExpress 2.0.0‑alpha – Why execCommand is Dead

October 24, 2026

The development of modern rich-text editors on the web has undergone a fundamental paradigm shift. The native browser API document.execCommand() is obsolete, generates inconsistent HTML, and prevents precise control over the document flow. Frameworks like Tiptap, ProseMirror, or Lexical demonstrate that the future lies in a strict separation of data and representation. WebExpress is now undergoing a complete migration from error-prone DOM manipulation to a deterministic, state-based approach combined with a modern, block-based layout system. The core of this new architecture is a central JavaScript object in JSON format that defines the document as a tree structure known as an Abstract Syntax Tree. A document consists of a root node whose children are either structural layout blocks or content-based text elements. Each node has a type, optional attributes like formatting, and an array of child nodes. A text section is declared as a paragraph node whose children in turn are text nodes w...

WebExpress 2.0.0‑alpha – The Countdown to Halloween Has Begun

October 19, 2026

The development of WebExpress 2.0.0-alpha continues to progress according to plan. Based on the current status, all major milestones remain on track, and the release is scheduled for Halloween. This would mark a return to a release date that was already chosen for a significant version last year. Over time, this consistency could evolve into a tradition, with major WebExpress releases arriving each Halloween. Current efforts are focused on completing new features, advancing core framework components, and delivering numerous improvements across the architecture, user interfaces, and development tools. Many of the planned enhancements have already been implemented and are currently undergoing integration and testing. As a result, the new version is steadily moving toward completion. Several bug fixes and smaller refinements are still in progress and are expected to be completed before release. As is typical for an alpha version, the current priority is to further improve stability, res...

WebExpress 2.0.0‑alpha – The End of Server Sessions

October 17, 2026

WebExpress currently uses a stateful session model in which a server side session is created for each client. The session ID is stored in a cookie and transmitted with every request. Initially, the session is used solely to recognize the client and is only associated with an identity after successful authentication. User, role, and permission information then becomes available within the session context. As a result, the identity is bound to the session rather than the other way around. This architectural model clearly separates the technical client context from the user identity and has proven itself in numerous applications. However, as requirements for scalability, containerization, and distributed cloud infrastructures continue to grow, this approach increasingly reaches its limits. Because authentication information is tied to the server side session context, session state must be maintained persistently and synchronized across multiple instances. This increases infrastructure co...

WebExpress 2.0.0‑alpha – Native Certificate Management

October 10, 2026

One of the strengths of WebExpress has always been its ability to operate efficiently across a wide range of environments, from small Raspberry Pi installations to larger server deployments. HTTPS support based on Kestrel has been part of the framework for years, and certificates can already be configured directly on endpoints using PFX files. This simple and reliable approach has served WebExpress well, particularly in lightweight and self hosted environments. As the platform continues to evolve, certificate management is becoming increasingly important. Today, HTTPS endpoints are directly coupled to certificate files defined in configuration. While this works perfectly for smaller deployments, it limits future scenarios such as automated certificate management, centralized certificate stores, cloud integrations, and dynamic multi domain hosting. To address these challenges, WebExpress is introducing a native certificate management infrastructure. The objective is to treat X.509 ce...

WebExpress 2.0.0‑alpha – Removal of Bootstrap and Popper.js

October 04, 2026

The release of WebExpress 2.0.0-alpha initiates a radical architectural shift that finally casts off the legacy burdens of past years. The declared goal of this transformation is a drastic reduction in external dependencies, a noticeable performance optimization, and a consistent alignment with modern, native web standards. To achieve this milestone, both Bootstrap and Popper.js are being completely removed from the framework. What seems like a major cut at first glance actually frees WebExpress from unused CSS and external JavaScript dependencies that have simply become redundant in today's browser landscape thanks to modern standards. However, this deep restructuring brings significant technical challenges, particularly affecting the migration of familiar interactive components. One of the biggest undertakings is the complete transition of modals to the native HTML5 dialog element. Previously, dialog windows had to be painstakingly controlled via nested div structures, Aria attri...

WebExpress 2.0.0‑alpha – 8,000 Unit Tests and a Little More

September 25, 2026

In the current development cycle of WebExpress 2.0.0-alpha, the framework has reached an important milestone in terms of quality assurance and stability. The current stage of development now includes more than 8,000 automated unit tests that continuously safeguard and validate a large portion of the framework's architecture. This testing foundation is complemented by extensive JavaScript and Node.js tests that cover client side components, integrations, and build processes. The large number of tests is not the primary goal itself, but rather the result of a consistently pursued commitment to quality. Every new feature, enhancement, and bug fix is accompanied by automated tests from the very beginning. This allows defects to be detected early, long before they can reach production environments. At the same time, it creates a reliable safety net for the ongoing evolution of the framework. The importance of automated testing has increased significantly throughout the development of We...