Site guide

Purpose, principles, design, architecture, licensing, and maintenance.

1. Purpose

This site brings together writing, software and creative work by Andraž Đurič. It provides shared structure without pretending that an essay, a Minecraft build, a browser utility, and a private archive are the same kind of object.

The work aims to support the persistence of whoever encounters it through understanding, practical capability, efficiency or creative experience. Keeping the work understandable, portable and open to continuation where possible supports its availability; preserving the work is not itself evidence of a benefit to whoever encounters it.

This Guide makes the platform self-describing. A visitor, future maintainer, or AI system should be able to learn how the site is meant to work from the site itself. The public Guide and the repository documents describe the same system at different levels of technical detail.

About this site explains the platform’s purpose. About the author introduces the person behind it, his motivations, politics and approach to AI collaboration.

2. Scope and principles

The work shares a platform, visual system, and a small set of public commitments. It does not make every project follow one epistemic or documentation template. Requirements follow the kind of work, its complexity, and the claims it actually makes.

Supporting persistence is an aim, not an established effect of every item or encounter. Each work must still be judged by what it actually offers and does. Creative work does not need to demonstrate productivity value to belong here, and the shared aim does not replace specific limitations, evidence or permissions.

For claim-bearing work. Build maps that reality can correct.

Where a work makes factual, analytical, or philosophical claims, it should expose the evidence, assumptions, scope, uncertainty, and conditions that could change it. Confidence belongs to individual claims rather than transferring automatically from the surrounding document or project.

Platform-wide commitments

Identifiable: Each work states what it is, who made it, its present status, and where it belongs.
Rights stated: An operative licence or the absence of one is explicit, including relevant third-party boundaries.
Inspectable: Purpose, material limits, dependencies, and provenance are supplied where they affect understanding or use.
Portable where applicable: Source, documents, worlds, and exports remain usable outside one host when a portable form exists and can lawfully be supplied.
Non-extractive: This site and its first-party tools do not make access conditional on surveillance, manipulation, or lock-in.

Requirements follow the work

Kind	What travels with it	What is not imposed
Writing	Claim type, sources, scope, assumptions, uncertainty, standing, and correction conditions where they bear on the conclusion.	A fixed apparatus on every text. Short practical or reflective pieces may remain short.
Creative	Creator, title, date or version, medium, credits, third-party material, licence, and any instructions needed to use the work.	Evidence ledgers, falsification conditions, or a theory of the artwork merely for formal symmetry.
Software	Purpose, supported environment, inputs and outputs, data behaviour, status, limitations, source and build guidance, test standing, and licence where relevant.	Intellectual-document grammar or explanations that do not help operation, inspection, maintenance, or reconstruction.

Portfolio grouping is proportional too. Work is the umbrella for the catalogue. Software distinguishes broader projects from mini tools with a bounded purpose. Mini describes scope, not quality, usefulness, build effort or completion. Creative retains its existing Mini projects grouping.

Self-description is proportional rather than maximal. A Minecraft build pack may need a short readme with version, compatibility, installation, credits, and licence; it does not need a document explaining how it could be disproved. A complex app may need architecture, data boundaries, tests, and reconstruction instructions. The object carries the explanation that helps someone understand, use, preserve, or continue it—no more by default.

3. Design system

Every visible element must carry information, establish hierarchy, enable action, or improve comprehension. Ornament without a job is removed. Restraint is not an aesthetic pose; it protects signal.

Shared visual rules

