BunshipBunship
Integrations

Marketing Site and CMS

Buyer-facing content operations guide: marketing pages, blog CMS, AI generation, cover generation, and locale sync.

This is not just a blog module. Bunship already connects the full content lifecycle for you:

  • Public marketing pages and blog rendering
  • Admin CMS content studio
  • AI-assisted metadata and copy generation
  • AI cover image generation
  • Multi-locale publish sync

What You Can Use Out of the Box

  • Marketing pages and blog surfaces (home/features/pricing/blog)
  • Post/category/tag management
  • Draft, publish, unpublish, and scheduled publish
  • CMS locale management and locale sync on publish
  • SEO fields (title, slug, description, keywords)

New CMS Generation Capabilities

1. AI Metadata Generation

Inside the post editor, "AI Generate Meta" can generate:

  • Title
  • Slug
  • Description
  • Keywords

Endpoint: /v1/admin/cms/posts/ai-meta

2. AI Promote Stream (Article Draft)

Generate article copy in stream mode and receive metadata in the same flow, useful for first-draft writing and campaign content.

Endpoint: /v1/admin/cms/posts/ai-promote/stream

3. AI Cover Generation

Generate post cover images directly in the editor with landscape, portrait, and square options.

Endpoints:

  • Sync generation: /v1/admin/ai/covers/generate
  • Async tasks: /v1/admin/ai/covers/tasks/*

CMS cover generation in Admin mode does not consume end-user credits by default, which is ideal for content operations teams.

  1. Configure CMS locales first (for example en, zh, ja).
  2. Create categories and tags for each locale.
  3. Complete body content, SEO metadata, and cover in the content studio.
  4. Choose whether to sync to other locales at publish time.
  5. Iterate title, description, and keywords using search performance data.

Pre-Launch Checklist

  1. Each target locale has enough publish-ready content.
  2. Key landing pages include metadata and OG images.
  3. Image URLs are served from production storage/CDN.
  4. Slug policy is stable to avoid broken historical links.
  5. Publish and rollback flows are tested in admin.

Next Steps