Have a static site? Stop losing time after your draft is done.
Floyi 2.9.4 gives you a faster path from draft to published content.
Most content teams still move files by hand, rebuild frontmatter, re-upload images, and clean up formatting before anything goes live.
Now you can publish directly from Floyi to GitHub for Astro, Next.js, Hugo, Jekyll, Docusaurus, and other static site workflows. Your article is sent as Markdown or MDX with frontmatter, images, and optional schema markup included.
That matters because Floyi is built to connect strategy to execution. You build the topical map, generate the brief, write the draft, and now move the content closer to deployment without breaking the workflow in the final steps.
Publish content to static sites with Floyi
Here’s what’s new:
Publish straight to GitHub - Send finished content from Floyi to your repository without the usual copy-pasting and manual file setup.
Framework presets - Choose Astro, Next.js, Hugo, Jekyll, or Docusaurus, and Floyi fills in the common paths and structure for you.
Frontmatter and images included - Set your frontmatter template once, and Floyi carries over the article details and images as part of the same publish action.
This update also improves Topical Research.
Floyi now uses live Google and YouTube autocomplete during subtopic generation. That gives your topic maps another layer of current search behavior, so topic ideas are shaped by what people are searching for now.
The result is better topic coverage, stronger briefs, and less guesswork about what to create next.
Floyi 2.9.4 is available now. Read the full release notes
Yoyao Hsueh
Founder @ Floyi