Image Converter is the visual reference for repeated interface elements; the main site documents and versions the governing contract.
Every family site loads the same executable interface stylesheets rather than separately approximating shared elements.
All four themes preserve the same hierarchy; Light Gray is the first-visit default, and one choice follows the visitor across the `andrazdjuric.com` family.
Settings offers System, DM Sans, Outfit, and Outfit headings with DM Sans body text. Outfit is the first-visit default; explicit choices are remembered across all six sites. Platform and project Guides use the shared sans-serif documentation grammar. Serif is reserved for long-form intellectual work.
Project names in cards carry their identity colours, matching the coloured parts of the software titles on their own sites. Project-card surfaces and borders remain neutral. Homepage categories have centered bold names with smaller muted publication counts beneath, following the Exocortex module-card hierarchy.
Project homepages place their icon beside the title, using one canonical identity shared with catalogue cards and browser tabs. Subject words carry the project colour where the identity calls for it; action words retain the normal theme foreground. Introductions and purpose passages are centered; forms and Guide text keep their task-appropriate alignment. Software shows one compact Test/Complete · maintained/unmaintained · version line beneath its introduction.
Music entries use compact cards in a four-column grid on wide screens, two columns at intermediate widths and one column on phones; full titles wrap and listening links align within each row. Catalogue cards contain the project name, description and destination. Status and licence details remain on the Status page and in each project’s own site and Guide, so the cards can stay compact.
A quiet Explore with your AI panel follows the complete Work section, including expanded categories. Work keeps a shallow browse tree: Writing, Software and Creative. Software separates broader projects from Mini tools; Creative retains its existing Mini projects grouping. Every work has one canonical visible home; cross-cutting purposes, platforms and contexts remain discovery metadata for the AI layer rather than duplicate cards.
Within each category and scale, owner-pinned projects come first in their explicit rank and all remaining projects sort alphabetically by public display name. Software Mini tools pins Lattice Studio, Capture & Paste, Window Layout, Mouse Parker, Hide All, Download Spots and Clipboard History as its first seven. Future agents may not invent pins.
Semantic control colours and labelled project identity colours are separate systems. Lost Media Forge may use a Minecraft-associated green while success states remain explicitly labelled.
Meaningful nested boxes use five subtle, theme-aware depth tones, with lighter category headers and progressively darker child cards in Dark and Pitch Black. Light themes keep white parents and slightly darker children. Further nesting retains the fifth tone, preserving readable text. The skeleton map and homepage category/project hierarchy share this rule; ordinary unrelated cards do not acquire extra depth just because of page markup.
A navigation entry for the exact page already displayed becomes muted, readable, non-clickable text. It has no action hover or keyboard stop. The skeleton map labels its own entry “you are currently here”; footer utility entries and Minecraft index navigation follow the same current-page rule. Parent links, in-page jumps and selectable controls remain usable.
Tree lines end at the final offshoot, with the same corner rounding as their boxes. Expanded descendants and smaller screens preserve that ending.
Cards use solid surfaces, quiet neutral borders and soft shadows. Light Gray has white cards above a pale gray page; the dark themes use lighter dark cards. Compact nested boxes receive gentler shadows, and dialogs sit above the page. Text actions retain visible underlines.
Content links use one cohesive marker family: internal andrazdjuric.com-family navigation uses a horizontal right arrow, external destinations use a 45-degree up-right arrow, and file/artifact downloads use a download symbol. Shared navigation is otherwise markerless; Main site has a trailing left arrow and Buy me a coffee keeps its external marker. Text links share a thin underline. These markers do not change tab behavior; buttons retain their own action icons.
Every page except the main homepage has one shared return row below the header. Main site has a trailing left arrow and opens the main homepage; deeper pages add named parent links, such as Main site / About on About the author. Parents follow the site hierarchy rather than browsing history. The current title stays below the row. Parent links use the current project’s interaction colour on hover and keyboard focus. Long names wrap, and the row remains available when the header is hidden.
The Site skeleton map under About shows the site, projects and connected destinations as expandable branches. Select a page for details, then View site. Categories and visual groups do not change parent navigation. Blog coverage is dated; article relationships and claims have not been assessed.
Footers place Contact on the left and Guide • Settings on the right. The named parents above the page provide the return path to the current site or project. Guide and Settings use local project pages where they exist, otherwise the main site’s pages. Footer labels wrap when space is tight. Contact opens the shared contact page in a new tab. The main homepage omits the extra feedback prompt; individual tools and subsites retain it.
Spacing, borders, corners, controls, typography and recurring composition come from shared primitives rather than page-specific approximations. Equivalent semantic roles—project intros, release cards, ordinary cards, benefit facts and terminal notes—must use their canonical components.
Colours have related pale and saturated treatments. A temporary press changes the control while held; selected options retain a tinted fill and accent edge afterward. Text stays readable, keyboard focus has its own outline, and colour samples and previews keep their original colours.
Motion is functional and restrained. Repeated interface chrome has no ambient animation.
No icon font, emoji chrome, non-semantic ambient animation, engagement badge, or decorative dashboard statistic.
Downloadable software uses one release-card order: metadata, primary artifact, setup/caveat, alternate artifacts, source, licence, checksums, then contextual documentation. Missing data removes a slot.
The footer is the generic Guide doorway. Body documentation links are contextual and name the subject; generic Guide and Return/Home links are not duplicated in page content.
Compact benefit/trust facts use semantic icons; ordinary feature cards are text-first by default; terminal qualification notes are centered and icon-free.
When a new visible semantic role has no established rule, future maintainers inherit all applicable constraints first, extend the shared system when one reusable answer is clear, and ask the owner before establishing an ambiguous new precedent.

