A first-party record of the archive work
A new Furry Con Archives redesign case study documents my ongoing website redesign and development contribution for Furry Con Archives. It sits alongside the software project hub without being represented as one of the five repository-backed software projects.
The page explains the design priorities behind the work, including archive discovery, descriptive links, durable routes and keeping source attribution close to the records it describes. It also links directly to Furry Con Archives and Consurf as separate external projects.
Relationship boundaries stay explicit
The case study is intentionally conservative about entity relationships. Furry Con
Archives, Consurf and Mello Zone remain distinct entities in the page copy and
structured data. The page does not use sameAs to equate them, and it does not
claim ownership, endorsement or shared governance where those relationships do
not exist.
Mello Zone appears because it is another project I am responsible for and helps explain my creator/developer portfolio. Its community standards, membership, events and editorial authority remain on mellozone.site. The case study also states that archive facts should be verified against Furry Con Archives and Consurf facts against Consurf.
Discovery and indexability
The new route is linked from the developer projects hub, included in the generated sitemap and LLM-readable discovery directory, and explicitly allowlisted by the Cloudflare Worker as an indexable canonical page.
The shared project document template now derives the Open Graph image MIME type from the actual image extension. That prevents a JPEG social card from being incorrectly described as WebP while preserving the existing behavior for WebP and PNG project images.
The release audit’s canonical inventory was extended separately from the five software records so the case study remains correctly classified while still being covered by sitemap, schema, internal-link and crawler checks.
Verification
The implementation passed the repository validation workflow in GitHub Actions run
34704428485. The Astro build, packaged feed checks, Worker regression tests,
rendered-release audit, robots source check and Wrangler configuration validation
all completed successfully.
These changes create a clear portfolio reference and make the real contributor relationship easier to cite. They do not promise backlinks, rankings, domain authority scores or search-engine indexing.