Landing pages on a by-hand site: write audit-recommended pages for sites not wired to @balladlabs/next
Get the newsletter
What shipped and what we're learning building Ballad, in your inbox. Unsubscribe any time.
What shipped
Audit findings that call for a landing page now offer Write it even when your site isn't wired to @balladlabs/next. Ballad drafts the page into a manual page collection.
Approving the draft never marks it live, because Ballad can't publish to a site you maintain by hand. The publish screen is worded for a page, and the URL you paste there becomes the page's address for the sitemap, citations and live link.
Who it's for and how it works
If you maintain your site by hand instead of through Content API and @balladlabs/next, this is for you.
The audit, under Content → Website, raises a finding that calls for a landing page. That finding now offers Write it, which drafts the page into a manual page collection. Approving the draft never marks it live. You publish it on your site yourself.
The publish screen is now worded for a page, not an article. Once the page is up, paste the URL where it went live. That URL becomes the page's address for the sitemap, citations and the live link.
The page counts as live only when you say where it lives.
Anything to know
Approving the drafted page never marks it live. Ballad has no way to put a page on a site you maintain by hand, so you publish it yourself. The page only counts as live once you paste its URL into the publish screen, and that URL becomes its address for the sitemap, citations and live link.
