Redirects and Legacy Content
This page lists the old site structure, redirects, and legacy material so visitors from outdated bookmarks can understand where the content moved.
What was the original CodeKing site?
The original site ran as a studio that offered web design and mobile app development under the slogan “we style your business.” It presented sections for services, references, and contact details, giving clients a clear path to the agency’s offerings while it was active. The layout reflected a typical service‑oriented agency, with navigation aimed at prospective customers during that period.
After the studio closed in 2014, the architecture was replaced by a notebook focused on software development and AI. The old pages were not migrated, so many URLs now resolve to 404 errors. The current platform no longer hosts commercial service pages; instead it records experiments, measurements, and code that were actually executed.
Why do old URLs return 404 errors?
When the site transitioned from an agency to a technical notebook, the folder structure and naming conventions were overhauled. Links that once pointed to “Leistungen” or “Referenzen” now reference paths that no longer exist, causing the server to return a 404 response. The change was intentional to remove obsolete service listings and focus on developer‑centric content.
The 404 pages also appear because legacy components such as the DZCP CMS system and custom scripts were removed from the primary domain. Those pieces were tied to the old business model and are not part of the present AI‑driven workflow. Visitors with old bookmarks should consult the archive section for any preserved documentation.
How can I find the old service pages?
The archive section stores snapshots of former pages, including the “Leistungen” and “Referenzen” listings. Those snapshots retain the original text and layout but are read‑only and hosted separately from the active notebook. They serve as a historical record rather than functional service pages, allowing developers to see how the site communicated its offerings before 2014.
To reach a specific old file, locate its entry in the archive index and follow the provided link. If the file was never archived, it is no longer available on the domain. The archive is deliberately limited to material that still offers insight into the site’s evolution.
Where is the current technical notebook?
The notebook lives under the main navigation items “Notes,” “Coding,” and “AI in practice.” Each section contains concrete measurements, code snippets, and step‑by‑step explanations of AI‑assisted development. The content is written for developers who ship code, avoiding marketing language and focusing on reproducible experiments.
All entries are tied to real builds that were executed on the author’s machine. The notebook therefore provides a transparent view of the development process, from data collection to final implementation, and includes links to the underlying source files where appropriate.
What happened to the DZCP CMS and scripts?
The DZCP CMS system and assorted scripts were core tools during the agency era, offering content management and custom functionality for client sites. After the transition, those components were retired and are no longer maintained on the primary domain. Their removal aligns with the shift toward AI‑driven workflows rather than legacy CMS solutions.
Although the original code is not hosted on the main site, copies may exist in the archive if they were deemed historically valuable. Developers interested in the implementation can search the archive for the relevant filenames, but should treat them as reference material rather than supported software.
How do I navigate the legacy and current content together?
Start by checking the archive for any historical pages you need, then move to the notebook for up‑to‑date technical guidance. The internal links at the top of each page point to “Notes,” “Coding,” and “AI in practice,” which are the primary hubs for current material. This workflow lets you compare past service descriptions with present development practices.
The site also provides a simple breadcrumb trail that shows whether you are viewing an archived page or a notebook entry. By following that trail you can jump between legacy documentation and modern code examples without losing context, ensuring a smooth transition between the two eras of the site.
Questions
Why do some links show a 404 error?
The site structure changed after the studio closed in 2014. Old bookmarks pointing to specific service pages or CMS components may no longer exist.
Is the agency still offering web design services?
No. The studio ceased operations in 2014. The site now functions as a technical notebook for software development.