Publish articles via Git (GitHub, GitLab)
For static websites (Astro, Next.js, Hugo, Jekyll, Eleventy, Vite/React), Aimarage writes approved articles as a Markdown file with YAML frontmatter straight into your repo; Cloudflare Pages, Vercel or Netlify then rebuild the site. Set it up under Project settings > Blog, "Publish automatically", type "Git": provider GitHub or GitLab (gitlab.com or your own instance via the GitLab address), repo as owner/name, branch, folder (e.g. src/content/blog), file name with {slug}, {date} and {lang} (default {slug}.md), the public article address (e.g. https://example.com/{lang}/blog/{slug}) and optionally an image folder. Token: for GitHub a fine-grained token for this repo only with "Contents: Read and write", for GitLab a Project Access Token with role Developer (Maintainer for a protected branch) and scope api. The token is stored encrypted and never shown. "Check" tests access to repo and branch and write permission without committing.
The frontmatter contains title, description, date, updated, slug, lang, translationKey, image (only with an image), canonical, draft (only with "create as draft only") and ai_generated (AI label). Each language becomes its own file; without {lang} in the file name, translations get the language appended (article.en.md). A new version updates the same file and keeps the first publication date. Aimarage only writes into the configured folder. Your site has to read these files as blog pages: the settings show a sentence for your Claude and the frontmatter format to copy. Images are only included with an image folder; if it sits under public/ or static/, that part is dropped from the image address. If "Post externally" is off, nothing is committed (dry run). Social posts waiting for the article then get the public address as their link. If you discard the task, the file stays in the repo; delete it yourself.