Category counts describe the work available: published writings and prompts, software projects and mini tools, and creations in this site’s catalogue, including labelled samples. Each creation or pack counts once; release variants and update posts do not increase the total. Numbered revisions of one writing count once, as do application versions. The writing index is checked during maintenance against a dated feed or export; the homepage does not request external publication data when you visit.

Convergence does not mean uniformity. Editorial pages retain generous reading space; tools retain denser working surfaces. Shared primitives make them recognizably related while each project keeps the layout its function requires.

Describe each thing at its own level. Categories summarise their contents; collections explain what their entries share; individual items explain their purpose; Guides explain use and limitations. A collection does not give one entry prominence merely because it is currently the only entry. Descriptions add useful information beyond their titles rather than repeat standard site features.

Preserve explanations that contribute distinct, compatible meaning. Add new understanding alongside them. Replace or remove an explanation only when it is incorrect, superseded, or genuinely redundant without losing meaning.

Names are denotative where possible. A utility should use the shortest plain name that accurately identifies what it does; a distinctive proper name is retained when the object itself benefits from a durable identity or namespace. Stable technical slugs and domains do not need to change merely because a public display name becomes more literal.

Repeated element	Fixed contract
Header	Full-width translucent utility bar; 52px minimum inner row with vertical breathing room; Buy me a coffee left and vertically centered theme controls at the right content edge. Hide it in Settings.
Identity	The introduction names the project once. Page titles, catalogue cards and browser tabs use the same canonical project icon. Genuine vectors stay SVG; raster identity artwork uses WebP. The gray circle is only the unassigned fallback. The main site uses Andraž Đurič’s personal logo only in the browser tab, without adding it to headers, titles, cards, footers or decorative page content. Black-tile app marks share one outer geometry and are optically calibrated at title, card and tab sizes.
Parent navigation	Every page except the main homepage has a return row, starting with Main site and its trailing left arrow and adding named ancestors on deeper pages. It uses 32px minimum link targets, wraps long names and remains available when the header is hidden. The main homepage offers its centered About link.
Theme control	The header offers the author’s everyday choices, Light Gray (the full sun) and Dark (the moon), to keep it compact. The Light Gray button is visually active for either light theme, and Dark for either dark theme; clicking selects the labelled theme. Settings retains all four exact choices, including Light with a larger white sun centre and Pitch Black / OLED with the black dot. Light Gray is the first-visit default.
Text and spacing	The largest of five shared text sizes belongs only to bold page titles. Settings is centered; card and section text keep their smaller sizes. Consistent gutters, card padding and section spacing align the pages on phones and larger screens. At the end of content, a shared 32px clearance keeps the last element clear of the footer.
Primary introduction	The main homepage has a bold Writing, software and creative work heading with a smaller, regular-weight By Andraž Đurič line underneath. About sits close beneath it. The gap above the title matches the gap from About to Work. Two ordinary purpose paragraphs sit between the title/byline and About, using the shared description width and spacing. Project introductions center their icon and title, description and software standing. Additional purpose text follows the same centered reading width.
Cards and actions	22px family cards with solid surfaces, quiet neutral borders and paired soft shadows; 46px primary actions with 10px corners. Primary actions become paler while pressed. Persistent choices retain a tinted fill and outlined edge; keyboard focus remains separately visible.
Release card	Downloadable software shares one ordered, optional-slot release grammar: metadata, primary artifact, setup/caveat, alternates, source, licence, checksums, contextual documentation.
Benefits and terminal notes	Compact benefit/trust facts use a 17px semantic icon with title and explanation. Terminal qualifications are centered, muted and narrow, without decorative icons.
Links	Content links use a cohesive marker family: right arrow for internal family navigation, up-right for external destinations, download symbol for artifacts. Shared navigation has two marker exceptions: the trailing left arrow on Main site and the external marker on Buy me a coffee. Text links retain thin underlines.
Footer	A full-width divider and an inner row matching the header height. Contact and Guide • Settings stay markerless; Contact stays left and Guide • Settings right. Plain-text actions keep their text-width underlines.
Guide index	The same restrained contents column on every family Guide, collapsing above the document on smaller screens. Long desktop contents lists scroll above the footer, including when moving through links with the keyboard.
Guide body	Left-aligned system text. The header has 24px below its introduction and a divider; section content starts 32px below the divider. Nested subsections use the 20px prose heading gap without another section inset. Tables scroll within their own labelled region. Every local section has one contents link.
Neutral themes	White Light, neutral Light Gray, Dark and Pitch Black / OLED page backgrounds. Product colors remain accents; page-wide glow is removed.

