Skip to content

feat(web): add detailed public tool landing pages - #201

Open
baba-dev wants to merge 2 commits into
mainfrom
feat/public-tool-landing-pages
Open

baba-dev wants to merge 2 commits into
mainfrom
feat/public-tool-landing-pages

Conversation

@baba-dev

Copy link
Copy Markdown
Owner

What changed

  • adds detailed, public-facing landing pages for 12 major creative capabilities under /tools/
  • uses sanitized screenshots captured from the authenticated product with example prompts entered and no generation, audition, processing, or chat submission
  • lists relevant enabled models and operations from the live public pricing catalogue
  • adds unique SEO metadata, canonical URLs, Open Graph images, FAQ and application structured data
  • cross-links related tools, Solutions, Learn, and Pricing content
  • adds Pixel AI to the public tool catalogue and an original SVG cover
  • moves MediaKit to /tools/media-toolkit with a permanent redirect from /tools/mediakit

Validation

  • pnpm format:check
  • DATABASE_URL=… pnpm lint
  • pnpm typecheck
  • AUTH_SECRET=… DATABASE_URL=… pnpm test (all configured suites passed; integration-only suites skipped)
  • AUTH_SECRET=… DATABASE_URL=… APP_URL=… pnpm build
  • production-server smoke check: all 12 routes returned HTTP 200; legacy MediaKit route returned HTTP 308

Product capture note

The browser session was already authenticated. Only form fields and local controls were used; no billable action was triggered. Account, credit, and workspace-identifying UI was removed from the public assets.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant