GitHubLive
Git-based CMS: Your articles arrive as a pull request.
Connect the repo your site already builds from. Verand reads it once, works out what kind of site it is, and writes files in the shape your site already expects. Your host deploys when you merge, the way it always has.
The GitHub App, or a token, on one repo. Verand reads the file list and tells you what it found.
You see what passed and what needs a look before anything leaves Verand.
The article and its images in one commit, on a branch of its own.
One click, and it reads before it writes.
You install the Verand GitHub App on the one repository your site builds from, or paste a fine-grained token that can see only that repository. Verand checks it can reach the repo and push, then lists the files once to work out what kind of site you have.
Vercel, 
Netlify, 
Cloudflare Pages and GitHub Pages need nothing at all.Repo reachable, push access confirmed. Publishing opens a PR against main for you to merge. Scheduled posts are merged by Verand at their time.
Astro (SSG)Articles publish as MD content files. Your site's own layout wraps them at build, so a redesign re-wraps every article automatically.
Nothing reaches your repo until you say so.
Every article is checked before it can go anywhere. Are the numbers cited, is the disclaimer your industry needs actually in there, does anything read like a promise you are not allowed to make. You get the answer on one screen, in words.
Compliance · gatePass · 6/6
willowdaleequity.com
The article and its images land in one commit.
Verand writes the files your site expects, on a branch of its own, and opens a pull request. The images ride in the same commit, because an article whose hero arrives separately is a broken page the moment you merge.
Astro, 
Next, 
Hugo, 
Eleventy, 
Jekyll, 
Gatsby, 
Nuxt, 
Docusaurus and 
SvelteKit) it writes a content file, with the frontmatter copied from your own recent posts. Your layout wraps it at build, so a redesign re-wraps everything Verand ever published.Fixing one line later does not mean rebuilding the page.
Say you want to add a source to one sentence, or move a date on to this year, on a page that has been live since 2023. You approve that one change in Verand and it commits the edited file to your main branch. Your host deploys it like any other commit.
Scheduled posts go live at their time.
Schedule an approved article and Verand opens the pull request and merges it at that time, after the compliance check runs again. If your repo requires a review or checks, the pull request stays open and Verand tells you. Prefer one more look? Switch the site to open the pull request at that time and leave the merge to you.
One click to connect, no token to make.
Install GitHub App takes you to GitHub, where you grant Verand the one repository your site builds from, and brings you back connected. When your host deploys from git, the card says so. A fine-grained token is still there for teams that would rather use one.
Your site is on Cloudflare Pages, which deploys from a git repo. Connect GitHub to apply fixes there.
A scheduled post shows its own plan.
Open the publish menu on a scheduled post and it says exactly what happens next: the repo, the time, and that it goes live only if the article is still Ready, unchanged, and passes the compliance check. Open the pull request now, reschedule, or take it off the schedule.
willowdaleequity.comThe four things people ask first.
Will it ever merge its own pull request?
Only a post you’ve scheduled. At its time, Verand opens the pull request and merges it after the compliance check runs again, unless you’ve set scheduled posts to open a PR for one more review. Anything you send now, it opens and stops, and merging it stays yours.
What if my repository is private?
That is the normal case. The GitHub App or the token is scoped to the one repo you point it at, and Verand only ever talks to GitHub, never to your host.
What if you cannot tell what my site is?
It says so. An unknown repo gets the plain article HTML and an honest label, rather than a guessed layout committed into your site.
Do I need to change anything about my host?
No. Vercel, Netlify, Cloudflare Pages and GitHub Pages all deploy on merge exactly as they do today. The integration is with GitHub, not with them.
Three steps, all of them yours.
Nothing here needs a developer, and nothing here touches your host.
Install the GitHub App
In Verand: Settings, then Integrations, then GitHub. Install GitHub App, and on GitHub grant it the one repository. A fine-grained token with read and write on contents and pull requests works too.
Pick the repository
Back in Verand, choose the repo this site publishes to. It opens pull requests against the branch your site builds from.
Read what it found
Verand lists the repo once and tells you the site type and the files it saw. Green means the next article can open a pull request.
Connect the site you have. Rank on Google and in AI answers from ChatGPT, Gemini, Google AI Overviews, Google AI Mode, Perplexity and Claude. Then approve what ships.
Articles arrive as a pull request with the image and the checks done. Your reviewer merges it or schedules it; nothing lands on the branch that a person didn’t approve.
Seven days, every feature unlocked, one click to cancel. WordPress and static sites on GitHub today.
The 2019 fund returned 14.2% net to investors, and this offering carries guaranteed returns of 12 to 15% over a five year hold.
A guaranteed return is deceptive in any financial context and can be a securities violation. Say targeted or projected return, with its basis.
ChatGPT
Gemini
AI OverviewsAI Mode
Perplexity
Claude
Willowdale Equity and four competitors · 14 days
YouEquityMultipleBAM Capital
Origin Investments
Ashcroft Capital31%You 27%14%11%8%