Getting Started
Choose a Collection
Determine which collection best fits your content. See the Collections Overview for details on each type.
Review the Schema
Check the Schema Reference for required and optional fields for your collection.
File Naming Conventions
General Rules
- Use lowercase letters
- Replace spaces with hyphens (
-) - Use descriptive, meaningful names
- Avoid special characters except hyphens
- Keep names concise but clear
Examples
Collection-Specific Guidelines
Events
Events
Include event name and year:
tumaini-festival-2025.mdrefugee-self-advocacy-november-2025.md
Jobs
Jobs
Use job title or role:
secondary-school-teachers.mdprograms-manager.mddigital-archivist.md
Services/Stores
Services/Stores
Use business name:
zawadie-solutions.mdmama-joys-kitchen.mddowa-bakery.md
Marketplace
Marketplace
Use product/service name:
refugee-for-life-book.mdkibebe-baby-products.md
People (Artists, Dancers, Poets)
People (Artists, Dancers, Poets)
Use person or group name:
christian-piniero.mdshakers-dance-crew.md
Frontmatter Requirements
Structure
All content files must start with YAML frontmatter between triple dashes:Required vs Optional Fields
Field Formatting
Strings
Simple strings can be unquoted:Dates
Use ISO 8601 format for date-time:Booleans
Arrays
Objects
Arrays of Objects
Enums (Specific Values)
Some fields only accept specific values. Check the schema for allowed values:Markdown Content
Basic Formatting
After the frontmatter, write your content in Markdown:Heading Levels
Start with
## (h2) for main sections. The # (h1) level is typically reserved for the page title.Lists
Links
Emphasis
Blockquotes
Great for testimonials:Code
Inline code: `code here` Code blocks:Image Guidelines
Image Paths
- Local Images
- External URLs
Store images in the The
public/images/ directory:/images/ path maps to public/images/ in the project.Image Optimization
File Size
- Aim for under 500 KB per image
- Use compression tools
- Consider WebP format
Dimensions
- Logos: 200-400px wide
- Thumbnails: 600-800px wide
- Cover images: 1200-1600px wide
Format
- Photos: JPG/JPEG
- Graphics/logos: PNG or WebP
- Avoid BMP, TIFF
Naming
- Use descriptive names
- Lowercase with hyphens
- Example:
tumaini-festival-2025.jpg
Organizing Images
Create subdirectories for better organization:Content Best Practices
Writing Style
- Write clear, concise descriptions
- Use active voice
- Be specific and factual
- Proofread for spelling and grammar
- Use proper capitalization
Accessibility
- Write descriptive alt text (coming soon)
- Use clear heading hierarchy
- Ensure sufficient contrast for images
- Make links descriptive (“Visit Zawadie Solutions” not “click here”)
SEO Considerations
- Use relevant keywords in titles and descriptions
- Keep titles under 60 characters
- Keep descriptions under 160 characters
- Use descriptive file names for images
- Include location information where relevant
Privacy & Consent
Common Examples
Service Listing
Event Listing
Job Posting
Validation & Testing
Before Submitting
Common Errors
Missing Required Field
Missing Required Field
Error:
Required field missingSolution: Check the schema for required fields and add them to your frontmatterInvalid Date Format
Invalid Date Format
Error:
Invalid dateSolution: Use ISO 8601 format: 2025-10-30T09:00:00Z or simple date: 2025-10-30Invalid Enum Value
Invalid Enum Value
Error:
Invalid enum valueSolution: Check allowed values in schema. For example, job type must be one of: full-time, part-time, contract, volunteer, internshipYAML Syntax Error
YAML Syntax Error
Error:
YAML parsing failedSolution: Check for:- Proper indentation (use spaces, not tabs)
- Matching quotes
- Correct array/object syntax
- No special characters without quotes
Invalid Image Path
Invalid Image Path
Error:
Image validation failedSolution: For photos collection, ensure image path starts with /images/ or is a valid URLSubmission Process
Via GitHub
- Fork the repository
- Create your content file in the appropriate collection folder
- Add images to
public/images/if needed - Commit with descriptive message
- Submit pull request
Via Email
Send your content file and any images to: content@dzaleka.com Include:- Collection name
- Content file (.md)
- Images (if any)
- Your contact information
Getting Help
Collections Reference
Learn about each collection type
Schema Reference
Detailed field specifications
Example Files
Browse existing content for examples
Contact Support
Email us for assistance