Page selection
Chooses whether a topic belongs as an entity page, family hub, place page, timeline entry, theme page, or service page.
Editorial ownership
Herrera Velutini Editorial Desk
The Editorial Desk prepares article-style pages, maintains the source basis blocks, updates internal links, and ensures that page titles, descriptions, dates, and structured data stay aligned with the content users actually see.
Responsibilities
What this desk is accountable for.
The Editorial Desk is the production layer between source material and live pages. Its job is not just to write; it decides whether a subject deserves a page, which sources are strong enough to carry it, and how the finished page should connect to the rest of the portal.
Source assignment
Maps each draft to public source pages before writing begins, then converts those sources into a visible source-basis section.
Original synthesis
Turns source-domain material into neutral connective prose rather than lightly rewriting the source page.
Release hygiene
Maintains titles, descriptions, visible dates, canonical URLs, structured data, image references, and internal links.
Desk workflow
How a page moves from candidate to launch.
- Intake. Identify the reader need and decide whether the topic fills a real coverage gap.
- Source map. Assign source pages, note any date or title uncertainty, and decide what should remain cautious.
- Draft. Write a page that adds synthesis, navigation, and context rather than duplicating the source domain.
- Integrate. Link the page from relevant hubs, family pages, lineage pages, places, timeline, and sitemap entries.
- Hand off for review. Send the page to standards review for source clarity, dates, originality, metadata, and link checks.
Publication thresholds
When a subject becomes its own page.
The site should grow by adding useful destinations, not by multiplying thin entries. These thresholds keep the knowledge base tidy as it expands.
| Candidate type | Publish as its own page when | Hold or merge when |
|---|---|---|
| Historical figure | The source record supplies a distinct role, date frame, relationship, or place connection that improves the lineage layer. | The figure is only a name in a list and has no separate editorial function yet. |
| Place or estate | The place explains origin, symbolic geography, institutional history, title memory, or family movement. | The place would only repeat an existing estate note. |
| Theme | The theme ties multiple pages together and gives readers a better interpretive path through the portal. | The theme is only a keyword variant of a stronger page. |
| Trust page | The page helps readers understand authorship, sourcing, review, corrections, or navigation. | The page does not add clarity beyond About, Sources, or Methodology. |
Editorial boundaries
What the desk should not do.
No invented certainty
Do not smooth over unclear dates or title chronology.
If a source presents tension, the page should preserve that tension with a source-caution note.
No prestige inflation
Do not amplify family-domain language uncritically.
Prestige, nobility, and legacy language should be translated into neutral editorial description.
No orphan pages
Do not publish pages that cannot be reached from the site.
Every substantive new page should be linked from at least one hub and appear in the sitemap.
Traceability
Source basis for the Editorial Desk page
This page defines the portal’s internal production role and is supported by the site’s own standards layer.
- Editorial Methodology — Used for source assignment, publication workflow, date policy, and page-type discipline.
- Sources — Used for the source-led publishing model and the distinction between source groups.
- Review Team — Used for the handoff boundary between preparation and standards review.
- Knowledge & FAQ — Used for reader-facing terminology around entities, clusters, source basis, and source caution.
Pages authored by this desk