Technical Note

Introduction

The current Level73 website was designed and developed as a lightweight, progressively enhanced web platform focused on long-term maintainability, accessibility and performance.

Rather than relying on a large CMS or frontend framework, the website is powered by a small custom PHP application built around an MVC architecture. This allows us to manage page composition, reusable components and potential database integrations while keeping the overall infrastructure intentionally minimal and maintainable.

The frontend was developed using modern CSS features and browser APIs, including technologies that are not yet fully part of the current browser baseline. We intentionally embraced progressive enhancement as a design principle, using media queries, container queries and feature detection through the `@supports` at-rule to adapt behaviour and presentation according to browser capabilities.

As a consequence, the website may produce slightly different visual experiences across browsers and devices. These differences are intentional and do not compromise usability, accessibility or content availability.

We believe the web should remain resilient and adaptable rather than visually identical across every possible environment.

Particular attention was given to semantic structure, accessibility and frontend efficiency.

Like every digital system, however, these concerns are never truly static. They evolve continuously alongside technologies, standards and user needs. For this reason, we consider them ongoing infrastructural responsibilities rather than fixed technical achievements.

This website is therefore not intended as a finished object, but as an evolving system subject to continuous observation, refinement and incremental improvement over time.

Accessibility

Accessibility was considered from the earliest stages of the project rather than introduced as a late-stage compliance layer.

The website was structured semantically in HTML first, focusing on document hierarchy, navigability and content relationships before defining visual presentation rules through CSS. This approach allowed us to minimize unnecessary markup while leveraging native browser capabilities and modern CSS features as much as possible.

Particular attention was given to keyboard navigation, ensuring that the website remains operable without relying exclusively on pointer-based interaction.

We also implemented specific media queries designed to respect users who prefer reduced or less invasive motion. Certain animations intentionally remain active as part of the website's communicative language and visual identity; however, these effects were designed to avoid disruptive layout shifts or interactions that could compromise readability and usability.

Color contrast and readability were evaluated using professional accessibility and editorial analysis tools in order to maximize readability across devices and viewing conditions.

Accessibility, however, is not treated as a binary state or a completed checklist. Like performance and maintainability, it is understood as an ongoing infrastructural responsibility requiring continuous observation, testing and incremental refinement over time.

Privacy

This website intentionally minimizes data collection and avoids unnecessary tracking technologies.

No advertising trackers, profiling systems or third-party marketing platforms are used. We believe digital infrastructure should respect users by default, collecting only the information strictly necessary for technical operation and communication.

Whenever possible, the website relies on native browser capabilities and self-hosted assets in order to reduce external dependencies and unnecessary data exposure.

Messages submitted through the contact form are processed through Google Workspace email services exclusively for communication purposes.

Privacy, like accessibility and maintainability, is treated as an infrastructural concern rather than a secondary compliance exercise.

Maintainability

The website was intentionally designed to minimize unnecessary complexity and reduce long-term infrastructural overhead.

External dependencies were kept to a minimum and are limited primarily to backend-related functionality. On the frontend, we intentionally avoided large frameworks and abstraction layers, choosing instead to rely on native browser APIs and modern web standards, which we considered sufficiently capable for the type of platform we wanted to build.

This approach helped keep the frontend lightweight, readable and easier to evolve over time.

A small build process is used to optimize and minify CSS and JavaScript assets for production environments. During development, however, the CSS architecture remains separated into distinct layers and sections, making it easier to navigate, maintain and evolve incrementally before recompiling into a unified production file.

Where possible, assets were designed to remain lightweight and resolution-independent. All interface imagery and graphical components are delivered as SVG files in order to improve scalability, rendering consistency and performance across devices.

More broadly, we believe maintainability is not simply a technical concern, but an ethical one. Systems that become unnecessarily fragile, opaque or difficult to evolve inevitably generate operational, economic and human costs over time.

For this reason, we try to design infrastructures capable of remaining resilient and maintainable well beyond their initial deployment.

Interoperability

This website does not currently rely on external APIs or third-party platform integrations. Its architecture was intentionally designed to remain focused and self-contained.

At the same time, interoperability remains a foundational principle in the way we think about digital infrastructure more broadly.

We strongly value open standards, open data practices and systems capable of communicating through transparent and well-defined interfaces rather than through opaque or tightly coupled dependencies.

A core aspect of this approach is the separation of concerns between infrastructural layers. We believe systems should be designed in ways that allow presentation, data, logic and communication layers to evolve independently whenever possible.

This separation makes platforms easier to maintain, extend and adapt over time as organizational needs, workflows and technologies change.

Rather than treating interoperability as a purely technical feature, we see it as a long-term infrastructural strategy that helps reduce fragility, avoid unnecessary lock-in and preserve the ability of systems to evolve sustainably.

Closing Notes

Complexity is often inseparable from human practices, relationships and organizations. Each person carries a different way of understanding the world, collaborating with others and interacting with technology.

We do not believe the solution is to flatten complexity into artificial simplicity. Complexity is not inherently negative; in many cases, it is a form of richness that needs to be understood, integrated and negotiated thoughtfully.

At the same time, not every layer of complexity should be transferred directly onto digital systems or onto the people using them.

Complex problems are often composed of many smaller problems. Large objectives are usually built upon small operational needs. Sustainable infrastructure rarely emerges from a single grand solution, but rather from an ecosystem of smaller, interconnected decisions evolving over time.

Over the years, we have seen frameworks, libraries and programming languages emerge with enormous enthusiasm, only to later disappear or become abandoned under the weight of changing trends and expectations.

In an increasingly noisy technological landscape, we prefer a more modest approach.

We prefer technologies that have demonstrated resilience over time, building digital ecosystems capable of evolving gradually rather than collapsing under cycles of hype and replacement.

The culture of “ship fast” often becomes exhausting — both technically and humanly. Instead, we prefer incremental improvements developed carefully, discussed openly and shared progressively with partners and users.

We believe every participant in a digital ecosystem deserves to have their voice heard. And as developers, designers and system architects, we believe it is our responsibility to listen.