User contributions for Mngr

15:1915:19, 13 July 2026 diff hist +93 Project:Model-Packs/PubModel/PubModel-short No edit summary Tag: Visual edit
14:5314:53, 13 July 2026 diff hist +2,026 N Project:Model-Packs/PubModel/PubModel-short Created page with " = AI Model Package = == Publication Model == === Version 0.1 === === Purpose === Provide the architectural context required before discussing publication components. This document contains '''accepted design decisions''', not implementation details. ---- = Scope = Applies to: * Publication pages * Bricks * Components * Viewers Does '''not''' describe: * Data model * Brick implementation * CSS/JS * Drupal configuration ---- = Design Principles = === P1 === Cos..." Tag: Visual edit
14:4714:47, 13 July 2026 diff hist +4,324 N Project:Model-Packs/PubModel Created page with " = AI Model Package – Publication Model = '''Version:''' Draft 0.1 '''Purpose''' This document contains the architectural principles governing the Costa Sano Publication Framework. It is '''not''' an implementation document. Its purpose is to provide the architectural context required before discussing publication components such as MediaCard, HistoricalCard, CarouselCard, TimelineCard or future publication elements. ---- = 1. Publication Philosophy = Costa Sano i..." Tag: Visual edit
13:4013:40, 13 July 2026 diff hist +5,406 N Drupal:PubModel/DocumentViewer approach Created page with " = Costa Sano Publication Framework = == DocumentViewer Architecture – Design Proposal (Version 1) == === Purpose === The purpose of this document is to define the architectural principles for introducing a dedicated '''DocumentViewer''' into the Costa Sano Publication Framework. This document intentionally focuses on architecture and responsibilities rather than implementation details. ---- = 1. Background = The original MediaCard displayed both images and PDF doc..." current Tag: Visual edit
07:3707:37, 13 July 2026 diff hist +4,728 N Project:Roadmap MediaCard Created page with "= Architecture Roadmap = == Evolution of the MediaCard towards a PDF.js-based DocumentViewer == === Objective === The current MediaCard successfully displays both images and PDF documents. Images are displayed with a zoom viewer while PDF documents currently use the generated first-page thumbnail and are shown in the same zoom modal. The next evolution is '''not''' to redesign the MediaCard itself, but to introduce a dedicated '''DocumentViewer''' for PDF documents wh..." current Tag: Visual edit

21:3421:34, 11 July 2026 diff hist +3,410 Drupal:Outputting a page in PDF format No edit summary current
21:3021:30, 11 July 2026 diff hist +5,899 N Drupal:Outputting a page in PDF format Created page with "= Drupal Heritage Project: Automated PDF Documentation Export = This page documents the setup for an automated PDF export feature for documentation and story pages. It utilizes the '''PDF Forge''' module, which processes PDFs server-side without relying on external system tools (like Puppeteer or wkhtmltopdf). This ensures that backgrounds are stripped out completely and custom branding (logos and running footers) are dynamically applied. == Prerequisites == * Drupal 1..."

18:5418:54, 8 July 2026 diff hist +1,211 Project:Architecture/The DUAL architecture No edit summary current Tag: Visual edit
18:5318:53, 8 July 2026 diff hist −714 Project:Architecture/The DUAL architecture No edit summary
18:5218:52, 8 July 2026 diff hist +2 Project:Architecture/The DUAL architecture No edit summary
18:4818:48, 8 July 2026 diff hist +5,953 N Project:Architecture/The DUAL architecture Created page with "= The Costa Sano Dual Architecture = ''One Publication Engine – Two Knowledge Domains'' == Introduction == The Costa Sano project consists of two complementary environments that share the same architectural philosophy while serving completely different purposes. The first environment is the **Workbench**. The second environment is the **Heritage Project**. Although their content differs completely, both are built upon the same publication principles. This common..." Tag: Visual edit: Switched
18:4818:48, 8 July 2026 diff hist +53 N Project:Architecture Created page with "<nowiki>= Project Architecture description =</nowiki>" current Tag: Visual edit
18:2318:23, 8 July 2026 diff hist +421 N Maintenance:Overall/Twig debugging Created page with "== '''Twig Debugging''' == During component development, Twig debugging may be enabled in <code>development.services.yml</code> to display template suggestions and theme hook information. Before validating generated publication pages or creating Brick Packages, disable Twig debugging and clear the Drupal cache. This ensures the generated HTML remains clean and suitable for publication, inspection, and AI consumption." current Tag: Visual edit
13:1313:13, 8 July 2026 diff hist +5,968 N Drupal:AutoPages/Brick Package generator Created page with "= Automatic Brick Package Generation = ''Design Guide – Version 1.0'' == Introduction == The initial objective was to produce a documentation package for the MediaCard Brick that could be used as an AI Package. During the design process it became clear that the real objective is much broader. Instead of manually documenting individual Bricks, the Workbench should become capable of generating complete documentation pages automatically from the information already st..." current

