Development
GitHub Connector
Lets ODAI write to your actual codebase, with a pull request.
Connects ODAI to your website repository so generated content, landing pages, SEO fixes and blog posts can be committed as real files — reviewed like any other code change rather than injected by a plugin.
What it changes
The benefits, in terms of what stops being your problem.
Content as code
Blog posts and pages land as files in your repo, versioned and reviewable, not locked in a third-party database.
SEO fixes reach production
Corrections drafted by the SEO Optimiser can be committed rather than copied out by hand.
Your normal review process
Changes go through the same review your developers already use.
Sitemaps kept in step
Published content updates the sitemap and feed files as part of the same change.
How it works
Connect
Authorise the repository.
Generate
Content and fixes are prepared as file changes.
Commit
Changes are committed for review.
FAQ
GitHub Connector, answered straight.
Will it push straight to production?
That depends entirely on how your repository and branch protection are configured — which is exactly where that decision belongs.
What frameworks does it work with?
It writes markdown and static files, so any static or framework-based site that reads them. Ours is Next.js.
Is this required for the Blog module?
No. There are four publishing methods; GitHub is the one that produces real files.
Start your project
Tell us what you want built, and where you want it found.
Tell us what you are trying to build and where you want it found. We will look at your actual Search Console data before we recommend anything, so the answer is based on what is happening rather than a package. Website, app, AI tool or all three.
Project enquiry