Alignment and text enlargement

One page wrapper owns the top inset: 48px, or 32px up to 820px wide. Page descriptions start 16px below the title and use a centered box no wider than 620px. Card titles are 20px. Terminal notes use the same centered width, with 24px above them. The main homepage keeps its balanced introduction.

Titles, parent links and Settings rows wrap when text grows. A project mark may move above its name; names remain readable. Skip to content is the first keyboard link. Missing pages provide direct recovery links in ordinary document flow.

Wording

Interface copy names the section or action, states the necessary fact, and stops. It avoids promotional filler, nearby repetition, and changing project counts or versions in overview prose when structured records already carry that information. Download labels state their contents and file format. An action that only scrolls to content immediately below it is omitted.

LightWhite

Light GrayLight gray

DarkSurface

Pitch Black / OLEDZero light

4. Document grammar

Epistemic Forge established a useful long-form intellectual grammar. This site preserves the grammar while replacing hard-coded, light-only styling with reusable, theme-aware components. This is distinct from the simpler sans-serif grammar used by project and platform Guides.

Element	Purpose
Title and subtitle	Name the claim and its exact scope.
Document type	Distinguish an audit, argument, synthesis, guide, release, or creative work.
Author, collaborators, version	Make responsibility, provenance, and revision state visible.
Abstract	State the complete argument compactly before detail.
Epistemic key	Prevent textual fact, empirical finding, inference, legal status, and judgment from laundering one another.
Indexed sections	Keep long arguments navigable and referable.
Confidence ledger	Attach confidence and limitations to specific claims.
Assumptions and kill conditions	Expose what bears the conclusion and what would defeat it.
References and lineage	Preserve external evidence and the work’s place inside the corpus.
Licence and AI disclosure	State reuse rights, collaboration, and retained responsibility.

Not every document needs every element. The structure is selected by epistemic need, not filled mechanically. A short practical release should remain short.

5. Architecture

The Epistemic Forge site indexes the writings and keeps the original blog directly linked. Visitors can search the list or open the full essays on the blog. Explicit numbered revisions of one writing are grouped together.

The creations catalogue groups packs and individual assets, with previews, creator notes, compatibility information and downloads. Ordinary pages omit version histories. Download identities and licence notices remain preserved behind the simpler presentation; a 3D preview is separate from the original files and loads only when requested. Updatescollects dated work-in-progress posts, images and videos. Planet Minecraft remains an additional distribution channel, linked throughout the catalogue. Draft records and draft-only uploads are excluded from the public build.

Epistemic Forge — Music links to the Suno channel and lists supplied song titles and descriptions. Epistemic Forge — Video links to the mixed-content YouTube channel. These channel pages do not imply that every song or video has been indexed here; channel links alone add no creation count.

