Overview

The FusionETA guides page is powered by the guides-skill — a Cowork skill that handles everything from writing the individual guide page to updating the guides listing and deploying both files to the live server. You do not need to write HTML, upload files, or touch FTP manually.

This guide explains exactly what to prepare, what happens automatically, and what decisions (like category) you may need to confirm.

🤖

How to trigger it

Open a Cowork session and tell Claude to "add a new guide" — then provide the details below. Claude will handle the rest: it reads the skill, builds the pages, updates the data file, and deploys everything live.

Example — See It In Action

Here's what an actual request looks like, and exactly what Claude does in response.

Cowork — FusionETA

Simon

Add a new guide to the FusionETA guides page titled "How to Add a New Guide to the FusionETA Website". This guide explains how to use the guides-skill to publish a new how-to guide — covering how to prepare your content, what fields are needed (title, description, category, tags, slug), how category auto-detection works, and what gets built and deployed automatically. It's aimed at the internal FusionETA team. Status: published.

Claude

📂 Category detected: Development — this guide is about the site's internal publishing workflow, not Bitrix24 or Xero configuration. 🔗 Slug: add-new-guide

✅ Reading guides-skill and fusioneta-website skill…

✅ Building guide page → web/guides/add-new-guide/index.html

✅ Inserting card into guides index (newest-first)

✅ Updating published count: 1 → 2

✅ Deploying via FTP — guide page + index

✅ Verified: HTTP 200 on both URLs

🚀 Live at fusioneta.com.my/web/guides/add-new-guide/

⚡

That's all it takes

One message from you. Claude reads the skill, builds the full HTML page, updates the listing, deploys both files over FTP, and confirms with a live URL — all in a single session, no further input needed.

Step 1 — Prepare Your Content

Before triggering the guides-skill, gather the following. The more detail you provide upfront, the less back-and-forth is needed.

Write the guide steps

Have the actual how-to content ready — the problem being solved, the step-by-step instructions, any code snippets, and any caveats or warnings. Claude will write the formatted HTML page from this, but the accuracy of the content is yours to provide.

Decide on a title

The title appears as the guide card heading on the listing page and as the <h1> on the guide page. Keep it descriptive and action-oriented — e.g. "Disable File Attachments in Bitrix24 On-Premise Chat" rather than just "File Attachments".

Write a 1–2 sentence description

This appears on the guide card in the listing. It should summarise what the guide achieves and who it's for. Keep it under 160 characters if possible — it also doubles as the SEO meta description.

Step 2 — Required Fields

When you tell Claude to add a guide, it will need the following information. Items marked Required must be provided; Optional items have sensible defaults.

Field	Required?	Notes
title	Required	Full guide title, shown as the card heading and page <h1>
description	Required	1–2 sentence summary shown on the card and used as SEO meta description
guide content	Required	The actual steps, context, and code — Claude builds the page from this
category	Auto-detected	Bitrix24, Xero, or Development — see Section 3. Claude detects from the title/description and confirms if ambiguous
slug	Auto-generated	URL-safe identifier, e.g. bitrix24-disable-file-attachment. Claude generates from the title; you can override
tags	Optional	Short metadata labels shown on the card, e.g. 5 min read, On-Premise, Xero Cloud
status	Optional	Defaults to published. Set to coming-soon to add a placeholder card without a live page
emoji	Optional	Single emoji for the card icon. Claude picks one based on the topic if not provided

Step 3 — Category Auto-Detection

Every guide belongs to exactly one of three categories. Claude auto-detects this from the title and description using keyword signals:

Bitrix24

Bitrix24, CRM, portal
on-premise, init.php
chat, deal, pipeline
automation, module
intranet, bitrix

Xero

Xero, invoice, accounting
P&L, tracking category
bank reconciliation
FX gains, GST, tax
chart of accounts

Development

REST API, webhook
integration, connect
middleware, JSON
endpoint, SDK
script, code (as primary topic)

⚠️

Tie-breaking rule

If a guide spans two categories (e.g. "Connecting Bitrix24 to Xero via REST API"), the primary subject wins. If the guide is about building an integration, it's Development. If it's about configuring a Bitrix24 on-premise feature using PHP, it's Bitrix24 — even though code is involved.

When Claude is confident in the category, it states it and proceeds. When it's ambiguous, it proposes its best guess and asks you to confirm before continuing. You can also state the category upfront to skip detection entirely.

Bitrix24 Xero Development

Step 4 — What Gets Built and Deployed Automatically

Once you've confirmed the fields and category, Claude runs the full publishing pipeline without any further input from you. Here is what happens:

📄

Guide Page Built

A full HTML page is created at web/guides/[slug]/index.html with hero, steps, FAQ, sidebar, and CTA sections

📋

Listing Updated

The guides index at web/guides/index.html gets a new card inserted at the top (newest-first), and the published count is incremented

🗃️

Data File Updated

The source-of-truth file guides-data.md is updated with the new entry so future sessions stay in sync

🚀

Deployed via FTP

Both files are pushed live to the server using the cpanel-deploy skill — the guide page to its own subfolder, the index to /guides/

✅

Live Check Run

Claude verifies both URLs return HTTP 200 before reporting success, so you always know the deployment worked

🔍

GSC Submission

For published guides, the new URL is submitted to Google Search Console for indexing via URL Inspection

💡

Coming-soon guides skip steps 1, 4, 5, and 6

If the status is coming-soon, only the listing card is added — no individual guide page is built and no deployment occurs for the guide itself. Only the guides index is deployed.

SEO — What's Handled for You

Every published guide page is built with full SEO coverage out of the box. You don't need to think about any of this — it's all in the template:

Title tags and meta descriptions are generated from your title and description fields. Open Graph tags (for social sharing), Twitter Card tags, canonical URLs, and structured data (HowTo or TechArticle schema) are included automatically. Heading hierarchy, image alt text, and mobile-responsive layout are part of every guide page by default.

Frequently Asked Questions

Can I add a guide without writing the full HTML myself? ▾

Yes — that's the whole point. Just describe the guide content in plain language or paste in your notes, and Claude handles the HTML, styling, SEO, and deployment. You only need to approve the category if it's ambiguous.

What if I want to change the slug/URL later? ▾

Changing a slug after publication breaks any existing external links. Claude will always ask you to confirm before making a slug change on a live guide. If you need to move a URL, consider adding a redirect from the old path to the new one.

Can I add a guide in "coming soon" status first, then publish it later? ▾

Yes. Tell Claude to add it as coming-soon — a placeholder card appears in the listing. When you're ready to publish, tell Claude to "publish the [title] guide" and it will build the full guide page, update the card, increment the count, and deploy everything.

What happens to the existing guide cards when I add a new one? ▾

The new published card is inserted at the top of the grid (newest-first), pushing existing published cards down. Coming-soon cards always stay below all published cards. The filter tabs continue to work correctly based on data-category attributes.

Can I add guides in a category other than Bitrix24, Xero, or Development? ▾

Not currently — the filter tabs and category system support only these three. If a new category is needed, the guides index page, filter bar, and card templates all need updating. Raise this as a separate task.

How do I update or correct a guide after it's published? ▾

Tell Claude which guide to edit and what to change — e.g. "update the description on the file attachment guide" or "fix the code in step 2 of the Xero tracking categories guide". Claude will fetch the current page, make the change, and redeploy.

✅

Ready to publish a guide?

Open a Cowork session and say: "Add a new guide titled [your title]" — then provide your content. Claude handles the rest. For questions about the website or deployment, get in touch.

How to Add a New Guide to the FusionETA Website