Universal Metadata Prompt
- Title: Universal Metadata Prompt
- Domain Name: `https://universalcake.com`
- Path: `/areas/accessibility/`
# Prompt for Content and Metadata Generation
## Minimum Required Inputs
- Title: Curiosity and Uncharted Territory
- Domain Name: `https://universalcake.com`
- Path: `/resources/practices/curiosity/`
## Optional Inputs
These values can be customized if available:
- Image: (Provide a direct URL to an image if applicable)
- Large Image: (Provide a URL for a high-resolution image if applicable)
- Twitter Handle: (Used for Twitter metadata, e.g., `@universalcake`)
- Author Name Override: (If different from Christopher Steel)
- Publisher Name Override: (If different from "Universal Cake")
- Canonical URL Override: (If different from the generated URL)
- Custom Description: (Overrides the auto-generated description)
- Video Metadata: (If applicable, provide video title, description, upload date, content URL, and embed URL)
## Calculated Input
Convert the Title into a lowercase, URL-friendly `File_Name` by:
- Replacing spaces with hyphens (-).
- Keeping existing double hyphens (--) as they are.
- Removing all special characters except for hyphens (-).
- Ensuring all letters are lowercase.
- Removing any leading and trailing hyphens.
Regex Example for Automation:
```regex
[^a-z0-9-]+ # Removes invalid characters
```
# Markdown Content Template
## Metadata Section (YAML format)
Additional Prompt Instructions for the metadata:
- No lines with no text.
- Output is for a Linux system.
- Each `metadata_key: "metadata value"` pair **must** be on its own line.
- The metadata section begins with `---` on the first line of the output.
- The metadata section ends with `---` on a new line.
Generate a YAML metadata block using the provided Title, Domain Name, and Path, while incorporating any Optional Inputs if provided:
```yaml
Title: "<Title>"
Description: "<Custom Description or auto-generated SEO-friendly description>"
Author: "<Author Name Override or 'Christopher Steel'>"
Date: "<auto-generated current date>"
License: "CC BY-SA 4.0"
Tags:
- "<tag1>"
- "<tag2>"
- "<tag3>"
- "<tag4>"
- "<tag5>"
URL: "<Canonical URL Override or Domain Name + Path>"
Path: "<Path + File_Name>"
Canonical: "<Canonical URL Override or Domain Name + Path>"
Sitemap: true
Keywords:
- "<keyword1>"
- "<keyword2>"
- "<keyword3>"
- "<keyword4>"
- "<keyword5>"
DC_Title: "<Title>"
DC_Creator: "<Author Name Override or 'Christopher Steel'>"
DC_Subject: "<A short description of the content’s subject matter>"
DC_Description: "<A detailed description for structured data compliance>"
DC_Language: "en"
DC_License: "https://creativecommons.org/licenses/by-sa/4.0/"
Robots: "index, follow"
# Open Graph Metadata (for Facebook, LinkedIn, WhatsApp, etc.)
OG_Title: "<Title>"
OG_Description: "<Custom Description or auto-generated SEO-friendly description>"
OG_URL: "<Canonical URL Override or Domain Name + Path>"
OG_Image: "<Image if provided, otherwise fallback>"
OG_Large_Image: "<Large Image if provided, otherwise fallback>"
OG_Type: "article"
OG_Site_Name: "<Publisher Name Override or 'Universal Cake'>"
OG_Locale: "en_US"
# Twitter Cards Metadata (for Twitter, Mastodon)
Twitter_Card: "summary_large_image"
Twitter_Title: "<Title>"
Twitter_Description: "<Custom Description or auto-generated SEO-friendly description>"
Twitter_Site: "<Twitter Handle if provided>"
Twitter_Creator: "<Twitter Handle if provided>"
Twitter_Image: "<Image if provided, otherwise fallback>"
# Schema.org Metadata (for Google, TikTok, YouTube, etc.)
Schema:
"@context": "https://schema.org"
"@type": "Article"
"name": "<Title>"
"author": {
"@type": "Person",
"name": "<Author Name Override or 'Christopher Steel'>"
}
"publisher": {
"@type": "Organization",
"name": "<Publisher Name Override or 'Universal Cake'>"
"logo": {
"@type": "ImageObject",
"url": "<URL to Universal Cake logo>"
}
}
"datePublished": "<Date>"
"dateModified": "<Last_Modified_Date>"
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "<Canonical URL Override or Domain Name + Path>"
}
"description": "<Custom Description or auto-generated SEO-friendly description>"
"image": "<Image if provided, otherwise fallback>"
# Additional Metadata for Telegram, Discord, and Slack
Embed_Title: "<Title>"
Embed_Description: "<Custom Description or auto-generated SEO-friendly description>"
Embed_URL: "<Canonical URL Override or Domain Name + Path>"
Embed_Image: "<Image if provided, otherwise fallback>"
# YouTube & TikTok Video Metadata (if applicable)
Video_Metadata:
"@context": "https://schema.org"
"@type": "VideoObject"
"name": "<Video Title if provided>"
"description": "<Video Description if provided>"
"thumbnailUrl": "<URL to video thumbnail if provided>"
"uploadDate": "<Upload Date if provided>"
"contentUrl": "<URL to video content if provided>"
"embedUrl": "<URL for video embedding if provided>"
```
## Content Structure
- Start with an H1 title matching the document Title.
- Include a well-researched introduction providing context.
- Structure the document using H2 and H3 sections for clarity.
- Write concise, engaging, and factually accurate content.
"Generate a structured reference list in the latest APA format for both research articles and additional resources. The ## References should be divided into two sections: ### Research and ### Additional Resources with resources references grouped by subtype, for example #### Books, #### Videos and so on. Format all references according to APA (7th edition), ensuring proper citation of journal articles, books, and online sources. Each reference should be followed by a concise summary (3-5 sentences) that explains the key findings, relevance, and implications of the work. For research articles, prioritize peer-reviewed journal articles from reputable sources such as PubMed, Google Scholar, and Semantic Scholar. For additional resources, include books, reviews, or reputable online sources relevant to the topic. Use the following structure as needed:"
## References
### Research
### Additional Resources
#### Books
#### Reviews
#### Reputable Websites
## License
This document, *Title*, by **Author** is licensed under the [Creative Commons Attribution-ShareAlike 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
Fixes and Improvements
✅ Fully valid Markdown document ✅ Code blocks are properly nested using four spaces ✅ Maintains your exact formatting ✅ All sections properly indented for readability ✅ No broken syntax—works across all Markdown parsers
This version ensures that everything is properly formatted without breaking the Markdown structure. Let me know if you need further refinements! 🚀