New pages

13 March 2026

• 14:4214:42, 13 March 2026 Progressive Enhancement and Graceful Degradation (hist | edit) [6,335 bytes] Dex (talk | contribs) (Created page with "= Progressive Enhancement and Graceful Degradation = '''Summary:''' Progressive Enhancement and Graceful Degradation are two complementary design philosophies used to build resilient, accessible, and future‑proof systems. They describe how a system behaves when features, capabilities, or assumptions are missing — whether by design, constraint, or failure. This article explains both approaches, where they came from, how they differ, and how they are applied in real...")
• 14:3514:35, 13 March 2026 One Data Model, Many Representations (hist | edit) [5,428 bytes] Dex (talk | contribs) (Created page with "= One Data Model, Many Representations = '''Summary:''' Modern web systems often create unnecessary separation between websites and APIs. In reality, both are simply different representations of the same underlying data. When designed correctly, a website can function as an API, and an API can render a complete website — without semantic loss, duplication, or inconsistency. This article explores that principle and the machine‑readable HTML technologies that make i...")
• 14:0614:06, 13 March 2026 Accessibility, ARIA, and Semantic HTML (hist | edit) [8,061 bytes] Dex (talk | contribs) (Created page with "= Accessibility, ARIA, and Semantic HTML = '''Summary:''' Accessibility is not a feature, a checklist, or an optional enhancement. It is the discipline of ensuring that meaning, structure, and behaviour remain usable when visual presentation is removed. This article explains how semantic HTML, ARIA, and backward‑compatible design work together — and why misuse of ARIA often makes accessibility worse, not better. == Context == Accessibility is frequently misund...")
• 12:4312:43, 13 March 2026 Digitizing Paper Forms and Business Processes - What to Remember and What to Forget (hist | edit) [10,782 bytes] Dex (talk | contribs) (Created page with "= Digitizing Paper Forms and Business Processes — What to Remember and What to Forget = '''Summary:''' Paper forms are not mistakes to be erased; they are artefacts of real work that evolved under physical constraints. When we digitize, we should preserve what paper gets right (clarity, authority, linear flow) and retire what it does poorly (long, multi‑party, storage‑heavy, silo‑creating processes). This article explains how to analyse the business process be...")
• 12:2812:28, 13 March 2026 Tabular Data: From Paper Ledgers to APIs (hist | edit) [7,767 bytes] Dex (talk | contribs) (Created page with "= Tabular Data: From Paper Ledgers to APIs = '''Summary:''' Long before computers existed, organisations recorded information in tables. While the technologies used to store and serve data have evolved — from paper ledgers to flat files, database servers, and modern APIs — the fundamental shape of most business data has remained remarkably consistent. This article explores that continuity, and how successive generations of systems have focused less on changing the...")
• 11:4511:45, 13 March 2026 How Computers Interact with HTTP Endpoints (hist | edit) [3,422 bytes] Dex (talk | contribs) (Created page with "= How Computers Interact with HTTP Endpoints = '''Summary:''' This article explains how computers programmatically communicate with remote systems using HTTP-based interfaces. It covers common web service approaches including XML-RPC, SOAP, RESTful APIs, and JSON-RPC, explaining how they differ, why they exist, and where each is still encountered in real-world systems. == Context == HTTP is often thought of as a protocol for humans using web browsers. In practice, it i...")
• 11:2311:23, 13 March 2026 HTTP (HyperText Transfer Protocol) (hist | edit) [9,348 bytes] Dex (talk | contribs) (Created page with "= HTTP (HyperText Transfer Protocol) = '''Summary:''' HTTP is an application‑layer protocol that defines how clients and servers exchange representations. While often described as simple and stateless, real‑world HTTP behaviour is shaped by decades of evolution, intermediaries, infrastructure policy, and layered usage. Understanding HTTP as a '''container protocol''' is essential to designing, publishing, securing, and troubleshooting modern systems. == Context == H...")
• 10:4510:45, 13 March 2026 Ethernet, Frames, and Thinking in Containers (hist | edit) [10,416 bytes] Dex (talk | contribs) (Created page with "= Ethernet, Frames, and Thinking in Containers = '''Summary:''' Ethernet is the foundational link technology of modern networking. It was designed as a practical engineering solution long before formal network-layer models existed. Understanding Ethernet frames and encapsulation as physical containers makes concepts such as MTU, VLANs, and packetisation intuitive rather than abstract. == Context == Ethernet was developed at Xerox PARC in the early 1970s to solve a loca...")

5 February 2026

• 10:0910:09, 5 February 2026 PUSH Technologies - An Overview (hist | edit) [23,681 bytes] Dex (talk | contribs) (A comparison of PUSH technologies that deliver real‑time updates without polling, including SSE, WebSockets, MQTT, Long‑Polling, and Web Push.)