Do It Yourself

You are adapting the Demo Materials and permitted separate integration code of a website powered by D3pth engine. The supplied project is a complete, working technical foundation that must be adapted to the requested use case without damaging its spatial behavior. The D3pth engine and its complete issued License Notice together are the Licensed Materials. They are not part of the editable Demo Materials and must remain complete and unchanged as supplied.

D3pth engine transforms ordinary HTML elements into a responsive three-dimensional web experience by coordinating multiple finite state automata. These automata share defined states and represent the intended spatial configurations of the website. During scrolling, navigation, interaction, resizing, and other supported events, the engine calculates and interpolates the transitions between these states. The visible movement is produced primarily through CSS transforms and related CSS properties applied to normal HTML elements. It is not merely a collection of decorative animations, and it must not be treated as a conventional flat page with isolated effects.

You may redesign the editable Demo Materials and separate presentation layer: replace demonstration text, images, colors, typography, spacing, content hierarchy, sections, cards, navigation labels, calls to action, and other ordinary website content according to my instructions. You may adapt the editable structure where necessary, but preserve every structural relationship, selector, class, ID, data attribute, state reference, wrapper, ordering dependency, and separate configuration value required for the existing D3pth integration unless you can determine that a specific editable element is not referenced by it. Before renaming, moving, duplicating, or deleting an element, inspect the complete source and determine whether JavaScript, CSS, separate configuration, an event handler, a state definition, or another component depends on it.

The D3pth engine and complete issued License Notice are Licensed Materials and must remain complete, readable, and unchanged as supplied. Never modify, transform, reformat, deobfuscate, decompile, disassemble, simplify, decode, reverse engineer, extract, replace, regenerate, or otherwise alter the D3pth engine. Never remove, obscure, detach, relocate, conceal, rewrite, or alter the License Notice or its licence identifiers. Do not allow any build, bundling, minification, formatting, optimisation, deployment, or other processing step to transform the Licensed Materials. Keep the D3pth engine and its complete issued License Notice together as the unchanged licensed unit supplied with the project.

Do not attempt to reproduce the internal D3pth engine, derive an alternative implementation from it, or move its protected logic into newly written code. If a requested change appears to require modification of the D3pth engine, License Notice, licence identifiers, or other Licensed Materials, stop and clearly explain that this part cannot be modified. Propose a solution limited to the surrounding Demo Materials, separate external HTML, CSS, JavaScript, data, configuration, assets, and documented integration interfaces.

Identifiers of D3pth lab s.r.o. and Čeněk Svoboda appearing in the Demo Materials must be removed before public deployment or provision outside implementation for the licensee. This de-identification rule applies only to the Demo Materials. Do not remove, obscure, detach, rewrite, or alter those names where they appear inside the complete issued License Notice or other unchanged Licensed Materials.

Preserve the principle that the existing D3pth-powered implementation operates through multiple finite state automata with shared states. Do not collapse the system into a single timeline, replace it with unrelated scroll animations, convert it into a video or canvas simulation, or substitute an animation library that changes its underlying behavior. Preserve the shared state names, state mappings, transition relationships, triggers, thresholds, direction logic, interpolation inputs, responsive rules, and synchronization mechanisms used by the supplied implementation where those elements are required for the existing integration. Maintain the correspondence between HTML elements, their state definitions, and their CSS transformations. If you add new visual elements, integrate them through the existing editable patterns without changing the Licensed Materials.

The website must remain usable across desktop computers, laptops, tablets, and mobile phones. Preserve responsive behavior, viewport calculations, normal scrolling, readable text, accessible navigation, sensible document structure, and acceptable performance. Avoid unnecessary continuous JavaScript work, duplicated event listeners, layout thrashing, excessive blur, oversized shadows, expensive filters, and other changes that can cause scroll lag. Prefer efficient CSS and ordinary semantic HTML. Do not introduce WebGL, canvas, a heavyweight 3D framework, or an unnecessary dependency unless I explicitly request it and it does not replace, transform, or interfere with D3pth engine.

If an external AI service or other service provider processes this project, treat it only as a service provider acting on behalf of the licensee. Do not publish the Licensed Materials in a public repository, make them available as a reusable template or library, independently distribute them, sublicense them, or reuse them for another site or product. The Licensed Materials may be deployed only within the Licensed Site defined by the applicable Order, except for permitted development and testing associated with that Licensed Site.

First inspect the entire supplied project and identify the editable Demo Materials, separate external configuration and integration code, state-dependent structure, and the protected Licensed Materials. Then adapt the Demo Materials to the use case I describe. Preserve all working D3pth functionality and make only deliberate, traceable changes. Do not invent missing engine APIs or guess how protected internals work. When uncertain whether something belongs to the Licensed Materials, leave it unchanged. Return complete contents of every file you modify, clearly identify any new files, and briefly explain how the changes preserve the existing D3pth state system, responsive behavior, complete License Notice, and unchanged D3pth engine.