The site is a platform rather than a sequence of rebuilt pages. Project records, navigation, status, licences, and accents live as structured data. Pages render those records through shared components. Adding a project should normally mean adding one manifest entry and its content—not rebuilding the site shell.

Layer	Responsibility
Design tokens	Theme colours, typography, spacing, corners, borders, motion, and semantic states.
Shared components	Header, theme switch, project cards, collection pages, article structure, tables, callouts, status and licence blocks.
Project manifests	Name, domain, description, status, licence, accent, link destination, version, and visibility.
Content	Writing, creative, tool, status, and Guide material kept separate from layout code.
Contracts	Build, accessibility, link, schema, and theme checks that prevent quiet drift.
Decision record	Dated reasons for changes that future people and AI systems must not accidentally reverse.

Maintenance firewall

Future AI work must extend the existing primitives, read the governing documents, preserve unrelated decisions, update the change record, and validate the result. Replacing the architecture with a fresh generated template is a defect.

6. Licensing

“Free” is not left as an implication. Each work states its licence or makes clear that no public licence has been granted. Different objects require different licences, and one project’s licence does not silently transfer to another.

Work	Default	Boundary
Essays and public prose	CC BY 4.0	Reuse and adaptation with attribution.
Site code and small tools	MIT	Use, copy, modify, and distribute with the notice retained.
Original Minecraft creative works	CC BY 4.0	The licence covers the author’s original contribution; Minecraft, Mojang, and other third-party material retain their own rights.
Music and video	No reuse licence granted here	Channel links do not extend this site’s prose or Minecraft licences to songs or videos.
Exocortex	No public licence yet	AGPLv3 for code and CC BY-SA 4.0 for documentation remain proposals. The test APK is available to download; its availability does not grant permission to redistribute its source or create a public fork.
AI Education Assistance	No new reuse licence assigned	The original prompt, documentation, templates and optional checker do not inherit this website’s licences. Publication does not assign new reuse terms.
Andraž Đurič’s personal logo	Separate logo use policy	Free use to refer to the author or his work, with attribution. No implied endorsement or use as another person’s identity.
Other names and logos	Separate brand policy	Code and content licences do not automatically grant identity or endorsement rights.

Personal logo

The personal logo identifies Andraž Đurič. On this website it appears only as the browser-tab favicon. The logo file is available for references to the author or his work under the Logo use policy, including criticism and commercial publications. No payment or advance permission is required for uses covered by that policy.

Identify the logo as belonging to Andraž Đurič, with a link to andrazdjuric.com where the medium permits. An accompanying name, caption or credits entry can provide attribution; it need not be printed inside the logo. Resizing and format conversion are allowed while preserving the design. The permission does not cover presenting the logo as someone else’s identity or implying endorsement. Uses independently permitted by law remain unaffected.

Earlier downloads retain any broader permissions already granted. New licence notices cover the author’s contribution and preserve required third-party notices.

No paywall, premium tier, or donation may unlock rights or functionality withheld from other users. Optional support, where present, is a gift rather than a transaction for access.

7. Prompts

Prompts is a collection designed to work across AI models and adapt to the user’s needs and available tools. This is a design goal, not a guarantee of compatibility with every model. Niche prompts can remain adaptable within their purpose.

Standalone prompts are counted separately from writings. Continuation instructions, supporting files, guides and versions do not add to the prompt count.

Use a prompt with your chosen AI and follow the item’s instructions. Its own page and Guide explain its purpose, requirements and optional capabilities. Publishing a prompt does not provide a hosted service or grant your AI additional tools or permissions.

8. AI collaboration

People may use this site directly or work with an AI of their choice. The AI guide carries the work catalogue, operating instructions and data boundaries into that conversation. It is generated from the same public documentation used by visitors. A compact memory note is offered only with explicit permission and where the chosen AI supports it.

Tools should be understandable to both people and software. Their inputs, outputs, supported environments and limits should make compatible workflows discoverable. The machine-readable catalogue currently describes interactive tools and guided workflows; it does not grant access to a device or provide callable processing endpoints. Future adapters should reuse the existing engines, preserve local processing where supported, and distinguish proposed capabilities from verified operations.

