Selected technical work
Responsibilities, decisions and delivery
These records cover selected publishing and information architecture work within a broader career across health, property, media and universities.
Publishing infrastructure / A decision from practice
Scale the publishing system.
This account describes my architectural judgment in a publishing environment of roughly a hundred sites with ingestion across thousands of social accounts.
The publishing queue kept growing.
The work involved a network of roughly a hundred sites, with ingestion across thousands of social accounts, and a publishing operation that had to make incoming material usable across a large and connected digital surface.
The volume needed an operating model.
Adding people was a reasonable response.
More editors and producers could have handled more incoming material, especially when there was immediate work to publish and a familiar production process already gave each person a way to contribute without waiting for a wider architectural change.
There was work to get through.
The repetition sat inside real work.
Editors and producers still needed to exercise judgment over what reached an audience, while the operation also required the repeated handling of inputs, categories and distribution that allowed those editorial decisions to move through the publishing process.
The editorial judgment still mattered.
The scale changed the question.
Across roughly a hundred sites and thousands of source accounts, a repeated handling step could become a recurring demand on production; the useful question was which work required editorial judgment and which work could be expressed as a publishing rule.
That distinction shaped the architecture.
The publishing surface was distributed.
The volume came through a network of sources and destinations, so choosing another framework or CMS would still leave the operation needing a model for what arrived, how it was classified and where it belonged in publication.
The platform was one decision.
Treat publishing as infrastructure.
I modelled the inputs, taxonomy, distribution and publishing rules as an information-flow problem, making the repeated machinery part of the architecture instead of treating every increase in publishing volume as a request for another layer of manual production.
The decision was to put repeatable publishing work into the system itself.
Walk through the machinery.
These two sites provide a public starting point: their page structures, editorial organisation and shared machine-readable records can be inspected directly. Earlier publishing architectures, acquisition systems and workflows can be discussed privately where the commercial material should remain private.
Inspect the shared entity record → · Discuss an architecture walkthrough →
Property publishing across markets
Diakrit / Publishing and acquisition infrastructure
- Responsibility
- Work inside a property publishing environment serving realtors across seven countries, including a Bangkok-based role with Diakrit.
- The operating context
- Property records, listing content, agent pages and campaign material moved through central tooling and local publishing routines. Templates and marketing technology configurations varied between markets.
- The delivery constraint
- Local teams still had material to publish. Changes to the shared pipeline had to account for the work those teams were already carrying.
- The scale
- Seven national markets meant that a template or publishing rule could affect several production teams. The scale describes the environment; it is not a measure of individual output.
- Contribution
- Established and improved production pipelines, template rules, marketing technology connections and page-level optimisation within the publishing process.
- Result
- Production moved toward repeatable publishing across markets, with page-level requirements carried by the pipeline. No quantified commercial uplift is claimed here.
University information architecture
CQUniversity / Digital direction, migration and governance
- Responsibility
- Digital Director work within CQUniversity’s large digital estate, including information architecture, migration and publishing governance.
- The operating context
- The estate had accumulated content across seven CMS platforms and distributed organisational owners. Those owners had different publishing requirements and histories.
- The delivery constraint
- Faculties and campuses needed to keep publishing while overlapping content, terminology and ownership were reconciled. A common architecture had to accommodate those responsibilities.
- The scale
- The recorded environment comprised approximately one million pages and nodes across roughly 22 organisational units. These figures describe the estate rather than a count of pages personally migrated.
- Contribution
- Worked on the migration away from seven CMS platforms, structural reconciliation between organisational units, publishing governance and the discovery consequences of architectural changes.
- Result
- The work supported movement toward a coherent information architecture and governed publishing decisions. The record describes a contribution within the wider programme.
Vocational education publishing
Australian RTO information / Architecture and implementation
- Responsibility
- Built a student-facing information system connecting courses, providers and guidance in the Australian vocational education sector.
- The operating context
- Source information was distributed across registers, PDFs and provider pages. A student’s question could require material from more than one of those sources.
- The delivery constraint
- The publishing model needed to retain the relationships between courses and providers while presenting information people could use to compare their options.
- The scale
- The React/Next.js system grew beyond 1,500 pages. At that volume, shared entity and template decisions affected repeated outputs across the site.
- Contribution
- Built the information architecture, course and provider entity model, relationships and publishing system, with search considered in the underlying structure.
- Result
- The system published connected course and provider information through a shared model. No quantified acquisition or student-outcome claim is attached to this record.
Search within the publishing system.
Across these environments, search work involved terminology, entities, information architecture, templates and implementation. It is a discipline running through the selected work.