Your site, one prompt away
from the next change.

Create a CMS collection

Set up a repeatable content type with the fields you need.

I want a new CMS collection for [collection name] on my FNJ site.

Use my connected FNJ MCP. Call list_sites, help me choose the site if needed, then call get_site and list_collections. Check whether a collection with this purpose already exists before creating one.

Create a collection with fields for [list the fields and types, for example: Title — text, Summary — richtext, Cover image — image, Published date — date]. Ask me only for missing field decisions that would change the structure. Use create_collection, then list_collections to verify the name and field keys. Give me the collection ID and a short example of the values an item will need.

Do not claim that creating a collection automatically creates public pages. If I need an item page or a dynamic listing, explain the separate CMS page setup in FNJ and help me do that next. Do not publish without my approval.

Collection creation stores content; public CMS routes need their own setup.

Add a CMS page

Plan a collection listing or an individual item page.

Help me add a page for my [collection name] CMS content at [desired URL] on my FNJ site.

Use my connected FNJ MCP to call list_sites, get_site, list_collections and list_items. Check whether the collection already publishes individual pages (publishesPages and routePrefix in the collection result). Tell me which route already exists and which part is missing.

If I want a regular page, use create_page by copying the closest existing route, then use get_page_outline, get_page_text and add_section to add a clear [listing or featured content] section. Use actual item data only after checking it; do not invent content. Preview the draft and tell me if this page is a static snapshot of CMS items.

If I want a dynamic page for every CMS item, do not pretend create_page or create_collection sets that up. Guide me through the collection's page-template and route setup in the FNJ editor, or tell me exactly what is unavailable through MCP. Ask me before publishing, then verify the public route after publication.

A copied page is static; per-item CMS routes require a collection page template.

Add a CMS item

Put a post, testimonial, project, or team member into a collection.

Add a new [content type] to the [collection name] collection on my FNJ site using my connected FNJ MCP.

The content is: [paste the title, body, image URL, date, and any other details here].

First call list_sites, get_site, list_collections and list_items. Match the collection and its exact field keys, and check for a duplicate item. If information required by a field is missing, ask me for it instead of inventing it. Use create_item with draft: true unless I explicitly ask for immediate publication. Read the resulting item back and show me its slug and field values. Tell me whether this collection publishes a page per item. Ask before publishing the site.

Create a new page

Start from an existing page so the site keeps its look.

Create a new [page purpose] page at [route, for example /about] on my FNJ site.

Use my connected FNJ MCP. Call list_sites and get_site, then inspect the closest existing page with get_page_outline and get_page_text. Use create_page with that existing route as fromRoute so the new page keeps the site's header, footer, fonts and styling.

Adapt the copied page for this purpose with edit_text, add_section and set_style where appropriate. Use only the copy and assets I provide; ask for missing details. Inspect the result on desktop and mobile if you have preview access. Tell me which parts are still inherited from the source page. Leave it as a draft and ask before publishing.

Rewrite page copy

Change words without disturbing the layout.

Improve the copy on [page route] of my FNJ site for [audience and goal]. Keep the current layout and meaning of any factual claims.

Use my connected FNJ MCP. Call list_sites, get_site and get_page_text for the exact route. Show me a concise before-and-after plan for the headline, supporting text and CTA. Use edit_text with the exact current text from get_page_text; use page scope unless I explicitly want a sitewide change. Do not change prices, dates, guarantees or claims without my approval. Read the page text again to verify the draft. Ask before publishing.

Add a new section

Add a call to action, FAQ, benefits, or another content block.

Add a [section type] section to [page route] on my FNJ site, near [existing section]. The content should say [content and CTA].

Use my connected FNJ MCP. Call list_sites, get_site and get_page_outline, and inspect nearby copy with get_page_text. Find a reliable anchor that appears at the needed breakpoints. Use add_section with semantic HTML and inline styles, following the site's existing type, colours and spacing. Use a stable sectionId so revisions replace the same block. Check desktop and mobile if preview is available, and report any layout issue. Leave the change in draft and ask before publishing.

