Differences

This shows you the differences between two versions of the page.

--- hortus:publish:projects [2026/04/08 12:14] – savino.frisardi
+++ hortus:publish:projects [2026/04/08 12:16] (current) – savino.frisardi
@@ Line 20: / Line 20: @@
 | **Abstract** | The abstract is the core narrative summary of the project. It explains what the project is about, why it matters, and what users should understand before moving to contributors, resources, discussions, or folders. |
 | **Rich-text project description** | The project page is not limited to one short summary. It can be expanded into a structured presentation using rich-text content, which makes it possible to describe methods, objectives, datasets, teams, outputs, or use cases in a readable academic format. |
+^ Paragraphs^^
 | **Additional paragraphs / sections** | The New paragraph function allows maintainers to add as many structured sections as needed. This turns the project page into a true research landing page rather than a fixed single-text block, and supports long, well-organized presentations. |
 | **Paragraph labels / tags** | Labels help structure and scan the content inside the project page. They can highlight themes, methods, or concepts and make long descriptions easier to navigate visually. |
 | **Paragraph URLs** | URLs inserted at paragraph level allow the project to connect directly to supporting material such as documentation, repositories, institutional pages, forms, publications, or external services. |
 | **Paragraph images by URL** | Image URLs allow sections of the project description to be enriched with visual material. This helps make the page more attractive, supports communication, and gives maintainers a way to add contextual or illustrative multimedia elements. |
+^ Call To Actions buttons^^
 | **CTA buttons (Actions panel)** | The page supports multiple call-to-action buttons. These transform the project page from a static description into an actionable landing page by linking users to training, documentation, videos, surveys, repositories, registration forms, tools, or other internal or external destinations. |
+^ Fields^^
 | **Maintainer field** | This identifies the person responsible for the page. It strengthens accountability, clarifies ownership, and helps users understand who is curating or stewarding the project. |
 | **Copyright and copyright text** | These fields allow the project to state ownership and legal framing more explicitly. They are useful when the page represents institutional work, curated content, or material that should carry a formal rights statement. |
@@ Line 37: / Line 40: @@
 | **Support** | The Support field gives the project a clearer operational dimension by indicating where users should go for help, clarification, or technical assistance. |
 | **External link** | External links extend the project beyond the HORTUS page itself. They can connect the project to websites, forms, portals, datasets, documentation, or partner systems and therefore make the project page more useful as a gateway. |
+**Note on project-resource visibility**: when resources are associated with a project, they become part of that project’s contextual resource layer and can be exposed through the Resources tab. In hierarchical structures, child projects help organize related outputs inside a larger project framework, so resources can be presented in the relevant project or sub-project context depending on how the structure is configured.
+**In practice, the Create Project page lets a maintainer build not just a page, but a complete research landing space: visible, structured, reusable, and connected to people, resources, and actions.**
 ----