17:0117:01, 6 July 2026 diff hist +4,037 N Drupal:Custom Text Field layout options Created page with "= Drupal Views: Custom Text Field Layout Capabilities = This document describes all layout elements available when using '''Custom text fields''' (Rewrite results) inside '''Drupal 11.3 Views''', including HTML, Twig logic, field tokens, and constraints. == Overview == Drupal Views allows you to hide fields and use a '''Custom text''' field to build your own layout. This technique provides full control over the HTML structure and enables Twig logic inside Views withou..." current Tag: Visual edit: Switched

20:1720:17, 4 July 2026 diff hist +4,834 N Platforms:DevEnv/Opening VS Code from a Drupal Form Link on Windows 11 Created page with "= Opening VS Code from a Drupal Form Link on Windows 11 = == Purpose of This Document == This page explains the complete conceptual background behind opening '''Visual Studio Code''' directly from a '''Drupal form link''' on a Windows 11 workstation. It expands on the existing setup guide by clarifying ''why'' a local server is required, ''how'' the browser interprets the link, ''what roles Node.js and Express play'', and ''why the mapped network drive (T:) is essential..." current Tag: Visual edit
20:0620:06, 4 July 2026 diff hist +4,001 N Platforms:DevEnv/Node.js npm express Created page with "= Express, Node.js, Drupal, and VS Code: A Practical Overview = == Purpose of This Document == This page provides a clear, concise explanation of how '''Express''', '''Node.js''', '''Drupal''', and '''Visual Studio Code (VS Code)''' relate to each other when working on Windows 11. It is written for inclusion in a MediaWiki knowledge base and focuses on practical understanding rather than deep technical theory. ---- == Node.js == Node.js is a '''JavaScript runtime envir..." current Tag: Visual edit

17:1117:11, 3 July 2026 diff hist +5,590 N Project:Workbench overview (final version)/Brick as doc point Created page with "= Workbench Documentation Strategy – Brick Documentation Packages = ''Draft 1.0'' == Background == During the design of the MediaCard extension (supporting different viewers such as PDF.js), a broader question arose: ''How can the Workbench provide sufficient information for both a developer and an AI assistant to understand one publication building block without requiring the complete Drupal project?'' Initially, the idea was to introduce a new content type repres..." Tag: Visual edit: Switched
16:5116:51, 3 July 2026 diff hist +2,898 N Project:Workbench overview (final version)/Package Proposal Created page with "= Publication Component Package (PCP) = == Version 1.0 == === 00-README.md === This is the only file I will read first. It should answer, in plain English: * Component name * Current version * Date * Status (Experimental / Stable / Production) * Purpose of the component * Main capabilities * Known limitations * Planned extensions Example ---- = 01-Architecture.md = Describe the architecture. For example Include a small explanation of the responsibility of every l..." Tag: Visual edit
16:4516:45, 3 July 2026 diff hist +5,590 N Project:Workbench overview (final version)/AI package proposal Created page with "= Publication Component Package (PCP) Specification = ''Version 1.0 – Experimental'' == Purpose == The Publication Component Package (PCP) is intended to describe one publication component of the Costa Sano Heritage website in a structured way. The package has three goals: Allow a developer to understand a component quickly. Allow an AI assistant to understand the architecture and implementation without requiring the complete Drupal project. Form the basis for aut..." Tag: Visual edit

