Skip to content

PostCraft

websiteLast commit

A production-oriented publishing workspace that moves one idea through generation, brand controls, platform preview, and scheduled delivery.

Role
Product design and full-stack engineering
Scope
AI workflow, publishing integrations, and background jobs
Status
Active early-stage product
PostCraft workspace showing the social content creation interface

Problem

Creators and small teams repeat the same editorial work for every social platform. They rewrite one idea for different limits, compare weak AI variants, check brand language, and then move the result into separate publishing tools.

Constraints

  1. C1

    AI providers vary in availability, rate limits, model behavior, and key quotas.

  2. C2

    LinkedIn, X, and Facebook each impose different OAuth, account, content, and API requirements.

  3. C3

    Scheduled publishing must survive beyond the request that created it and retain a reviewable status.

Architecture

The Next.js application keeps HTTP boundaries in route handlers, product logic in domain modules, infrastructure in core services, and durable delivery in Inngest.

01

Workspace

Generation, scoring, editing, brand rules, and platform previews

02

Domain services

Validated workflows for content, library, accounts, and publishing

03

Provider layer

OpenRouter, Groq, Gemini, and ZhipuAI with model and key fallback

04

Delivery

MongoDB persistence, Inngest jobs, and social platform APIs

Decisions

D1

Separate provider choice from generation

A provider switcher walks configured models and keys, so product workflows do not depend on one vendor-specific client.

D2

Treat brand voice as stored rules

Required language, blocked language, audience, tone, and persona context are workspace data rather than prompt-only instructions.

D3

Move scheduled work to a durable queue

Inngest owns delayed execution and status transitions instead of relying on an open browser session or a long HTTP request.

Contribution

  • Defined the end-to-end product flow from topic input to platform-ready output.
  • Built the Next.js interface, API routes, domain services, and MongoDB repositories.
  • Implemented multi-provider AI selection, reusable guardrails, scoring, and platform previews.
  • Integrated authentication, account recovery, social OAuth, Inngest scheduling, and publishing records.

Outcomes

  • One workspace now covers generation, comparison, refinement, preview, and delivery.
  • Provider and key fallback reduce the workflow's dependency on a single AI endpoint.
  • Publishing state is persisted for library and insights views instead of ending at generation.
  • Operational limits remain explicit: publishing still depends on platform approval, scopes, account type, and API access.

Product screenshot

PostCraft workspace showing the social content creation interface
The shipped workspace brings generation, brand-aware editing, scoring, and social previews into one flow.

Verified stack

  • Next.js
  • React
  • TypeScript
  • MongoDB
  • Mongoose
  • Redux Toolkit
  • Better Auth
  • OpenRouter
  • Gemini API
  • Groq API
  • ZhipuAI
  • Inngest
  • REST APIs
  • Tailwind CSS
  • shadcn/ui
  • Radix UI
  • Zod
  • Resend
  • System Design

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.