Costa Sano KB - Recent changes [en]

Project:Model-Packs/Foundation Pack/Final architecture

Mngr — Wed, 22 Jul 2026 13:00:32 GMT

Project:Model-Packs/Foundation Pack/Final architecture

Mngr — Wed, 22 Jul 2026 12:19:55 GMT

Created page with "= Costa Sano Architectural Synthesis: The Virtual Exhibition Paradigm = This document serves as the master conceptual blueprint for redrafting the Costa Sano Foundation Document. It codifies the final, production-tested architecture that bridges a highly sophisticated, multi-column skeleton skin with an intuitive, no-code curation workflow for historians. __TOC__ == 1. The Core Vision: The Virtual Exhibition == The website is no longer modeled as a collection of stand..."

Project:Model-Packs/THE skin/section 4 test - final

Mngr — Wed, 22 Jul 2026 11:35:15 GMT

Project:Model-Packs/THE skin/section 4 test - final

Mngr — Wed, 22 Jul 2026 11:32:45 GMT

Created page with "= Technical Architecture Guide: Flat Unified Exhibition & Skeleton Skin Layout = This document outlines the definitive, low-maintenance architecture for the Costa Sano Archive Storytelling Engine. By utilizing a completely flat paragraph list model combined with a unified taxonomy coordinate prefix (<code>CS-</code>), historians can visually position any standard story card or external archive profile onto a 14-section skeleton skin wall from a single editing canvas. T..."

Project:Model-Packs/THE skin/section 4 test - v2

Mngr — Wed, 22 Jul 2026 09:16:21 GMT

Project:Model-Packs/THE skin/section 4 test - v2

Mngr — Wed, 22 Jul 2026 09:05:27 GMT

Created page with "= Technical Architecture Guide: Flat Unified Exhibition & Skeleton Skin Layout = This document outlines the definitive, low-maintenance architecture for the Archive Storytelling Engine. By placing the pane selection field directly on every paragraph type, historians can visually position any standard story card or external archive link onto the 14-section skeleton skin wall from a single, flat field list. This approach requires zero nested paragraph rows, zero custom q..."

Project:Model-Packs/THE skin/section 4 test

Mngr — Wed, 22 Jul 2026 08:32:16 GMT

Project:Model-Packs/Passing ID to entity browser view

Mngr — Tue, 21 Jul 2026 18:43:35 GMT

Mngr moved page Project:Model-Packs/Passing ID to entity browser view to Project:Bin/Passing ID to entity browser view without leaving a redirect

Project:Model-Packs/THE skin/twig & css

Mngr — Tue, 21 Jul 2026 18:41:17 GMT

Mngr moved page Project:Model-Packs/THE skin/twig & css to Project:Bin/twig & css without leaving a redirect

Project:Bin

Mngr — Tue, 21 Jul 2026 18:39:54 GMT

Created page with "= Bin - Poubelle - Vuilbak ="

Project:/Bin/Auto Page - DNN skin

Mngr — Tue, 21 Jul 2026 18:38:39 GMT

Mngr moved page Project:/Bin/Auto Page - DNN skin to Project:Bin/Auto Page - DNN skin without leaving a redirect

Project:Model-Packs/Bin/Auto Page - DNN skin

Mngr — Tue, 21 Jul 2026 18:37:56 GMT

Mngr moved page Project:Model-Packs/Bin/Auto Page - DNN skin to Project:/Bin/Auto Page - DNN skin without leaving a redirect

Project:Model-Packs/PubModel/Auto Page - DNN skin

Mngr — Tue, 21 Jul 2026 18:28:36 GMT

Mngr moved page Project:Model-Packs/PubModel/Auto Page - DNN skin to Project:Model-Packs/Bin/Auto Page - DNN skin without leaving a redirect

Project:Model-Packs/Foundation Pack/Museum

Mngr — Tue, 21 Jul 2026 14:40:05 GMT

Project:Model-Packs/Foundation Pack/Museum

Mngr — Tue, 21 Jul 2026 14:37:30 GMT

