Dev-Log/Blog

Dev Log – 4NERDS-GAMING

Behind the Scenes

Dev Log

Building the 4NERDS Digital Museum

This is the build journal for 4nerds-gaming.com — design decisions, technical fixes, WordPress/Astra battles, content upgrades, research notes, and the small steps that turn a retro gaming archive into a real digital museum.

Send Suggestion

No matching Dev Log entries

Try another search term, remove the topic filter, or reset the DevBlog view.

Dev Log #4 — The premium museum redesign

The biggest visual shift so far happened today: 4NERDS-GAMING moved away from the older synthwave-heavy look and into a more refined premium museum style.

The new direction: less neon overload, more dark archive atmosphere — cream typography, gold accents, deep navy panels, museum cards, curated sections, and a clearer sense that every page belongs to the same digital collection.

1) The Museum page became the design anchor

The Timeline page was reworked from a long scrolling tour into a more accessible exhibit gallery. Instead of repeating lists and route cards, it now focuses on compact museum-style exhibit cards:

  • Curator’s Pick of the Day as a starting point.
  • Museum Map filters for Origins, Arcade, Console, PC, Portable, and Media halls.
  • Preview panel for quick orientation.
  • Read Dossier modal for in-page deep dives.

2) The global header got a full identity pass

The header now follows the same premium direction. The old cyan/pink synthwave styling was replaced with a darker 4NG identity: gold outlines, cream text, compact rounded tiles, and a corrected 4NG badge.

Mobile rule: the three main entry points — Museum, Hardware, and Games — must always stay visible as equal-width tiles. No hidden hamburger menu for the core archive.

3) Hardware, Games, Museum, and DevBlog are becoming one system

The important thing now is consistency. A visitor should immediately feel: “I am inside the same archive, just in a different wing.”

  • Museum: curated historical pathways and timeline dossiers.
  • Hardware: searchable machines, generations, and collector context.
  • Games: archive database with platform, genre, series, and preview logic.
  • DevBlog: transparent build journal for updates, polish, and design decisions.

4) What this unlocks next

With the visual identity now much stronger, the next big step is expansion without chaos: more entries, more related links, better content hubs, and a stronger affiliate/collector layer.

Next up: turning the marketplace and related-entry blocks into a consistent site-wide standard.
Back to top

Dev Log #3 — Platform filter overhaul (goodbye duplicates)

Today was one of those “tiny UI detail → huge quality win” days. The Games page was already strong, but a microscope-level issue was hiding in plain sight: the platform dropdown.

The problem: The dropdown contained entries like “Wii U / Switch” — and when you picked that option, the filter behaved like “must be on both platforms” instead of “show all games that include either platform”.

1) The new rule: each platform appears only once

The dropdown is now cleaned up so it lists platforms individually: Wii U, Switch, PS4, PS5 — no more combined “A / B” entries.

  • No duplicate platforms, no confusing combos.
  • The selection feels like a real database filter.
  • Better UX on mobile — fewer weird edge cases.

2) The important part: inclusive matching

Selecting Switch will now also show games that are Switch + Wii U releases, because the filtering behaves like: “contains Switch”, not “contains exactly Switch-only”.

Why this matters: Multi-platform history is part of the story. You should discover that a title jumped generations — not accidentally hide it.

3) What this unlocks for the site

  • Better discovery: platforms are reliable entry points.
  • Cleaner data model: every game can carry multiple platform tags without breaking UX.
  • Future-proofing: more platforms can be added without combo pollution.

It is one of those changes that seems small, but instantly makes the whole site feel more professional. The Games page is not just pretty now — it behaves like a real archive.

Next up: expanding generations and polishing the Games page visuals even further.
Back to top

Dev Log #2 — Generations rebuilt (and the site became a timeline)

The last couple of days were all about one big goal: turning the “console generations” part of 4nerds-gaming.com from a simple list into a browsable history map.

Milestone reached: the generations page is now stable, expandable, and visually consistent — with enough structure that adding 50 more systems will not break the design.

1) The real work: structure before content

The most important decision was to treat the generations page like an exhibit wall: tiles should be consistent, readable, and sortable — even when hardware families get complicated.

  • Consistent card layout across generations.
  • Clean handling for series vs standalone systems.
  • UX decisions that keep things nerdy, but not chaotic.

2) Fixing the WordPress + Astra reality

A big chunk of time went into making the site behave reliably across desktop and mobile — especially the areas where WordPress themes love to fight back:

  • Sticky navigation behaving differently depending on containers and overflow.
  • Header quirks when tiny CSS changes caused unexpected layout shifts.
  • Mobile banner handling and responsive polish.
Lesson: it is not just “CSS looks right” — it is also “CSS survives Astra’s layout decisions”.

3) Content: the museum feeling is starting to show

Once the structure was solid, we could move faster: adding systems, improving tiles, and building the sense that every click leads to the next discovery.

4) What’s next

  • More generations fully finalized.
  • Even tighter consistency between homepage, games page, and generation pages.
  • More images that feel curated, not random.

The exciting part: the foundation is now strong enough that expanding the archive feels fun — not like rebuilding the website every evening.

Next up: platform selection and search behavior on the Games page.
Back to top

Dev Log #1 — Building a museum that clicks

When I started 4nerds-gaming.com, the goal was not “news” or “reviews” in the classic sense. It was something I personally missed: a place where you can explore video game history like you would wander through a museum — curated, connected, and satisfying to browse.

The core idea: one click should always lead to the next discovery — a console page should naturally pull you into the games, the era, the tech, and the people behind it.

1) The vibe: modern, readable, still unmistakably retro

I love pixel fonts and hard retro aesthetics — but the moment readability suffers, the whole project loses its purpose. So the design direction became: modern UI clarity plus retro atmosphere.

  • Readable first: comfortable line-height, calm panels, clear headings.
  • Retro second: accent colors, subtle grid, and atmospheric highlights.
  • Consistency: every game page follows the same structure so visitors feel at home.

2) The structure: a template that scales

The big lesson: if a site like this grows, it needs a stable template. Otherwise every new page becomes a redesign. That is why game pages are built with a consistent flow: hero, boxart, TL;DR, data section, media gallery, timeline, and gameplay video.

3) The tech reality check: WordPress + Astra can be spicy

WordPress is great for publishing speed, but styling a global header and sticky navigation while keeping mobile behavior perfect is where time goes to die.

  • Headers vanishing unexpectedly.
  • Mysterious grey side rims.
  • Sticky nav breaking because a parent container had the wrong overflow.
  • Mobile banner logic behaving differently than desktop.
Lesson learned: if something is a Header Builder element, it is often safer to change it in Astra’s builder than to fight it with global CSS.

4) The content philosophy: no endless research required

The point is not to replace Wikipedia or giant databases. It is to make the experience fun and connected. If you land on a console, you immediately see the games people actually played. If you land on a game, you see where it fits historically.

5) What’s next

  • Expand console pages across more generations and regions.
  • Add more historical context blocks explaining why something mattered.
  • Improve discovery through related consoles, related games, and timeline browsing.
  • Keep the look clean — premium first, retro flavor second.

If you are reading this: welcome. This site is a passion project — but I am building it with future growth in mind: a structure that can expand for years without turning into chaos.

Next up: Dev Log #2 — Generations rebuilt.
Back to top
DevBlog template note: add new entries by duplicating an existing post block and updating the metadata.
Nach oben scrollen