Change footer links

Update destinations as well as labels, with a real URL check.

Update the footer links on my FNJ site as follows:
[old link label and URL] → [new link label and URL]
[add more changes here]

Use my connected FNJ MCP to identify the site and inspect its pages and footer. Verify each destination URL and check desktop and mobile footers.

If this is an FNJ Studio site, use the Studio page context and batch_edit_design only if the footer links are editable nodes with href values. If this is a converted site, FNJ MCP can edit link text but cannot directly replace an existing link's href. Do not call edit_text and claim the destination changed. If I only need an added footer link, you may use get_page_outline and add_section with a sitewide footer anchor. For replacing an existing destination, use an authorized source-code editor or the FNJ editor if it exposes that control; otherwise tell me exactly which URL still needs manual editing. Ask before publishing, then click each changed link on the live site to verify it.

On converted sites, MCP cannot directly change an existing href.

Update a CMS item

Revise an existing post, project, or testimonial without duplicating it.

Update the [item title or slug] item in my [collection name] collection. Change [fields and new values]; keep every other field as it is.

Use my connected FNJ MCP. Call list_sites, get_site, list_collections and list_items to identify the exact item and field keys. If more than one item matches, ask me which one. Show me the current values and the proposed changes before writing. Use update_item with only the fields I named, then read the item back to verify it. Tell me whether the collection publishes item pages and whether the item is a draft. Ask before publishing the site.

Add several CMS items

Turn a supplied content list into drafts in the right collection.

Add these [posts/projects/team members] as drafts to the [collection name] collection on my FNJ site:
[paste the complete items here]

Use my connected FNJ MCP. Call list_sites, get_site, list_collections and list_items first. Map each supplied value to the collection's actual field keys. Check existing titles and slugs to avoid duplicates. Ask me about missing required fields rather than inventing copy, dates, photos or people. Create each new item with create_item and draft: true. Read the created items back and give me a short list of their titles, slugs and any entries you skipped. Do not make them live or publish the site without my approval.

Build a contact page

Add a clear route for people to reach you.

Create a contact page at [route] on my FNJ site. Use these real contact details: [email, social links, business hours, and any address I want public].

Use my connected FNJ MCP to call list_sites and get_site, then choose the closest existing page as the source for create_page. Inspect its structure with get_page_outline and get_page_text. Replace copied content with my contact details and add a simple contact section with add_section if needed. Do not invent an address or publish a form that has no working submission handler; an email link is fine. Check the page on desktop and mobile if preview access is available. Ask before publishing.

Add an FAQ section

Answer real customer questions on an existing page.

Add an FAQ section to [page route] on my FNJ site using these questions and answers:
[paste approved questions and answers]

Use my connected FNJ MCP. Call list_sites, get_site and get_page_outline; read the nearby content with get_page_text. Use add_section with semantic headings and a list of question-and-answer pairs, matching the page's style with inline CSS. Use a stable sectionId so later edits replace this section. Do not invent policies, guarantees or product capabilities. Check the draft at mobile and desktop sizes if possible, then ask before publishing.

Add testimonials

Place approved quotes in a section that fits the site.

Add a testimonial section to [page route] on my FNJ site. Use only these approved quotes, names and roles:
[paste the quotes and attribution here]

Use my connected FNJ MCP. Call list_sites, get_site, get_page_outline and get_page_text to find a suitable position. Use add_section with semantic HTML, legible quotation marks and responsive inline styles. Do not invent people, job titles, company logos, star ratings or results. Check that each quote and name matches what I supplied, review desktop and mobile if possible, and ask before publishing.

Add a pricing block

Present your actual offer and its main details clearly.

Add a pricing block to [page route] on my FNJ site using this approved offer: [price, billing period, features, eligibility, and destination URL].

Use my connected FNJ MCP. Call list_sites, get_site, get_page_outline and get_page_text. Find an appropriate place and use add_section with a clear price, feature list and CTA link. Keep the site's visual style. Do not invent a discount, comparison price, deadline, guarantee or feature. Verify the CTA's actual destination and check the draft on desktop and mobile if you have browser access. Ask before publishing.