Created page with "The project started with a '''historical objective''':<blockquote>"We want to organize an exhibition."</blockquote>Then you realized the problem wasn't the exhibition—it was the lack of a structured archive behind it. So you changed the order: # Build the archive. # Structure the knowledge. # Then create the exhibition. What is fascinating is that the publication framework you're designing has brought you back to the original goal, but in a much richer form. It isn..."

Project:Model-Packs/Foundation Pack/Virtual exibition

Mngr — Tue, 21 Jul 2026 14:34:34 GMT

Mngr moved page Project:Model-Packs/Foundation Pack/Virtual exibition to Project:Model-Packs/Foundation Pack/Virtual exhibition without leaving a redirect

Project:Model-Packs/Foundation Pack/Virtual exibition

Mngr — Tue, 21 Jul 2026 14:05:06 GMT

Created page with "The Architectural Translation You can now explicitly define your Drupal components using museum terms in your documentation: * '''The Museum Building:''' The Drupal website itself. * '''The Exhibition Wing / Gallery Room:''' A <code>Subchapter Story</code> page. * '''The Modular Partition Walls:''' Your <code>Universal Layout Rows</code> (the 14 skeleton sections). * '''The Wall Hooks / Display Cases:''' The layout coordinates (<code>Grid4APane</code>, <code>Grid4BPane..."

Project:Model-Packs/THE skin/section 4 test

Mngr — Tue, 21 Jul 2026 13:53:46 GMT

Project:Model-Packs/THE skin/section 4 test

Mngr — Tue, 21 Jul 2026 09:31:11 GMT

Created page with "= Technical Implementation Guide: Section 4 Layout Test = This document provides a step-by-step guide to testing and implementing your modular, sparse layout pattern using Drupal and Bootstrap. This test focuses exclusively on '''Section 4''' to ensure the core logic operates correctly before building out the remaining sections. __TOC__ == Step 1: Create the Pane Selection Field in Drupal == You need a way to tell Drupal which layout pane a card belongs to. # Naviga..."

Project:Model-Packs/THE skin

Mngr — Mon, 20 Jul 2026 17:56:25 GMT

Project:Model-Packs/THE skin/twwxig & css

Mngr — Mon, 20 Jul 2026 15:58:44 GMT

Mngr moved page Project:Model-Packs/THE skin/twwxig & css to Project:Model-Packs/THE skin/twig & css without leaving a redirect

Roject:Model-Packs/THE skin/split twig & css

Mngr — Mon, 20 Jul 2026 15:57:43 GMT

Mngr moved page Roject:Model-Packs/THE skin/split twig & css to Project:Model-Packs/THE skin/split twig & css without leaving a redirect