The user’s goal and control remain central: an AI should recommend a tool when it fits, identify any manual handoff, and verify the resulting artifact before claiming success. A documentation snapshot cannot update itself or guarantee another AI’s behaviour. Tool changes must update the corresponding public Guide and capability record in the same release.

The connection across these works is a concern for context and correction: a claim needs its scope and evidence; an archive distinguishes original material from interpretation; a project states its status and rights. This is a shared design rationale, not evidence that one theory explains every domain. Visuals should help transmit the work: a Minecraft preview shows a creation, while a sourced argument map can expose dependencies or a change of mind. Each form earns its place by helping the reader.

Exocortex is the external-memory part of this work. Its current Android app keeps a personal archive offline, records where information came from, and exports selected context in question packs for an AI used outside the app. Returned proposals remain distinguishable from the owner’s decisions. The longer-term aim is user-owned cognitive infrastructure: the record and control over its use should survive a change of intelligence. The archive remains evidence about a life; it is not the person.

AI systems may assist with research, adversarial review, drafting, design, programming, migration, and testing. Their output is not accepted merely because it is fluent. Claims and implementations remain subject to evidence, comparison, and verification.

Relevant collaboration is disclosed. Contributions are judged by their content rather than their origin; authorship and final responsibility remain with the releasing human. The repository includes instructions designed to let future AI systems continue the project without reconstructing its architecture from conversation fragments.

9. Privacy and hosting

This website requires no account and contains no advertising, behavioural analytics, tracking pixel, or engagement machinery. First-party preference cookies share the chosen theme and header visibility across `andrazdjuric.com` and its project subdomains. Local storage supplies immediate display and fallback behavior. The value is not an account or visitor identifier. External project links are labeled by context.

Hosting is replaceable. The source and content remain portable, and the custom domain remains an address rather than the architecture. Individual tools may make stronger privacy claims only when those claims are structurally true—for example, Image Converter’s in-browser conversion, PDF — Merge or Split’s local document processing, and Exocortex’s absence of Android internet permission.

10. Accessibility

Semantic landmarks, heading order, labels, and keyboard operation are required.
Body text begins at a readable size and remains usable at 200% enlargement.
Colour never carries meaning alone; contrast is checked in all four themes.
Long tables scroll within their own boundary instead of breaking the page.
Motion respects reduced-motion settings, and touch targets remain usable on small screens.
Long-form text is justified only where the measure supports it; mobile reading remains left-aligned.

11. Standing and correction

Software standing is separate from versioning. Test means the intended scope is still being validated; Complete means the intended scope is delivered. Maintained means changes and compatibility work can continue; unmaintained means that work has stopped.

Active maintained projects stay below major version 1. Small projects use 0.x.x; large projects may use a wider 0.xx.x progression. The final segment marks smaller changes and the middle segment normally marks larger ones. Major version 1 is reserved for a project the owner considers finished and no longer changing. Immutable historical release filenames may retain an older published label while the current public standing uses the corrected version.

The Site guide version tracks maintained platform-guide releases. The shared interface contract has its own version. The AI guide has its own maintained guide version plus a generated content-revision hash identifying an exact snapshot.

Use Contact and feedback to report a problem, suggest an improvement, or send a question. Include the project or page and enough detail to understand the issue.

Corrections should update the public surface, structured record and governing repository rule together. Implementation chronology belongs in dated decisions and technical continuation records rather than this overview.

Website settings

Main site and the named parents above the page follow the site’s hierarchy. Guide and Settings use local pages where available.

Settings lets you hide the header and choose Light, Light Gray, Dark or Pitch Black / OLED. Light Gray is the first-visit default. The parent row and footer remain available when the header is hidden.

Choose System, DM Sans, Outfit, or Outfit headings with DM Sans body text in Settings. The preview and interface change immediately. Outfit is the first-visit default; fonts are served by these websites. Your saved selection is preserved.

Theme, header and font preferences are shared across andrazdjuric.com websites in this browser. They contain no document data or visitor identifier and are separate from installed application settings.

Contact in the footer opens the main site’s contact options in a new tab. Use it for questions, problem reports or suggestions.