15:4815:48, 2 July 2026 diff hist +8 N Tools:Test Created page with "= test =" current
15:4815:48, 2 July 2026 diff hist +55 Tools:Content No edit summary current
15:4615:46, 2 July 2026 diff hist +22 N Tools:Content Created page with "= Tools Content Page =" Tag: Visual edit: Switched
15:2015:20, 2 July 2026 diff hist +53 DNN:Content No edit summary current
15:0415:04, 2 July 2026 diff hist −1 Project:Bricks/Components-Bricks-Structures No edit summary current

19:1819:18, 1 July 2026 diff hist +3,981 N Drupal:Maintenance/Removing stale (ghost) modules Created page with "= Drupal Maintenance – Removing Stale (Ghost) Modules = == Purpose == During the lifetime of a Drupal installation, it may happen that a module is removed from the filesystem (or via Composer) without first being properly uninstalled. Drupal then retains references to that module although the code no longer exists. Such a module is called a '''stale''' or '''ghost''' module. Typical symptoms appear during: <syntaxhighlight lang="text"> drush updatedb </syntaxhighl..." current
19:1719:17, 1 July 2026 diff hist +23 N Drupal:Maintenance Created page with "= Maintenance section =" current
12:0012:00, 1 July 2026 diff hist 0 m Drupal:Config/Test-23 Mngr moved page DNN:Config/Test-23 to Drupal:Config/Test-23 without leaving a redirect current
11:5911:59, 1 July 2026 diff hist 0 m Drupal:Config/Test-23 Mngr moved page DNN:Config/Test-2 to DNN:Config/Test-23 without leaving a redirect
11:5811:58, 1 July 2026 diff hist 0 m Drupal:Config/Test-23 Mngr moved page DNN:Config/Test to DNN:Config/Test-2 without leaving a redirect
10:4110:41, 1 July 2026 diff hist −26 Project:Workbench overview (final version) No edit summary Tag: Visual edit
10:3810:38, 1 July 2026 diff hist +1,851 Project:Workbench overview (final version) No edit summary Tag: Visual edit
10:2710:27, 1 July 2026 diff hist +5,786 N Project:Workbench overview (final version) Created page with "= Costa Sano Engineering Workbench = == Definitive Definition of the R-S-B-C Architecture == === Purpose === The Costa Sano Engineering Workbench is '''not''' a duplicate of the Drupal administration interface. Its purpose is to provide: * architectural documentation; * architectural navigation; * implementation traceability; * engineering memory; * a developer workbench. The Workbench documents the Costa Sano architecture independently from Drupal while maintaining..." Tag: Visual edit
08:4108:41, 1 July 2026 diff hist +4,558 N Drupal:C-Modules/webtools Created page with "= Adding a Custom "Edit Related View" Button to a Drupal Link Field Widget = This document explains how to add a custom button to a Drupal node edit form, based on the value stored in a Link field. It covers the problem, the underlying Drupal mechanics, and the final working implementation. == Overview == We want to add a button labeled '''Edit related view''' inside the widget of a Link field named '''field_re_edit_resource''' on the node edit form of the content t..." current