← Older revision		Revision as of 15:57, 20 July 2026
(4 intermediate revisions by the same user not shown)
Line 18:		Line 18:

	To make your skeleton drawing areas recognizable to the Drupal user interface, you must register them as theme regions. Open your theme's <code>.info.yml</code> file and list each pane area under the <code>regions:</code> key:		To make your skeleton drawing areas recognizable to the Drupal user interface, you must register them as theme regions. Open your theme's <code>.info.yml</code> file and list each pane area under the <code>regions:</code> key:

			<pre>
			name: 'Costa Sano Universal Theme'
			type: theme
			core_version_requirement: ^10 \|\| ^11

			regions:
			header: 'Top Header'
			primary_menu: 'Main Navigation'
			content: 'Main Text Content'

			# Costa Sano Skeleton Skin Page Panes
			full_pane: 'CS: Full Pane'
			content_pane: 'CS: Content Pane'
			full_section_pane: 'CS: Full Section Pane'
			grid_6a: 'CS: Grid 6A Pane'
			grid_6b: 'CS: Grid 6B Pane'
			left_pane: 'CS: Left Pane Column'
			header_a: 'CS: Header A Pane'
			right_6a: 'CS: Right 6A Pane'
			right_6b: 'CS: Right 6B Pane'
			right_4a: 'CS: Right 4A Pane'
			right_4b: 'CS: Right 4B Pane'
			right_4c: 'CS: Right 4C Pane'
			middle_a: 'CS: Middle A Pane'
			# [Continue listing all remaining panel options matching your drawing names here...]

			footer: 'Footer Region'
			</pre>2. Create the Shared Layout Grid Template (<code>page--costa-sano.html.twig</code>)

			Create this template file in your theme's <code>templates/layout/</code> directory. It maps the regions defined in the <code>.info.yml</code> file to the universal responsive layout CSS selectors.

			<pre>

			{# Stage 1: The Shared Unlabeled Page Skin Layout #}
			<div class="costa-sano-skin">

			<!-- TOP PANES -->
			{% if page.full_pane %}
			<div class="pane full-pane">{{ page.full_pane }}</div>
			{% endif %}

			<!-- SECTION 1 -->
			<section class="cs-section section-1">
			{{ page.content }} {# Standard body text and core field location #}
			<div class="pane content-pane">{{ page.content_pane }}</div>
			<div class="pane full-section-pane">{{ page.full_section_pane }}</div>
			</section>

			<!-- SECTION 2 (50/50 Layout Grid) -->
			<section class="cs-section section-2 grid-2col">
			<div class="pane grid-6a-pane">{{ page.grid_6a }}</div>
			<div class="pane grid-6b-pane">{{ page.grid_6b }}</div>
			</section>

			<!-- SECTION 3 (3/9 Complex Nested Layout Grid) -->
			<section class="cs-section section-3 nested-grid-3-9">
			<aside class="pane left-pane">{{ page.left_pane }}</aside>
			<div class="nested-right-content">
			<div class="pane header-a-pane">{{ page.header_a }}</div>

			<div class="grid-2col">
			<div class="pane right-6a-pane">{{ page.right_6a }}</div>
			<div class="pane right-6b-pane">{{ page.right_6b }}</div>
			</div>

			<div class="grid-3col">
			<div class="pane right-4a">{{ page.right_4a }}</div>
			<div class="pane right-4b">{{ page.right_4b }}</div>
			<div class="pane right-4c">{{ page.right_4c }}</div>
			</div>

			<div class="pane middle-a-pane">{{ page.middle_a }}</div>
			</div>
			</section>

			{# ... Repeat the html structure blocks for sections 4 through 14 ... #}

			</div>

			</pre>STAGE 2: THE ROUTER VIEW (THE NO-CODE BRIDGE)
			To fill these empty page layout blocks automatically based on what the historians filled out, we use a single automated '''Views Block''' display workflow.

			1. Build the Router View

			# Navigate to '''Structure > Views > Add view'''.
			# Name the view: <code>Universal Skin Story Router</code>.
			# Select '''Show: Paragraphs''' of type '''All'''.
			# Check '''Create a block''', name the block display <code>Router: Pane Grid 6A</code>, and click Save and Edit.

			2. Add Context and Filtering Logic

			# In the right-hand '''Advanced''' column, add a '''Relationship''': <code>Paragraph: Content using field_shared_story_cards</code>. (This follows the shared field back to the parent entity).
			# Under '''Contextual Filters''', add '''ID''' (from Content). Set it to use the relationship you created. Under ''When the filter value is NOT available'', select '''Provide default value -> Content ID from URL'''.
			# In the left column under '''Format''', change ''Show:'' to '''Fields'''.
			# Under '''Fields''', add your raw Paragraph fields (Title, Assets, Text etc.) or use '''Paragraph View Mode''' to control card design layout.
			# Under '''Filter Criteria''', add your pane selector field: <code>Paragraph: field_pane_placement</code>. Set the operator to ''Is equal to'' and select your option (e.g., <code>grid_6a</code>).

			3. Deploy Block Layout Across Your Content Architecture

			# Duplicate this Block inside the View for each layout zone (<code>left_pane</code>, <code>right_4a</code>, etc.), setting the '''Filter Criteria''' match value to correspond to each block area name. Save the View.
			# Navigate to '''Structure > Block layout'''.
			# Scroll down to your custom page areas. Locate your '''CS: Grid 6A Pane''' region.
			# Click '''Place Block''', choose your <code>Router: Pane Grid 6A</code> block, and save.
			# In the block configuration pop-up visibility parameters:
			#* Click '''Content types'''.
			#* Check '''Person, Object, Event, and Subchapter'''.
			# Repeat this positioning process for all your remaining panel layout columns.

			----COMPLETED OPERATIONAL WORKFLOW

			This setup provides an incredibly streamlined framework for layout development:

			# '''The Core Sheet:''' Your universal <code>skin-layout.css</code> remains active in the background, shaping columns across every page url.
			# '''The Dynamic Filter:''' When a visitor opens an Event page (<code>/node/456</code>), the global page skin activates.
			# '''The Data Assembly:''' The view checks the URL, isolates Paragraph cards bound to Event <code>#456</code>, reads the historian's dropdown choices, and places the narrative data items natively into the target structural template wrappers.

			----

Roject:Model-Packs/THE skin/split twig & css

Mngr — Mon, 20 Jul 2026 15:50:39 GMT

Created page with "DRUPAL 11: TWO-STAGE SKELETON SKIN ARCHITECTURE (NO-CODE) ARCHITECTURE OVERVIEW The two-stage approach separates the '''structural layout layout grids (Stage 1)''' from the '''dynamic field injection (Stage 2)'''. Instead of tying your custom layout drawing to a single specific content type (like <code>node--person.html.twig</code>), the layout skin is moved up into a global template using '''Theme Regions'''. This allows you to create your complex layout grid '''exac..."

New page

DRUPAL 11: TWO-STAGE SKELETON SKIN ARCHITECTURE (NO-CODE)

ARCHITECTURE OVERVIEW

The two-stage approach separates the '''structural layout layout grids (Stage 1)''' from the '''dynamic field injection (Stage 2)'''. Instead of tying your custom layout drawing to a single specific content type (like <code>node--person.html.twig</code>), the layout skin is moved up into a global template using '''Theme Regions'''.

This allows you to create your complex layout grid '''exactly once'''. Any content type (Person, Object, Event, Subchapter, etc.) can instantly utilize the skeleton layout grids entirely via the administrative block interface.

ARCHITECTURAL BENEFITS

* '''Unified CSS Management:''' The <code>skin-layout.css</code> file handles everything globally. You never have to duplicate your styling code for different sections of the website.
* '''Infinite Scalability:''' If you add a new archival content type next year, it instantly inherits the entire layout framework with zero file modifications.
* '''Historian Friendly:''' Historians continue to use a single, simple form dropdown to position story elements on any page format.

----STAGE 1: DEFINE REGIONS AND BUILD THE STRUCTURAL PAGE SKIN [1]

1. Edit Your Theme's Definition File (<code>your_theme.info.yml</code>)

To make your skeleton drawing areas recognizable to the Drupal user interface, you must register them as theme regions. Open your theme's <code>.info.yml</code> file and list each pane area under the <code>regions:</code> key:

Project:Model-Packs/THE skin/twwxig & css

Mngr — Mon, 20 Jul 2026 15:43:58 GMT

Project:Model-Packs/THE skin/twwxig & css

Mngr — Mon, 20 Jul 2026 15:33:59 GMT

Created page with "= Drupal 11 Site Building: Universal Layout Grid Skin Specification = == Architecture Overview == This document outlines a code-free layout approach designed to achieve the grid skin configuration layout specified for the Costa Sano Project. By combining standard Drupal 11 Paragraphs, a custom Twig node template, and a modern CSS Grid/Flexbox layout scheme, historians can drop storytelling content directly into specific thematic page panes via the Drupal user interface...."

Project:Model-Packs/PubModel/Auto Page - DNN skin

Mngr — Mon, 20 Jul 2026 13:22:33 GMT

Project:Model-Packs/Subchapter teaser cards for storytelling

Mngr — Mon, 20 Jul 2026 12:45:10 GMT