Images first, then the markdown
The order is deliberate. Committing the markdown triggers your build, so the images have to be in place already or the first build ships broken images.
Integration
If the site is static and lives in a repo, an article is a file. Inowara commits markdown and images into your repo, and your existing build takes it from there.
What we need from you
What lands on the destination
How it works
The order is deliberate. Committing the markdown triggers your build, so the images have to be in place already or the first build ships broken images.
Title, description, date, image, category and author go into frontmatter. The body stays HTML inside the markdown, which every static site generator renders without loss.
If the slug changes, the old file is deleted in the same pass, so two versions of the same text never sit on the site.
Limits
It's on the page on purpose. Better seen now than after the first publish.
FAQ
Yes, with any generator that reads markdown from the repo. Frontmatter fields are configured to match your template.
Yes. Every publish is a commit with a clear message, so article history lives in git like everything else.
Other integrations
Next step
Connect any site — services, webshop or blog. The plan builds itself, articles are written and published on schedule, and the first one is free.