When I bought AIBuiltProjects.com, I had a domain name and a clear subject, but I did not yet have a finished website structure. The aim sounded simple: create one place for my games, websites, applications and future tools, then document how each one was built with AI assistance. Turning that idea into a site people could actually navigate required many more decisions than the first sentence suggested.
The website was built on WordPress.com with ChatGPT Work helping me shape pages, blocks, menus and content. I was not handing over a complete specification written in advance. I described what I wanted, looked at the result, explained what felt wrong and continued refining it. The construction process resembled the way I had already worked on Unity projects: conversation, implementation, inspection and correction.
Getting from staging to the real domain
One of the first sources of confusion was the address. The site initially appeared through a WordPress staging domain even though I had bought AIBuiltProjects.com. That made the work feel unfinished because the pages existed but the public identity did not yet match the domain I intended people to visit.
Connecting and verifying the custom domain was therefore more than a cosmetic task. It established the permanent URLs that would later be used in Google Search Console, privacy policies, store listings and links from other websites. A project site cannot work as a stable reference if its address is still temporary.
The Projects page needed to describe a system
The first version of the Projects area misunderstood the structure. It presented three individual projects, while my actual idea contained three project families: games, websites, and applications or tools. Gem Forge Idle and Swarmloom Idle belonged under games. GottaPics and AIBuiltProjects.com belonged under websites. Chaos Booth later gave the applications section its first real project.
That distinction changed the purpose of the page. Projects was not supposed to be a fixed collection of three cards. It needed to become a durable entrance to categories that could keep growing. The labels were simplified to Play, Web and Tools, unnecessary numbering was removed, and the visual hierarchy was strengthened so that visitors could understand the structure quickly.
Permanent project pages then became the centre of the system. A project page explains what the game, application or website is. Connected blog articles record individual stages. Categories bring those articles together. This prevents a visitor from landing on one isolated post with no route back to the larger story.
Building navigation around real visitor behaviour
A navigation menu can look tidy and still hide too much. Initially, hovering over Projects revealed the main project pages, but there was no obvious way to continue from a project to its development articles. The solution was to add a separate Blog area and use project-specific categories, while keeping the parent pages available from Projects.
Legal pages needed similar care. The site has its own Privacy Policy, while games and applications require separate policies. Sending every Privacy Policy click to a directory of unrelated documents would be confusing. The main link therefore remains the policy for AIBuiltProjects.com, and a separate Game & App Legal area collects the policies and terms belonging to individual products.
The same principle guided the move of game policies away from GottaPics. They made sense there only before AIBuiltProjects.com existed. Once this site became the public home for the projects, their legal pages also belonged here.
Creating a visual identity
The original header used plain text. I wanted the site to have a recognisable logo that could work as a long horizontal mark, while its first letter could become a transparent favicon. Several versions were explored before I selected the direction: AI in purple, Built in black and Projects carrying the yellow accent.
Even after choosing the idea, the spacing needed repeated adjustment. Letters appeared too close together, the gap between the symbol and the wording was too wide, and one part looked slightly higher than the rest. Those are small details, but a logo displayed on every page makes small alignment problems difficult to ignore.
The final identity now belongs to the site rather than sitting on top of it. Its purple and yellow colours match the page accents, and the transparent A favicon can remain readable without being trapped inside a square background.
Choosing what should change automatically
The homepage includes a current project panel. It would have been possible to make that section update automatically whenever the newest project was published. I decided against it. The newest item is not always the project I most want to feature. A website article could replace a game or application simply because it had a later date.
The section therefore remains under manual control. At the time of writing, Chaos Booth is the selected current project. It will stay there until I deliberately choose another one. That decision is a good example of the role I want AI to play: automation is useful only when it supports the editorial choice rather than quietly replacing it.
The result is a framework, not a finished archive
The website went live with a working structure: Projects, Blog, About, Contact, the site Privacy Policy, individual project pages and dedicated legal pages. It also gained category archives that display articles as cards with featured images instead of presenting complete posts one after another like an endless document.
The framework can now hold new work without rebuilding the whole site each time. A game can receive a parent page, a category, a series of development posts and links to the platforms where it becomes available. A website experiment can use the same system. An application can have its public story separated from its privacy policy and terms.
The AI Built Projects project page keeps the permanent overview. This article records how the structure behind that page was assembled: not in one perfect attempt, but through a sequence of practical corrections until the site began to behave like the growing archive I had imagined.
Leave a Reply