15:0315:03, 30 June 2026 diff hist +47 Drupal:General/Views - Relationship vs Contextual Filters No edit summary current
15:0215:02, 30 June 2026 diff hist +2,289 N Drupal:General/Views - Relationship vs Contextual Filters Created page with " In Drupal 11.3 Views, '''Relationships''' and '''Contextual Filters''' are advanced features that let you build dynamic queries without writing SQL. Here is the straightforward definition and purpose of each: ----1. Relationships (The SQL "JOIN") * '''Definition''': A tool that connects your primary View content type to a separate, related piece of data in the database. * '''Purpose''': To display information that doesn't natively belong to the main item you are listi..." Tag: Visual edit
14:0814:08, 30 June 2026 diff hist +27 N Platforms:DevEnv Created page with "= Development Environment =" current
12:3312:33, 30 June 2026 diff hist +4,114 N Platforms:DevEnv/Opener Created page with "= Developer Workbench: VS Code Opener Service (Windows 11 + Drupal + Network Drive) = == 1. Overview == This document describes how to install, configure, and run a lightweight Node.js service on Windows 11 that allows Drupal to open local or network‑mounted files directly in Visual Studio Code. The service exposes a simple HTTP endpoint: <pre> http://localhost:7777/open?path=<absolute-windows-path> </pre> When accessed, it opens the requested file in VS Code..." current Tag: Visual edit: Switched
09:1409:14, 30 June 2026 diff hist 0 m Platforms:Drupal Mngr moved page Platform:Drupal to Platforms:Drupal without leaving a redirect current
09:1309:13, 30 June 2026 diff hist 0 m Platforms:Drupal/Drupal migration Mngr moved page Platform:Drupal/Drupal migration to Platforms:Drupal/Drupal migration without leaving a redirect current
09:1209:12, 30 June 2026 diff hist 0 m Platforms:Tooling Mngr moved page Platform:Tooling to Platforms:Tooling without leaving a redirect current
09:1209:12, 30 June 2026 diff hist 0 m Platforms:Tooling/Drupal Workbench Mngr moved page Platform:Tooling/Drupal Workbench to Platforms:Tooling/Drupal Workbench without leaving a redirect current
07:2107:21, 30 June 2026 diff hist +525 N Platforms:Tooling/Drupal Workbench Created page with " == Characteristic of each part of the drupal engineering environment: == === Workbench === Answers: * What is this? * Why does it exist? * How does it fit into the architecture? * Where is it? ---- === MediaWiki === Answers: * How does it work? * Why was it implemented this way? * What mechanisms are involved? ---- === VSCode === Answers: * How do I modify it? ---- === Drupal === Answers: * How do I execute it? ----Those four environments complement each oth..." Tag: Visual edit
07:1907:19, 30 June 2026 diff hist 0 m Platforms:Tooling Mngr moved page Platform:Environment to Platform:Tooling without leaving a redirect
07:1807:18, 30 June 2026 diff hist +26 N Platforms:Tooling Created page with "= Description of tooling =" Tag: Visual edit: Switched

17:2317:23, 29 June 2026 diff hist −13 Platforms:AlmaLinux/map filesystem on windows No edit summary current Tag: Visual edit
17:2217:22, 29 June 2026 diff hist +4,097 N Platforms:AlmaLinux/map filesystem on windows Created page with " = Connecting a Windows Workstation to the AlmaLinux File System using SSHFS = == Purpose == The Costa Sano development environment uses Visual Studio Code running on Windows while the Drupal source code resides on an AlmaLinux virtual machine. To simplify navigation and editing of Twig, CSS, PHP and other component files, the AlmaLinux file system is mounted as a Windows drive using SSHFS. This allows: * Browsing the Drupal file structure from Windows Explorer. * Op..." Tag: Visual edit

15:4015:40, 26 June 2026 diff hist +3,681 N Project:Evolution/Phases Created page with "Now I will prepare some new content types like Resource and Story to start moving in the automatic publication direction with a good knowledge of what I actually have already in the system. I think that's exactly the right next step. Notice that you're '''not''' starting with automatic publication. You're preparing the '''knowledge infrastructure''' that will make automatic publication possible. That is a very different strategy, and I think it's the right one. If I..." current Tag: Visual edit
15:2615:26, 26 June 2026 diff hist +4,338 N Project:Evolution Created page with "= Evolution of the Costa Sano Platform = The Costa Sano platform did not originate from the selection of a particular technology. Instead, it evolved through a series of practical decisions driven by the requirements of the project. == Initial Objective == The original objective was to build a collaborative heritage information system capable of: * managing large collections of historical documents, * organising structured heritage information, * supporting collaborat..." current Tag: Visual edit
15:0715:07, 26 June 2026 diff hist +49 N Project:Model-Packs Created page with "= AI discussion packages for different subjects =" Tag: Visual edit: Switched

13 July 2026

11 July 2026

8 July 2026

6 July 2026

4 July 2026

3 July 2026

2 July 2026

1 July 2026

30 June 2026

29 June 2026

26 June 2026