VIXNODE GUIDES · CHATGPT PLUGINS

The Complete Guide to VIXNODE Plugin: Build and Manage Websites with AI

From building a website to everyday maintenance: 10 practical scenarios, copy-ready prompts, and a quick reference to 43 tools.

VIXNODE and ChatGPT working together to build and publish websites

Connect your VIXNODE account to plan websites, create and edit pages, manage assets, configure custom domains, and review versions and SEO using natural language. AI selects the appropriate tools; you do not need to memorize tool names or enter project IDs yourself.

Ordinary page creation and editing starts with a preview so you can review the content, target page, and publishing options before execution. Saving a draft and publishing are separate actions: a draft update does not mean visitors can see it, while publishing replaces the live version with the latest saved content.

Open VIXNODE Plugin

How to connect

  1. Open the VIXNODE Plugin link in this article.
  2. Select Connect, sign in, and authorize your VIXNODE account.
  3. Return to the conversation and describe the website, page, and goal.
  4. Confirm that AI has found the correct project before reviewing a preview or proposed changes.

After connecting for the first time, try: “Check the connected VIXNODE account and list the websites I can manage so I can choose one.” Once you select a website, continue with the scenarios below.

From building a website to everyday maintenance

The following examples follow a “Bread Workshop” website through its lifecycle. Each prompt also works independently; replace the website name and details with your own real information. For actions that require confirmation, wait until AI shows the content or preview before approving it. Do not paste advance approval for content you have not reviewed.

When to use: When connecting for the first time, managing several websites, or checking which account is active.

Check the connected VIXNODE account, plan, and quotas, then list the websites I can manage.Open “Bread Workshop” and list its pages and current domain settings. If more than one project has that name, let me choose first.

If the wrong account is connected, say: “I want to use a different VIXNODE account. Help me reconnect.” If you cannot find a page, say: “Search across my websites for ‘Course Introduction’ and list matching pages so I can choose.”

Next step: Confirm the project before preparing content. If you do not have a website yet, continue with the next scenario.

Quick reference: 43 tools

Use this reference to find the tools for the scenarios above. Prompts are grouped by scenario rather than repeated in every tool row. The count reflects the catalog confirmed for this update; the current connected definitions determine which tools are available.

Accounts and website projects (6 tools)

ToolPurpose
get_account_infoView the account, plan, and quotas
switch_accountReconnect and switch accounts
get_website_projectsList website projects
project_infoView a website’s settings and domain information
create_projectCreate a website project
modify_projectChange general website settings without editing or publishing pages

References and documentation (3 tools)

ToolPurpose
get_reference_themesBrowse reference themes, styles, and colors
get_url_htmlRead HTML from a reference URL
get_docsLook up guides, tool descriptions, and examples

Images, videos, and files (12 tools)

ToolPurpose
get_photo_galleryOpen the image library and select images
get_imageRetrieve an image or thumbnail
upload_imageUpload an image
chunk_upload_imageUpload an image in chunks
get_video_libraryView the video library
get_videoRetrieve a video or thumbnail
upload_videoUpload a video
chunk_upload_videoUpload a video in chunks
get_file_libraryView the file library
get_fileRetrieve a private resource or public file
upload_fileUpload a general file
chunk_upload_fileUpload a general file in chunks

Prefer the VIXNODE platform upload interface for large assets, then give AI the actual paths. Sending large Base64 payloads through a conversation can consume more usage; chunked uploads still require complete data and must never use invented content.

Private uploads are preferred for ordinary web resource files. Public files are live website resources; uploading to the same path can overwrite existing public content. Confirm the project and location first.

Creating, editing, and publishing pages (10 tools)

ToolPurpose
get_project_pagesList pages in a website
get_all_project_pagesSearch pages across websites
create_project_page_previewOrdinary creation: preview and confirm before creating
modify_project_page_previewOrdinary editing: read current content, preview, and confirm before updating
create_project_pageExceptional direct creation after separate explicit confirmation; does not publish automatically
modify_project_pageExceptional direct editing after separate explicit confirmation; does not publish automatically
publish_project_pageAfter confirmation, make the page public and publish its latest saved version
publish_projectRepublish currently public pages; skip private pages
create_web_pageCompatibility creation tool for existing workflows
modify_web_pageCompatibility editing and publishing tool for existing workflows

Ordinary preview workflows select public access and publishing after save by default. For a draft, explicitly request “Do not publish” or “Make the page private” and check the options before confirming. Direct tools are exceptional workflows; an initial editing request does not itself approve immediate writing or publication.

SEO (3 tools)

ToolPurpose
get_project_page_seo_settingView the title, description, and structured data
get_seo_data_structure_sampleGet examples such as Article, FAQPage, and Product
modify_project_page_seo_settingAfter confirmation, update and publish SEO settings

Custom domains (4 tools)

ToolPurpose
validate_project_domainValidate plan eligibility and DNS A/TXT records without attaching a domain
configure_project_domainConfigure a domain and revalidate plan eligibility and DNS before execution
get_project_domain_statusCheck and synchronize the current domain and SSL status
remove_project_domainAfter confirmation, remove the domain binding and routing and clear the project’s virtual path

Successful validation does not mean the domain is attached, and attachment does not guarantee immediate SSL activation. Replacing or removing a domain affects its current URL. Replacement removes the old binding first; a later configuration failure can leave the old URL unavailable. Review the impact first. Domain tools do not publish pages.

Content and versions (5 tools)

