Scope of Work - Configuration, Templating & Pages

This section describes how Urban List will be configured using Craft CMS.

The RFP describes configuration through WordPress, Elementor and Voxel. Our approach achieves the same outcomes through Craft CMS's native content modelling and templating. Sections 9.2–9.6 are WordPress/Voxel specific; our equivalent approach is described below. Core platform capabilities from Section 9.1 are addressed in the Scope of Work Overview.

Platform configuration

The platform is built on a structured content model where core entities (articles, venues, events, competitions, products, locations) exist as independent entries that can appear consistently across editorial content, directories, search results and location hubs.

Configuration focuses on:

• Content model and entity relationships
• Editorial block system for composing articles
• Taxonomies and attributes for filtering and discovery
• Roles, permissions and moderation workflows
• Integrations with search, advertising and analytics

Templating approach

Templates use a component-driven system aligned with the design system. Rather than rigid page templates, we use reusable components (editorial cards, directory listings, discovery modules, layout primitives) that render entities consistently.

The same entity can appear in multiple contexts: within articles, search results, curated lists or location pages, without separate templates for each. Improvements to performance, accessibility or layout propagate automatically.

Template and component quantities

The RFP specifies detailed template quantities (headers, footers, loop items, archive variants). These quantities will be formalised during discovery based on actual usage requirements and editorial workflows.

Our component-driven approach ensures all necessary template variations are supported. Rather than building fixed template counts upfront, we define reusable components that can be assembled into the required variations. This approach is more efficient and ensures consistency across the platform while accommodating the specific needs identified during discovery.

Editorial publishing

Editorial content uses structured blocks aligned with the design system. Editors assemble articles using rich media, embedded listings, related content modules and commercial placements while maintaining consistent structure.

This supports everything from quick updates to long-form guides and art-directed features.

Directories and discovery

Listings, events and products exist as structured entries that can be browsed, searched and embedded into editorial content. Search and filtering is powered by Meilisearch for fast faceted filtering, location-aware discovery and promoted listings.

Commercial integration

Sponsored placements, affiliate links and promoted listings are implemented through structured relationships and template rules. Campaign and partner relationships drive advertising categories, content placements and analytics tagging.

Newism has implemented Urban List's existing Google Ad Manager integration and will ensure continuity through the transition.

Standard pages

Pages such as Home, About, Careers, Contact and Editorial Policy are managed as CMS entries using the same block-based content system as editorial content.

Content migration

The working demo includes a comprehensive migration of Urban List's existing content into Craft CMS: articles, listings, events, locations and their relationships. This exceeds the representative migration requested in the RFP and demonstrates the approach works in practice.

Because Newism has deep familiarity with the existing database, we have transformed content into the new structured model and validated the resulting data structure.

The migration also presents an opportunity to review what should be carried forward. We can cross-reference Google Analytics page view data to identify high-performing content and flag outdated or low-value pages: venues that have closed, content with little engagement, or pages that can be consolidated. Legacy URLs will be redirected to preserve search visibility.