Jerusalem Story

Jerusalem Story isn't a standard publication. It runs multiple content types across layered themes, each interconnected through a contextual lexicon and cross-referenced bios and topics. The editorial team needed a CMS that could handle this complexity while remaining manageable for a large team of writers, editors, and content administrators working across different content streams simultaneously.

We designed a structured content architecture around the platform's distinct content types: topics grouped under themes, biographical entries, lexicon items, blog posts, quick facts, and an organizational directory. Each content type was built with the relationships and editorial controls the team needs to publish and maintain interconnected content at scale.

The platform features a multi-content-type CMS with structured theming, cross-referencing between topics, bios, and the lexicon, a blog engine for the Jerusalem Notebook, a quick facts module, and an organizational directory. The architecture supports a large editorial team with role-based content management and workflows designed for high-volume publishing.

Jerusalem Story now has a digital infrastructure that matches the ambition of its editorial mission. The team can publish and maintain deeply interconnected content across multiple streams, and the platform serves as a growing, searchable resource for researchers, journalists, and communities following the Palestinian Jerusalem story.