Product media placeholder
Replace this area with a screenshot or short walkthrough video during the media sweep.
Some pages are powered by plugin data. You can adjust design and copy, but the page may also depend on records, forms, checkout, access rules, or scheduling settings.
What this guide helps you do
- Understand which parts of a plugin page are design versus plugin data.
- Edit copy and layout while preserving the workflow.
- Test the customer action after each page change.
Before you start
- Know which plugin owns the page.
- Open the related plugin record before editing the page.
- Create a draft or branch when the change is more than a small copy edit.
Do it manually
- Open the plugin page in the website or plugin editor.
- Identify dynamic areas such as product details, booking slots, registration fields, or member access.
- Edit safe copy, layout, media, and section settings.
- Avoid deleting required dynamic blocks unless you know how the plugin uses them.
- Preview the page and complete a test action.
- Publish after confirming the plugin record and page still match.
Ask Faster AI
- Review this plugin page and tell me which parts are safe to edit as copy and which depend on plugin data.
- Update the page copy for this booking service but do not change availability, payment, or confirmation settings.
- Create a launch review checklist for this plugin page before publishing.
Review before saving or publishing
- Test the real customer action: booking, checkout, registration, access, or form submission.
- Confirm dynamic data still displays correctly after design edits.
- Review mobile layout and placeholder media.
Common issues and fixes
- If data disappears, restore the required plugin block or reconnect the record.
- If checkout or booking stops, review the plugin settings before editing more page design.
- If a public URL changes, check links from campaigns, posts, and navigation.
Use it in daily operations
- Pair page edits with plugin record review.
- Keep screenshots of the intended public flow for later comparison.
- Use AI for review checklists, not blind approval of payment or access changes.
Team handoff
- Write down what changed, who owns the next review, and which page, customer record, campaign, or plugin record should be checked next.
- If the work affects customers, include the public URL, test result, and any unresolved placeholder media in the handoff note.
- When Faster AI helped prepare the change, ask it to summarize the draft and review checklist so a teammate can approve the work without retracing every click.
Versioned workspace model
For why plugin page edits should move through the same versioned review flow as the rest of the workspace, read the versioned workspace article. Why Every Faster Workspace Is a Git Repo.
Connected workflows
Placeholder media
- Screenshot placeholder: add an annotated screenshot of edit plugin pages safely with private customer, payment, and workspace details blurred.
- Video placeholder: add a short walkthrough that shows the manual path, the Faster AI prompt, and the review step before anything goes live.