Michael J Wright Archive – Project Overview
For curators, producers, and partners who want the big picture without the server jargon.
Why this archive exists
Michael J Wright’s creative work spans photography, writing, exhibitions, and collaborative research. This archive preserves every piece, makes it discoverable, and feeds trusted content into the public website at michaeljwright.com.au. Think of it as the studio vault and distribution hub rolled into one:
- Create once, publish everywhere – new works are catalogued here, then pushed to the public site, partner collections, and special releases.
- Preserve the originals – the master files live safely in Fedora, with version history and metadata that travels with each item.
- Collaborate with confidence – curators, writers, developers, and partner institutions all reference the same authoritative source.
How the pieces fit together
| Layer | What you should know | Who touches it |
|---|---|---|
| Fedora Repository | Stores master files, metadata, and every revision. This is the “single source of truth.” | Curators, ingestion tools |
| Cloudflare Worker | Provides a friendly front door, adding security and access control. | Developers, integrations |
| Cloudflare Pages | Hosts this documentation and other supporting interfaces. | Producers, stakeholders |
| Prometheus & Grafana | Monitoring and dashboards that show system health. | Operations |
Public Website (michaeljwright.com.au) |
The storytelling surface that draws content from the archive. | Public audience, marketing |
Who does what
- Curators catalog works, assign metadata, and approve public releases.
- Digital producers plan publishing milestones, coordinate partner feeds, and sign off on go-lives.
- Developers/integrators maintain the automation, Worker/API endpoints, and ingestion tooling.
- Partner institutions receive scheduled exports or tailored API feeds.
- Public visitors experience the curated stories on the main website, which is powered by this archive.
Everyday workflows
- Curate a new work
- Prepare assets, descriptions, and rights information.
- Use the ingestion tooling (or work with a developer) to post it into Fedora through the secured Worker.
- Update the roadmap checklist once the item is live.
- Publish to the public site
- Producers decide which items appear on michaeljwright.com.au.
- Developers sync approved items into the frontend project (separate repository).
- Marketing reviews and schedules public announcements.
- Update partners
- Export batches for collaborators in the required format (JSON, CSV, METS).
- Share access links or schedule automations using the provided runbooks.
Where to go next
- Need technical instructions? Browse the runbooks at
/docs/(Production checklist, upgrade guides, ENT365 install, and more). - Looking for roadmap updates? Visit
/docs/development-roadmap.htmlto see what’s in flight. - Want to see the system status? Check Grafana dashboards or ask the tech team for the latest metrics.
- Ready to release content? Coordinate with the producer and developer teams to push updates into the public site repository.
Keep this overview open during planning meetings or onboarding sessions—it stays updated alongside the rest of the documentation hub.