ToolPurpose
get_project_page_htmlRead the latest saved design content
get_published_page_htmlRead the live published content
get_project_page_html_historyView historical versions
get_project_page_html_by_versionRead a selected historical version
get_project_page_html_compare_by_versionCompare a selected version with its previous version

Reading a historical version does not restore a page automatically. Review the content to apply and whether it should be published.

Download VIXNODE website resources

Add these references to a ChatGPT Project or provide them as conversation sources to improve stability, layout accuracy, and visual consistency.

VIXNODE Page Creation Instructions

Guidance for page types, layout relationships, identifiers, previews, and confirmation.

Download page instructions

AI Website Art Direction Instructions

Visual direction, brand character, and art-direction guidance for more consistent design results.

Download art direction

If a reference conflicts with the user’s current request, follow the user’s newest and clearest instruction. Always review the target website, page, layout, content, and scope before applying changes.

ChatGPT Project Context

This example can be added to ChatGPT Project instructions or supplied as project context in a conversation so that future VIXNODE work follows consistent content, visual, image, and linking rules.

# Default Plugin

@VIXNODE

# Starting Project

@VIXNODE `Bread-Workshop`

# Project Theme

Build the website around an artisan bread workshop. Introduce handmade bread, baking classes, recipes, ingredient knowledge, and workshop events.

# Website Goals

1. Communicate the workshop’s brand philosophy and commitment to craftsmanship.
2. Introduce classes, events, and participation details.
3. Share practical bread recipes and baking knowledge.
4. Establish a warm, professional, and approachable brand image.
5. Guide visitors to explore classes, book an experience, or contact the workshop.

# Primary Audiences

* Beginners interested in handmade bread
* Baking enthusiasts who want to improve their skills
* Visitors looking for parent-child experiences or group activities
* Readers interested in ingredients, fermentation, and bread-making techniques

# Content Categories

| Category | Content Direction |
| --- | --- |
| About the Workshop | Brand story, teaching philosophy, instructors, and studio |
| Baking Classes | Course content, difficulty, duration, and suitable participants |
| Bread Recipes | Ingredients, quantities, steps, and practical tips |
| Baking Knowledge | Flour, yeast, fermentation, tools, and storage |
| Events | Trial sessions, family classes, and private group workshops |
| Workshop Journal | Class records, student work, and everyday stories |

# Brand and Visual Direction

Brand personality:

* Warm and natural
* Honest and handmade
* Simple and thoughtful
* Professional yet approachable
* Rooted in everyday life

Draw visual inspiration from flour, dough, baked crust, wooden worktables, linen, and traditional baking tools.

Use flour white, wheat beige, bread golden brown, deep wood brown, with small accents of sage green or brick red.

Avoid arbitrary blue-purple technology gradients, neon effects, glassmorphism, excessive rounded cards, or a generic AI-generated website look.

# Content Writing Principles

1. Use a natural, friendly, and easy-to-understand tone.
2. Explain professional baking terms before using them.
3. Recipes must clearly list ingredients, quantities, timing, steps, and precautions.
4. Course pages must explain content, difficulty, duration, and suitable participants.
5. Prioritize specific and useful information over empty promotional language.
6. Do not invent instructors, prices, addresses, event dates, certificates, or awards.
7. When essential information is missing, ask the user or leave clearly labeled placeholders.
8. Avoid unnecessary duplication of existing content.

# Images and Hero Visuals

1. Focus on finished bread, the making process, natural ingredients, baking tools, and the workshop space.
2. Keep the style natural, warm, bright, and authentically handmade.
3. The default hero-image size is `1672 × 941 px`.
4. Ingredients, tools, and production methods shown in images must be realistic.
5. When modifying a page and adding a hero image, add `data-meta="true"` to the `<img>` node.
6. VIXNODE image paths use the format `/API/GetImage/...`.
7. Every image must have an accurate `alt` description.

# Link and File Rules

1. Use relative paths for internal website links.
2. Link only to pages that actually exist.
3. Specify `virtualPath` and `fileName` separately when creating a page. For example, use `virtualPath="classes"` and `fileName="beginner-bread"`; do not put a full path or `.html` in `fileName`.
4. When modifying a page, preserve its current filename and page relationships.
5. Never guess or invent unknown project IDs, page IDs, Layout IDs, or Placeholder IDs.

Internal-link examples:

* `classes/index.html`
* `recipes/sourdough-bread.html`
* `../index.html`
* `../classes/beginner-bread.html`

# Working Rules

1. Preview page creation and editing before execution. Review the target, content, public status, and publishing options.
2. Explicitly request no publication when only a draft is needed. Read the latest HTML before editing.
3. Explain the impact before changing a domain, public resource, or shared layout.
4. Use public URLs returned by tools instead of guessing them. Existing `.html` links may be retained.

# Reference Guidelines

When creating or modifying VIXNODE pages, follow:

https://news.vixnode.com/vixnode-page-creation-instructions.md

For website visual design, consult the project resource:

`AI-WEBSITE-ART-DIRECTION-INSTRUCTIONS.md`

If a reference guideline conflicts with the user’s current request, follow the user’s newest and clearest instruction.

Before execution

  • Confirm the website and page.
  • Read the latest content and preserve existing layout relationships.
  • Review the preview and ensure public and publishing options match your intent.
  • Check whether live content or public files could be overwritten, or an existing domain could stop working.
  • Approve the SEO title, description, and JSON-LD.
  • Distinguish completed, queued, and publishing results; do not claim completion while processing continues.