Why 8,000 Pages of Cyberpunk 2077 Documentation Still Wasn't Enough

According to Insider Gaming, CD Projekt Red used a Digital Dragons panel to explain one of the biggest mistakes behind Cyberpunk 2077, The Witcher, The Witcher 2: Assassins of Kings, and even later work on the Phantom Liberty DLC: documentation that grew past 8000 pages without becoming a usable shared asset. The studio says The Witcher 4 and Cyberpunk 2 are now being built under reworked processes designed to stop that from happening again.

The more important point here is not that CDPR had a lot of documents. It is that a huge volume of documents failed to turn into durable team knowledge. For a studio building large RPGs, systems, quests, scripts, toolchains, and outsourcing pipelines all move at once. Once information is split across platforms, or documentation stops keeping pace with development, more pages can actually make things harder to search, harder to verify, and less useful overall. CDPR's own example is telling: during the original The Witcher era, the team lacked long-term planning for the years ahead, and when the company later revisited that game for The Witcher Remake, much of the technical knowledge from that period had effectively disappeared.

At the panel, technical writer Jarosław Ruciński and senior technical writer Adrian Fulneczek discussed the development problems that surfaced during Cyberpunk 2077. They said documentation management was one of the studio's biggest mistakes across Cyberpunk 2077, The Witcher, and The Witcher 2: Assassins of Kings. Ruciński noted that the remake project, which aims to rebuild the classic game to modern standards, discovered that almost no technical knowledge from that era had been preserved. One reason The Witcher Remake can still move forward, he said, is that the project includes many longtime CDPR staff who can fill those gaps from experience.

That makes this more significant than a routine technical bug. Bugs can be fixed at the surface level. But if a studio cannot preserve knowledge in a reusable, transferable, traceable form, every new project starts to feel like rebuilding the foundation. That drives up production costs, communication errors, and delay risk. CDPR described Cyberpunk 2077 as so large in scope that development was almost like starting from scratch. The implication is clear: the studio did not simply fail to produce information; it failed to structure that information in a way future teams could actually use.

The same issue also carried into the Phantom Liberty DLC, which shows this was not just an old legacy problem from an earlier era. After moving to Confluence Cloud, some documentation remained local while other parts lived in the cloud, making it difficult for both CDPR's internal teams and external partners to piece together the full picture. In any large-scale content production pipeline, that is a dangerous setup. Fulneczek's advice was blunt: if possible, do not split materials across different platforms or different tools, and if you must, the relationships between them need to be made absolutely clear. That is less a writing tip than a baseline rule of project management.

For anyone waiting on The Witcher 4 or Cyberpunk 2, the value of this story is mainly about expectations. CDPR says it has established new development standards and a new definition of done, with documentation quality now treated as one of the core requirements before a project can move into its next development phase. In other words, process quality is no longer background infrastructure; it is becoming part of the gate that determines whether work can continue.

That is a positive long-term signal, but not a short-term reason for unconditional preorders. CDPR has already shown that it can make top-tier narrative RPGs, and it has also shown how costly it becomes when a large project loses control of its process. The encouraging part is that the studio is now naming the problem clearly and trying to reuse lessons between The Witcher 4 and the broader Cyberpunk projects. For players who follow big single-player releases, the thing worth watching is not the promise itself. It is whether every future reveal shows a steadier, more consistent production rhythm.