Restyle a section

Adjust spacing, colour, type, or borders while keeping the content.

Improve the styling of the [section name] on [page route]. I want [specific change, for example more spacing or a darker background]. Keep its content and links intact.

Use my connected FNJ MCP. Call list_sites, get_site and get_page_outline to identify the exact element. Read nearby copy with get_page_text if needed. Use set_style with the smallest set of CSS properties that achieves the request. Start with page scope; use site scope only if I want the change everywhere. Check the draft on desktop and mobile and report any breakpoint differences. Ask before publishing.

Fix mobile spacing

Tighten a layout that feels crowded or too wide on phones.

The [section or page] on my FNJ site looks wrong on a phone: [describe the issue]. Please improve it without changing the desktop design unnecessarily.

Use my connected FNJ MCP and, if available, a mobile browser preview. Call list_sites, get_site and get_page_outline to inspect the page. Converted sites may have separate desktop, tablet and phone elements; identify the affected copy before using set_style. Do not apply a broad sitewide style if it would change other breakpoints. Make the smallest draft change, inspect the phone and desktop results, and explain any issue that MCP cannot target safely. Ask before publishing.

Rename a navigation link

Change a menu label while keeping its destination clear.

Rename the [current menu label] link to [new label] on my FNJ site. Its destination should remain [expected URL].

Use my connected FNJ MCP. Call list_sites, get_site and get_page_text on a page where the menu appears. Use edit_text with the exact current text and site scope if the same menu is shared across pages. Then verify the visible label on more than one route. edit_text changes words, not href values: inspect the actual link destination with a browser if available, and tell me if it differs from the URL I expect. Do not claim that a destination changed unless you verified it. Ask before publishing.

Add a footer link

Add a new destination without changing existing footer links.

Add a link labeled [label] to [full URL] in the footer of my FNJ site.

Use my connected FNJ MCP. Call list_sites, get_site and get_page_outline. Check whether the footer already contains this link. For a converted site, use add_section to append a small semantic link block inside the footer, with site scope and a stable sectionId. Converted pages may have separate footers for each breakpoint, so ensure the link appears on phone and desktop. For a Studio site, use its design tools if the footer is an editable component. Do not claim you replaced an existing href; this request is to add a link. Verify the URL, then ask before publishing.

Review the draft

Find unfinished edits and obvious issues before anything goes live.

Review the current draft of my FNJ site before I publish it.

Use my connected FNJ MCP. Call list_sites and get_site. Check the page list, CMS collections and pendingEdits. For a converted site, inspect important routes with get_page_text and get_page_outline. For a Studio site, use get_site_context and audit_design. If you have browser access, inspect home, navigation, key CTAs and mobile layout in the preview. Give me a short list of findings, separate confirmed problems from things you could not verify, and suggest fixes. Do not publish or make speculative edits.

Publish reviewed changes

Ship the approved draft to your connected hosting account.

Help me publish the changes I have reviewed on my FNJ site.

Use my connected FNJ MCP to call list_sites and get_site. Show me the site name, live URL, pending edit count and whether canPublish is true. Confirm the saved deployment target in the FNJ dashboard before calling publish; do not risk deploying to an unexpected provider. Summarize what will go live and ask me for final approval. If I approve, call publish once, open the returned public URL and verify the changed pages and links. If there is no connected deployment or your MCP grant is read only, tell me the exact step I need to complete. Do not report success until the public site loads.

Check the live site

Verify what visitors can actually see after publishing.

Check the live version of my FNJ site at [public URL] after the latest publish.

Use my connected FNJ MCP to call list_sites and get_site so you can confirm the site and its live URL. If you have browser access, open the public URL, follow the main navigation, test important CTA destinations and inspect key routes on desktop and mobile. Compare the visible copy against the changes I requested: [list expected changes]. Report the exact URLs that work, any broken route or visual problem, and anything you could not test. Do not modify the site or say it is verified based only on the publish tool's response.