ICT:Drupal Blueprint start if implementation data model
Costasano Heritage Project — Drupal 11 Architecture & Workflow Blueprint (v5.1)
Purpose of this Document
This page defines the architectural, conceptual, and workflow foundations of the Costasano Heritage Project.
It serves as:
- a stable reference for human contributors
- a briefing document for AI-assisted work sessions
- a safeguard against context loss over long-term development
All future design, implementation, and automation decisions must be compatible with the principles defined here.
Project Overview
The Costasano Heritage Project is a long-term digital heritage initiative operated by members of the Costa Sano Club (70+ years old, amateur historians, non-ICT specialists).
The project manages:
- hundreds of gigabytes of documents, images, and maps
- collaborative historical research
- multi-channel dissemination (wiki, public website, exhibitions, video)
The system is designed for decades-long durability, not short-term publication.
Core Philosophy
Authoritative Source Principle
There is exactly ONE authoritative system for data and assets:
- Drupal 11
All other outputs (MediaWiki, public website, video, exhibitions) are derivatives.
No downstream system is allowed to correct, invent, or override facts. All corrections must return to Drupal.
Asset-Centric Design
The central object of the entire system is:
DigitalAsset + File (ONE asset = ONE file)
Everything else (timeline chapters, places, organisations, narratives) exists to:
- contextualize assets
- classify assets
- generate stable identifiers
- reuse assets across outputs
Ingest First, Enrich Later
The system must allow:
- rapid bulk ingestion of files with minimal metadata
- gradual collaborative enrichment over time
- clear lifecycle states without pressure for completeness
Completeness is a process, not a prerequisite.
Target Users & UX Constraints
User Profile
- Age: 70+
- Background: amateur historians
- ICT skills: minimal
- Tolerance for complexity: low
UX Non-Negotiables
- No technical terminology exposed (no “entity”, “taxonomy”, “foreign key”)
- No cluttered forms
- Dashboard-first navigation
- Large click targets
- Predictable layouts
- Dark mode mandatory (accessibility)
Users must never feel they are “using Drupal”.
System Architecture
Infrastructure
- Reverse Proxy: Windows Server (IIS + ARR, SSL offloading)
- Web Server: AlmaLinux 10.1 (Apache 2.4, PHP 8.3, PHP-FPM)
- Database Server: AlmaLinux 10.1 (MariaDB 10.11+)
- SELinux: Enforcing
- PHP-FPM: Per-site pools
- Filesystem: Hardened
Operational Constants
- Site URL: https://research.costasano.club
- Drupal project root: /var/www/drupal
- Drupal web root: /var/www/drupal/web
Output Channels
1. MediaWiki (Research & Writing)
Role:
- illustrated research pages
- collaborative narrative writing
- preparation for Wikipedia publication
MediaWiki does NOT:
- store authoritative metadata
- manage files
- generate identifiers
2. Public Drupal Website
Role:
- curated presentation of selected research
- timelines, maps, galleries
Only “complete” or approved assets are shown publicly.
3. Offline Outputs
- video documentaries
- lectures
- exhibitions
These reuse:
- the same assets
- the same identifiers
- the same metadata
Authority Entity Implementation Strategy (v5.0)
Authority entities are implemented progressively, from simplest to most complex. This order is mandatory.
Step 1: TimelineChapter (Temporal Authority)
Type:
- Drupal Custom Content Entity (authority)
Meaning:
- historical periods / timeline segmentation
- not editorial or narrative content
Characteristics:
- recursive (parent/child)
- stable Code (max 6 characters)
- used as first component in asset identifiers
- no sequence field
Dashboard pattern:
- table of existing records
- add new record
- click row to edit
Step 2: Place (Spatial Authority)
Type:
- Drupal Custom Content Entity (authority)
Characteristics:
- recursive (parent places)
- stable Code (max 6 characters)
- Address field for geocoding
- coordinates auto-derived when possible
- coordinates never required for ingestion
Purpose:
- spatial context
- reused across assets and organisations
Step 3: Organisation (Institutional Authority)
Type:
- Drupal Custom Content Entity (authority)
Characteristics:
- stable Code (max 6 characters)
- linked to a Place
- reused across assets
Purpose:
- institutional context
- archival provenance
Step 4: DigitalAsset (CORE ENTITY)
Type:
- Drupal Custom Content Entity
Rules:
- ONE asset = ONE file
- file is immutable once uploaded
- identifier is immutable once generated
- physical filenames are managed by Drupal
- original filename is preserved for user reference
Identifier format:
- TimelineChapter.Code
- Place.Code OR Organisation.Code
- Scoped 4-digit counter (asset sequence only)
Example:
CH03-ROM-0007
DigitalAsset creation is impossible before TimelineChapters, Places, and Organisations exist.
Step 5: HeritageObject & Advanced Relationships (Deferred)
Type:
- Custom Content Entities
- Role-based relationships
This step is explicitly deferred until asset logic is proven.
Asset Lifecycle & Collaboration Workflow
Roles (conceptual)
- Ingestor
- uploads files
- assigns minimal context
- Enricher
- adds metadata
- validates data
One person may have multiple roles.
Lifecycle States
- Newly added
- In progress
- Reviewed
- Complete
States describe maturity, not publication.
Dashboard Design Pattern
For TimelineChapters, Places, Organisations:
- single dashboard page
- table of existing records
- add/edit via simple forms
For Assets:
- add asset always visible
- recent assets list
- guided asset discovery
- no massive tables
Help & Guidance Strategy
Help must be:
- contextual
- non-intrusive
- always available
Mechanisms:
- field descriptions
- ℹ️ icons
- collapsible help sections
No separate manuals.
Automation & Logic
Automation is handled via:
- Drupal configuration
- ECA workflows
- Custom event subscribers if required
Automation is used to:
- generate identifiers
- manage asset counters
- enforce immutability rules
- reduce cognitive load
Automation must never obscure what happens.
Design Discipline Rules
- No authority entity is implemented as editorial content
- No field is required unless it enables a mechanism
- No output system becomes authoritative
- No UX decision is optimized for power users
- Stability is more important than elegance
Usage in AI Sessions
This document must be:
- pasted or referenced at the start of new AI-assisted sessions
- treated as authoritative context
- updated only when architectural decisions change
AI output must conform to this blueprint.
Supplement — UI Theming, Accessibility & Visual Discipline
This supplement records explicit requirements related to visual theming, accessibility, and user comfort that were clarified after initial project restart. These requirements are binding and must be respected in all future design and implementation decisions.
Separation of UI Concerns
The system UI is explicitly divided into two independent domains:
- Administrative / Dashboard UI (authenticated users)
- Public Presentation UI (anonymous visitors)
No design, theme, or UX decision in one domain is allowed to negatively affect the other.
Administrative & Dashboard UI (Authenticated Users)
Target Users
- System administrator (username: mngr)
- Club members and contributors (e.g. testuser)
- Age profile: 70+
- Long working sessions expected
Mandatory Requirements
- Permanent dark mode must be available and usable
- Dark mode must be:
- supported natively by Drupal
- configurable per user
- persistent across sessions
- No reliance on browser-level dark mode
- No custom CSS or hacks
Scope
- Applies to:
- content ingestion
- asset enrichment
- review workflows
- dashboards
- Applies equally to administrators and non-technical contributors
Design Discipline
- Accessibility and eye comfort take precedence over aesthetics
- The administrative UI must remain:
- predictable
- low-contrast-stress
- uncluttered
- No experimental or unstable admin themes are permitted
Public Presentation UI (Anonymous Users)
Audience
- General public
- Researchers
- Visitors with unknown accessibility needs
Mandatory Requirements
- Public-facing theme must be:
- modern
- responsive / adaptive
- suitable for long-term institutional use
- Both light mode and dark mode must be supported
- Visitors must be able to:
- choose their preferred mode
- view the site correctly in either mode
Design Implications
- Page design must be validated in:
- light mode
- dark mode
- No layout, content, or contrast decision may assume a single color scheme
- Visual discipline is required from the beginning to avoid later rework
Explicit Non-Goals
- The public UI must not resemble:
- archival back-office tools
- database front-ends
- legacy academic platforms (e.g. Omeka-style rigidity)
- The solution must avoid visually conservative or static templates that limit narrative and exhibition-style presentation
Timing & Implementation Rules =
- Administrative dark mode is considered a foundational setup step
- Public-facing theming is explicitly deferred until:
- asset logic is validated
- authoritative entities are stable
- Early decisions must not constrain future design exploration, but must enforce:
- accessibility
- adaptability
- long-term maintainability
Stability Principle (UI) =
- UI comfort is a prerequisite for correct decision-making
- Visual strain increases error rates and architectural drift
- Therefore:
- administrative UI comfort is non-negotiable
- public UI adaptability is mandatory
End of Blueprint
appendix: Data Model
// =====================================================
// Costasano Heritage Database Model — v5.0
// (revised: sequence cleanup)
//
// Rules:
// - Code max length = 6 characters
// - Sequence exists ONLY for DigitalAssets
// - Identifier = Chapter.Code + Place/Org.Code + 4-digit Sequence
// =====================================================
// ============================
// TEMPORAL AUTHORITY
// ============================
Table TimelineChapters {
id string [pk]
Parent string [ref: > TimelineChapters.id]
Code string // max 6 chars, immutable
Label string
StartDate datetime
EndDate datetime
}
// ============================
// SPATIAL AUTHORITY
// ============================
Table Places {
id string [pk]
Parent string [ref: > Places.id]
Code string // max 6 chars
Label string
Address string // used for geocoding
Latitude float
Longitude float
}
// ============================
// INSTITUTIONAL AUTHORITY
// ============================
Table Organisations {
id string [pk]
Code string // max 6 chars
Label string
Place string [ref: > Places.id]
}
// ============================
// CORE ASSET ENTITY
// ============================
Table DigitalAssets {
id string [pk]
// ---- identification ----
TimelineChapter string [ref: > TimelineChapters.id]
Place string [ref: > Places.id]
Organisation string [ref: > Organisations.id]
Sequence int // 4-digit counter, scoped
Identifier string // e.g. CH03-ROM-0007, immutable
// ---- file handling ----
FileUri string // managed by Drupal
OriginalFileName string // auto-filled at upload
// ---- recursion ----
Parent string [ref: > DigitalAssets.id]
// ---- classification ----
AssetSourceType string
AssetType string
// ---- workflow flags ----
AiProcessed boolean
IsPublishable boolean
}
Lessons learned on feb 27 2026
This session ended in with Drupal in an undetermined stated due to a misunderstanding about the requirements, and then finally a problem wrongly using a Drupal reserved word DASHBOARD.
Restart from scratch after that day, restoring of the full virtual disks for both machines dated 26 feb.
Conclusion of the day were chatgpt promises for restarting.
Tomorrow I will:
- avoid cleverness
- avoid custom routing early
- avoid reserved names
- rely on Drupal defaults first
- reduce bash steps to the minimum stop earlier when entropy appears
Agreement: You bring architectural clarity. I bring Drupal-specific caution. That’s a workable division.
Important AI protocal
After the agreement an a workflow, we work step by step, no hurry. AI proposes a step, I execute and report back the result and then only we go for the next step. Too much explanation is NOT needed, as I am a novice in this field. After 50+ years in ICT, I understand mostly what the steps do and if not, I will ask for. This should permit for a slow but steady flow towards the endgoal of the session.
Modules Enabled in our Drupal 11 configuration =
mngr@localhost:/var/www/drupal$ drush pm:list --status=enabled
---------------- ------------------------------------- --------- ----------
Package Name Status Version
---------------- ------------------------------------- --------- ----------
Core Announcements (announcements_feed) Enabled 11.3.3
Core Automated Cron (automated_cron) Enabled 11.3.3
Core BigPipe (big_pipe) Enabled 11.3.3
Core Block (block) Enabled 11.3.3
Core Block Content (block_content) Enabled 11.3.3
Core Breakpoint (breakpoint) Enabled 11.3.3
Core CKEditor 5 (ckeditor5) Enabled 11.3.3
Core Comment (comment) Enabled 11.3.3
Core Configuration Manager (config) Enabled 11.3.3
Core Contact (contact) Enabled 11.3.3
Core Contextual Links (contextual) Enabled 11.3.3
Field types Datetime (datetime) Enabled 11.3.3
Field types Datetime Range (datetime_range) Enabled 11.3.3
Core Database Logging (dblog) Enabled 11.3.3
Core Internal Dynamic Page Cache Enabled 11.3.3
(dynamic_page_cache)
Core Text Editor (editor) Enabled 11.3.3
Core Field (field) Enabled 11.3.3
Core Field UI (field_ui) Enabled 11.3.3
Field types File (file) Enabled 11.3.3
Core Filter (filter) Enabled 11.3.3
Core Help (help) Enabled 11.3.3
Core History (history) Enabled 11.3.3
Field types Image (image) Enabled 11.3.3
Core Inline Form Errors Enabled 11.3.3
(inline_form_errors)
Core Layout Builder (layout_builder) Enabled 11.3.3
Core Layout Discovery (layout_discovery) Enabled 11.3.3
Field types Link (link) Enabled 11.3.3
Core Media (media) Enabled 11.3.3
Core Media Library (media_library) Enabled 11.3.3
Core Custom Menu Links Enabled 11.3.3
(menu_link_content)
Core Menu UI (menu_ui) Enabled 11.3.3
Core MySQL (mysql) Enabled 11.3.3
Core Node (node) Enabled 11.3.3
Field types Options (options) Enabled 11.3.3
Core Internal Page Cache (page_cache) Enabled 11.3.3
Core Path (path) Enabled 11.3.3
Core Path alias (path_alias) Enabled 11.3.3
Core Responsive Image (responsive_image) Enabled 11.3.3
Core Search (search) Enabled 11.3.3
Core Shortcut (shortcut) Enabled 11.3.3
Core System (system) Enabled 11.3.3
Core Taxonomy (taxonomy) Enabled 11.3.3
Field types Text (text) Enabled 11.3.3
Core Toolbar (toolbar) Enabled 11.3.3
Core Update Status (update) Enabled 11.3.3
Core User (user) Enabled 11.3.3
Core Views (views) Enabled 11.3.3
Core Views UI (views_ui) Enabled 11.3.3
Core Workspaces (workspaces) Enabled 11.3.3
Core Workspaces UI (workspaces_ui) Enabled 11.3.3
Field types Address (address) Enabled 2.0.4
Field types Color Field (color_field) Enabled 3.0.2
Other Contact Formatter Enabled 2.0.4
(contact_formatter)
Core Dashboard (dashboard) Enabled 2.2.0
Field types Entity Reference Revisions Enabled 8.x-1.14
(entity_reference_revisions)
Fields Field Group (field_group) Enabled 4.0.0
File metadata File metadata manager (file_mdm) Enabled 3.2.0
File metadata File metadata - EXIF Enabled 3.2.0
(file_mdm_exif)
File metadata File metadata - Font Enabled 3.2.0
(file_mdm_font)
Geocoding Geocoder (geocoder) Enabled 8.x-4.30
Geocoding Geocoder Address (geocoder_address) Enabled 8.x-4.30
Geocoding Geocoder Field (geocoder_field) Enabled 8.x-4.30
Geocoding Geocoder Geofield Enabled 8.x-4.30
(geocoder_geofield)
Geofield Geofield (geofield) Enabled 10.3.3
Other Gin Toolbar (gin_toolbar) Enabled 3.0.3
Media Image Effects (image_effects) Enabled 5.0.0
User interface Klaro Cookie & Consent Manager Enabled 3.0.8
(klaro)
Geofield Leaflet (leaflet) Enabled 10.4.4
Geofield Leaflet Markercluster Enabled 10.4.4
(leaflet_markercluster)
Geofield Leaflet Views (leaflet_views) Enabled 10.4.4
User interface Linkit (linkit) Enabled 7.0.13
Paragraphs Paragraphs Type Permissions Enabled 8.x-1.20
(paragraphs_type_permissions)
Paragraphs Paragraphs (paragraphs) Enabled 8.x-1.20
Paragraphs Paragraph Bundle 3D Carousel Enabled 1.0.15
(paragraph_bundle_3d_carousel)
Paragraphs Paragraph Bundle 3D Flip Box Enabled 1.0.15
(paragraph_bundle_3d_flip_box)
Paragraphs Paragraph Bundle Accordion Enabled 1.0.15
(paragraph_bundle_accordion)
Paragraphs Paragraph Bundle Alert Enabled 1.0.15
(paragraph_bundle_alert)
Paragraphs Paragraph Bundle Block Enabled 1.0.15
(paragraph_bundle_block)
Paragraphs Paragraph Bundle Block Content Enabled 1.0.15
(paragraph_bundle_block_content)
Paragraphs Paragraph Bundle Card Enabled 1.0.15
(paragraph_bundle_card)
Paragraphs Paragraph Bundle Carousel Enabled 1.0.15
(paragraph_bundle_carousel)
Paragraphs Paragraph Bundle Contact Form Enabled 1.0.15
(paragraph_bundle_contact_form)
Paragraphs Paragraph Bundle Content Enabled 1.0.15
(paragraph_bundle_content)
Paragraphs Paragraph Bundle Grid Enabled 1.0.15
(paragraph_bundle_grid)
Paragraphs Paragraph Bundle Hero Enabled 1.0.15
(paragraph_bundle_hero)
Paragraphs Paragraph Bundle Icon Enabled 1.0.15
(paragraph_bundle_icon)
Paragraphs Paragraph Bundle Image Enabled 1.0.15
(paragraph_bundle_image)
Paragraphs Paragraph Bundle Image Background Enabled 1.0.15
(paragraph_bundle_image_background)
Paragraphs Paragraph Bundle Image Grid (Image Enabled 1.0.15
Gallery - Lightbox)
(paragraph_bundle_image_grid)
Paragraphs Paragraph Bundle Image Overlay Enabled 1.0.15
(paragraph_bundle_image_overlay)
Paragraphs Paragraph Bundle Layout Enabled 1.0.15
(paragraph_bundle_layout)
Paragraphs Paragraph Bundle Modal Enabled 1.0.15
(paragraph_bundle_modal)
Paragraphs Paragraph Bundle Node Reference Enabled 1.0.15
(paragraph_bundle_node_reference)
Paragraphs Paragraph Bundle Parallax Enabled 1.0.15
(paragraph_bundle_parallax)
Paragraphs Paragraph Bundle Slideshow Enabled 1.0.15
(paragraph_bundle_slideshow)
Paragraphs Paragraph Bundle Tabs Enabled 1.0.15
(paragraph_bundle_tabs)
Paragraphs Paragraphs Bundles Enabled 1.0.15
(paragraphs_bundles)
Solo Suite Solo Utilities (solo_utilities) Enabled 1.0.6
Media SVG Image Responsive Enabled 3.2.2
(svg_image_responsive)
Media SVG image (svg_image) Enabled 3.2.2
Core Claro (claro) Enabled 11.3.3
Core Olivero (olivero) Enabled 11.3.3
Gin (gin) Enabled 5.0.12
Solo Solo (solo) Enabled 1.0.30