Building for Real Realities: Why We Eliminated Em Dashes and Standardized Equal Thirds
When you are writing code that represents a physical and digital studio from East London, South Africa, aesthetic choices quickly become engineering constraints. This week, our main repository ( CreativelyNanda.co.za ) underwent a massive structural refinement. We didn't add a flashy new database or migrate to an exotic edge runtime. Instead, we focused on the bones: equal thirds, strict color…
When coding for a digital and physical studio spanning East London, South Africa, aesthetic decisions transform into engineering constraints. This week, our primary repository (CreativelyNanda.co.za) experienced a significant structural overhaul. Rather than introducing a novel database or migrating to an unconventional edge runtime, we concentrated on fundamental elements: equal thirds, consistent color tokens, print stylesheets, and rigorous typographic simplicity.
Our discussion centers on the design choices behind this week's commits. Firstly, the equal-thirds layout mitigates the often unnoticed yet detrimental impact on frontend aesthetics. Across our platforms, including Notion integrations, business archives, and the Poem Wall, we adopted an equal-thirds structure. This approach offers users consistent mental models when navigating complex literary and commercial content.
We extended this structural pattern to legal pages, roots, testimonials, and imprints, providing a steady foundation regardless of the content—be it a poem or a physical volume.
Secondly, we tackled the challenge of translating digital design systems to physical print. We adjusted the navy pages to ensure accurate color representation and precise positioning of elements, such as buttons and masthead pockets, on paper. This consideration is crucial in regions where power outages are common, as it ensures the web page remains functional even when offline, mirroring the offline capability of VarsityOS for students managing NSFAS budgets.
Thirdly, we adopted a strict typography rule by eliminating all em dashes from our site. Em dashes frequently serve as a crutch for complex architectural logic in copywriting. By removing them, we prompted our prose to rely on pauses, hinge words, and structured rhythm. Our updates to X-ray poetry modes and garden layouts adhered to this stylistic constraint.
Lastly, we addressed potential pitfalls, such as stray comments in JSX code and CSS remap selector conflicts. A stray comment in a JSX conditional caused a build failure, highlighting the importance of vigilance in JSX parsing. Additionally, we cleaned up CSS remap selectors to prevent specificity wars. Our experiences with applications like AdminOS and the K53 Drill Master, which undergo rigorous audits against official documentation, underscore the importance of discipline in maintaining clean codebases.
Proper token management and rigorous testing of build logs are essential practices that ensure the longevity and reliability of complex applications.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.