diff --git a/README.md b/README.md index 29c4ef2..e1340c9 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,8 @@ Documentation site for [Kite](https://kite.ai), built with [Docusaurus](https://docusaurus.io/). +Kite is your AI marketer in Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Most AIs wait for instructions. Kite finds what needs doing and does it. Building and hosting your website is one of the ways it executes that strategy. + ## Development ```bash @@ -20,7 +22,7 @@ npm run build Search is powered by the offline [`@easyops-cn/docusaurus-search-local`](https://github.com/easyops-cn/docusaurus-search-local) plugin, which builds the index from Markdown at build time. The index is **only -generated during `npm run build`, not during `npm start`** — so to test search +generated during `npm run build`, not during `npm start`**, so to test search locally, run a production build and serve it: ```bash diff --git a/website/docs/account/README.md b/website/docs/account/README.md index f0835f3..8655c1c 100644 --- a/website/docs/account/README.md +++ b/website/docs/account/README.md @@ -1,30 +1,31 @@ --- title: Account & Settings -description: Manage your Kite account, sign in, and control your data — including deleting your account or exporting your site. +description: Sign in to Kite, understand team roles, export your website's code, and request account deletion. --- # Account & Settings -Everything about your Kite account lives here: creating an account, signing in, and managing your data. Whether you're just getting started or you want to delete your account or get a copy of your site, this section walks you through it. +Everything about your Kite account lives here: signing in, who can do what on your team, getting a copy of your website, and deleting your account. ## What you can do here -- **Create an account and sign in** — set up your login and get back in when something goes wrong. -- **Control your data** — delete your account and data, or request a copy of your site. -- **Manage billing separately** — if you only want to stop paying (but keep your account), that's handled under your subscription settings. +- **Sign in** with Google or an email one-time code, and link your Slack identity to your Kite team. +- **Understand roles.** Owners manage billing; admins manage the team; members use Kite and the editor. +- **Export your site's code** as a ZIP from your site's Settings, on any plan. +- **Request account deletion** through support, after canceling any subscription. -:::tip Account vs. subscription -Deleting your account and canceling your subscription are two different things. Deleting your account removes your account and data. Canceling your subscription just stops billing — your account stays. See [Manage Your Subscription](/pricing-credits/manage-subscription) if you only want to stop paying. +:::tip Account versus subscription +Deleting your account and canceling your subscription are two different things. Canceling stops billing and keeps your account. Deleting removes your account, your personal teams, and their websites. See [Manage Your Subscription](/pricing-credits/manage-subscription) if you only want to stop paying. ::: ## In this section -- [Login & Sign Up](/account/login-and-signup) — create an account, sign in, and fix common login problems. -- [Delete Your Account & Data](/account/delete-account) — how to remove your account and data, and what that means for billing. -- [Export or Download Your Site](/account/export-your-site) — what you can get a copy of today, and how to request it. +- [Login & Sign Up](/account/login-and-signup): sign in, connect your Slack identity, and fix common login problems. +- [Delete Your Account & Data](/account/delete-account): how to request deletion, what it removes, and why you cancel first. +- [Export or Download Your Site](/account/export-your-site): download your website's source code as a ZIP. ## Related help -- [Pricing & Credits](/pricing-credits/) — plans, trials, credits, and billing. -- [Publishing](/publishing/) — get your site live once your account is set up. -- [Troubleshooting](/troubleshooting/) — fixes for editor and preview issues. +- [Team access](/slack/team-access): roles and who can approve work. +- [Pricing & Credits](/pricing-credits/): plans, credits, and billing. +- [Troubleshooting](/troubleshooting/): fixes for editor and preview issues. diff --git a/website/docs/account/delete-account.md b/website/docs/account/delete-account.md index c4332c7..b08e1bd 100644 --- a/website/docs/account/delete-account.md +++ b/website/docs/account/delete-account.md @@ -1,68 +1,55 @@ --- title: Delete Your Account & Data -description: How to request deletion of your Kite account and data, how it differs from canceling your subscription, and what to expect about refunds. +description: How to request deletion of your Kite account, what it removes, why you must cancel any subscription first, and what happens to shared teams. --- # Delete Your Account & Data If you want to remove your Kite account and the data tied to it, this guide explains how to request it and what happens afterward. It also clears up a common point of confusion: deleting your account is not the same as canceling your subscription. -:::caution Deleting is permanent -Deleting your account removes your account and its data, including your sites. This generally can't be undone. If you only want to stop paying, cancel your subscription instead (see below). +:::caution Deleting is permanent and immediate +Deletion removes your sign-in identity right away, and it cannot be undone. It also deletes your personal teams and every website in them, which takes those published sites offline. ::: -## Account deletion vs. canceling your subscription +## Account deletion versus canceling your subscription -These two actions are easy to mix up, but they do very different things: +- **Delete your account** removes your identity, your personal teams, and their websites. You are leaving Kite entirely. +- **Cancel your subscription** stops future billing and keeps your account and sites in place. See [Manage Your Subscription](/pricing-credits/manage-subscription). -- **Delete your account** — removes your account and your data, including your sites. You're choosing to leave Kite entirely. -- **Cancel your subscription** — stops future billing, but your account and sites stay in place. You're still a Kite user; you've just stopped (or changed) your paid plan. +If your goal is simply to stop being charged, cancel your subscription instead. -If your goal is simply to stop being charged, you probably want to **cancel your subscription**, not delete your account. See [Manage Your Subscription](/pricing-credits/manage-subscription). - -## How to request account and data deletion +## Before you delete - +1. **Cancel any active subscription first.** Deletion is refused while a personal team still has an active paid plan. See [Manage Your Subscription](/pricing-credits/manage-subscription). +2. **Export any site you want to keep.** Download the source code from each site's Settings. See [Export or Download Your Site](/account/export-your-site). +3. **Disconnect any custom domain** you want to use elsewhere. See [Custom Domains](/custom-domains/). -1. First decide whether you really want deletion or just want to stop billing (see the comparison above). -2. If you're sure you want everything removed, request account and data deletion. -3. Provide the email address on your account so the team can locate and confirm it. -4. Confirm the request when asked, since deletion is permanent. +## How to request deletion -:::note -We're confirming whether account deletion is fully self-serve from your settings or handled as a support request. If you don't see a clear delete option in your account, contact support and ask them to delete your account and data. -::: +Account deletion is handled by the Kite team rather than by a button in your settings. -## Before you delete +1. Open **Chat with us** in Kite (or on kite.ai) and ask for your account and data to be deleted. +2. Give the email address you sign in with so the team can locate the account. +3. Confirm the request when asked. Once confirmed, deletion is immediate. -A few things worth doing first: +## What happens to shared teams -- **Cancel your subscription** if you haven't already, so billing stops cleanly. See [Manage Your Subscription](/pricing-credits/manage-subscription). -- **Save anything you need.** Once your account is deleted, your sites and data go with it. If you want a copy of your site, see [Export or Download Your Site](/account/export-your-site) first. -- **Disconnect or move any custom domain** you want to keep using elsewhere. See [Custom Domains](/custom-domains/). +If you belong to a team with other owners, that team is preserved. Your websites in it are reassigned to another owner, and the team carries on without you. ## Refunds - - -If you've paid for a plan or credits, deleting your account doesn't automatically guarantee a refund. Refund eligibility depends on Kite's billing policy, which we're confirming. If you believe you're owed a refund, contact support with your account email and the details of your purchase. +Deleting your account does not by itself trigger a refund. If you believe you are owed one, mention it in the same conversation with support. ## Troubleshooting -### I only wanted to stop paying - -You don't need to delete your account to stop being billed. Cancel your subscription instead — your account and sites stay intact. See [Manage Your Subscription](/pricing-credits/manage-subscription). - -### I can't find a delete option - -Account deletion may be handled by the support team rather than a button in your settings. Contact support, include your account email, and ask them to delete your account and data. +**I only wanted to stop paying.** Cancel your subscription instead. Your account and sites stay intact. -### I deleted by mistake +**Support says deletion was refused.** A personal team still has an active subscription. Cancel it, then ask again. -Because deletion is permanent, recovery may not be possible. Contact support as soon as possible with your account email — but treat deletion as final. +**I deleted by mistake.** Deletion is immediate and cannot be reversed. You can create a new account with the same email, but your previous teams and sites are gone. ## Related help -- [Manage Your Subscription](/pricing-credits/manage-subscription) — cancel billing while keeping your account. -- [Export or Download Your Site](/account/export-your-site) — get a copy before you go. -- [Account & Settings](/account/) — overview of your account and data options. +- [Manage Your Subscription](/pricing-credits/manage-subscription) +- [Export or Download Your Site](/account/export-your-site) +- [Account & Settings](/account/) diff --git a/website/docs/account/export-your-site.md b/website/docs/account/export-your-site.md index 1083d95..24b9195 100644 --- a/website/docs/account/export-your-site.md +++ b/website/docs/account/export-your-site.md @@ -1,55 +1,37 @@ --- title: Export or Download Your Site -description: What you can get a copy of from your Kite site today, the current limits on code export, and how to request it. +description: Download your website's source code as a ZIP from your site's Settings, on any plan, and learn what the export contains. --- # Export or Download Your Site -Want a copy of your site or its code? Here's an honest look at what's possible today on Kite, what isn't, and how to ask for what you need. +You can download your website's source code at any time, on any plan. This page shows where the button is and what you get. -:::note Export is currently a request, not an instant download -Right now, exporting or downloading your site's code is **limited** and handled as a **request** — you may be routed to talk to the team rather than getting an instant self-serve download. The steps below explain how to ask. -::: +## Download your site's code -## What you can and can't get today +1. Open your site in the browser workspace and go to **Settings**. +2. In the **Export** section ("Download your website's source code"), click **Export code**. +3. The first time, a short feedback form appears. Fill it in and the download starts. After that, the button downloads directly. - +Your browser receives a ZIP file named `-frontend.zip`. -What's available may change, but here's the current picture: +## What the export contains -- **You can** keep your site live and hosted on Kite, and you can connect your own custom domain so it's reachable at your address. See [Custom Domains](/custom-domains/). -- **You can** request a copy of your site or its code by contacting the team. -- **You may not** be able to instantly download a full code bundle yourself the way you would from some other tools — full code export/download is limited today and isn't a one-click self-serve feature yet. +The ZIP holds your site's source tree: the pages, components, styles, and content. It leaves out git history, environment files, and build output. A developer can run it or host it anywhere that runs a Next.js site. -If your main goal is to have your site at your own web address, you likely want a **custom domain** rather than a code export. See [Connect a Custom Domain](/custom-domains/connect-a-custom-domain). +## Other ways to get your code -## How to request your site or its code - -1. Decide what you actually need — your live site at your own domain, or a copy of the underlying code. -2. If you need a code copy, **contact the support team** and ask about exporting or downloading your site. -3. Include your account email and the name of the site you're asking about. -4. The team will let you know what's available and walk you through next steps. You may be routed to talk to them directly rather than getting an instant download. - -:::tip Just want it at your own address? -If you don't actually need the raw code and only want your site reachable at your own domain, connecting a custom domain is usually the simpler path. See [Connect a Custom Domain](/custom-domains/connect-a-custom-domain). -::: +- **Sync to GitHub.** Connect a repository from the Integrations page and Kite keeps it in sync with your site both ways. See [Integrations](/forms-integrations/integrations). +- **Just want your own web address?** You do not need to export anything for that. Connect a custom domain and keep your site hosted on Kite. See [Connect a Custom Domain](/custom-domains/connect-a-custom-domain). ## Troubleshooting -### I don't see a download or export button - -That's expected for now — code export/download isn't a one-click self-serve feature yet. Request it by contacting support with your account email and site name. - -### I'm leaving Kite and want my content - -Contact the team to ask what they can provide for your site, and save anything you can before making account changes. If you're also planning to delete your account, get your copy **first** — see [Delete Your Account & Data](/account/delete-account). - -### I just want my site at my own domain +**The download did not start.** Check your browser's download bar and pop-up settings, then click **Export code** again. -You don't need to export anything for that. Connect a custom domain and keep your site hosted on Kite. See [Connect a Custom Domain](/custom-domains/connect-a-custom-domain). +**I'm leaving Kite and want my content.** Export each site you want to keep before you delete your account. See [Delete Your Account & Data](/account/delete-account). ## Related help -- [Custom Domains](/custom-domains/) — point your own address at your Kite site. -- [Delete Your Account & Data](/account/delete-account) — save a copy before you delete. -- [Account & Settings](/account/) — overview of your account and data options. +- [Custom Domains](/custom-domains/) +- [Integrations](/forms-integrations/integrations) +- [Delete Your Account & Data](/account/delete-account) diff --git a/website/docs/account/login-and-signup.md b/website/docs/account/login-and-signup.md index 9570066..c64463a 100644 --- a/website/docs/account/login-and-signup.md +++ b/website/docs/account/login-and-signup.md @@ -1,72 +1,55 @@ --- title: Login & Sign Up -description: Create your Kite account, sign in, and fix common problems like missing verification or password-reset emails. +description: Sign in to Kite with Google or an email one-time code, add Kite to Slack, connect your Slack identity to your team, and fix common sign-in problems. --- # Login & Sign Up -Setting up your Kite account takes just a minute. This guide covers creating an account, signing back in, and what to do when a login or email step doesn't go as planned. +You sign in to Kite with Google or with a one-time code sent to your email. There is no password to remember and no "sign in with Slack." This page covers creating your account, adding Kite to Slack, linking a teammate's Slack identity, and what to do when a sign-in step does not go as planned. -## Create an account +## Create your account and sign in -1. Go to the Kite home page. -2. Select **Sign Up** (or **Get Started**). -3. Enter your email address and choose a password, or sign up with a connected provider if one is offered. -4. Check your inbox for a verification email and select the link inside to confirm your account. -5. Once verified, you'll be signed in and ready to start building. +1. Go to [kite.ai](https://kite.ai) and select **Get started** or **Login**. +2. Choose **Continue with Google**, or enter your email and type the one-time code Kite sends you. +3. You land in the browser workspace, and a 5-day Growth trial starts automatically. See [Plans & Pricing](/pricing-credits/plans-and-trial). -:::caution Verification email didn't work? Don't sign up again -If the verification link fails or seems expired, **don't repeatedly create a new account** — signing up multiple times can create duplicate accounts that are hard to untangle later. Instead, try the link again from the same browser and tab where you signed up, or contact support to sort it out. See [Verification link failing](#verification-link-failing) below. +:::tip Use the same identity every time +Sign in with the same Google account or email address each time. A different email (even a small typo or a different provider) looks like a brand-new account and a brand-new team. ::: -## Sign in +## Add Kite to Slack -1. Go to the Kite home page. -2. Select **Log In**. -3. Enter the email and password you used when you signed up. -4. Select **Log In** to continue to your dashboard. +Once you are signed in, click **Add me to Slack** and follow the steps in [Add Kite to Slack](/get-started/add-kite-to-slack). The install is done by a signed-in team member; it does not create the account. -:::tip Use the same email -Always sign in with the exact email address you used to create your account. A different email (even a small typo or a different provider) will look like a brand-new account. -::: - -## Troubleshooting - -### Verification link failing - -If the verification email arrives but the link doesn't work or says it's expired: +## Connect a teammate's Slack identity -- **Try again from the same browser and tab** you used to sign up. Opening the link in a different browser or device can cause it to fail. -- **Don't sign up again.** Repeated sign-ups can create duplicate accounts under the same email and make things harder to fix. -- If it still won't verify, **contact support** and let them know the email you used so they can help confirm your account. +Anyone in the channel can talk to Kite. To give a teammate access to the browser workspace as well, they click the **Connect Kite account** button Kite offers in Slack, or a team owner or admin adds them to the team. See [Team access](/slack/team-access). -### Password-reset email not arriving - -If you requested a password reset and the email hasn't shown up: +## Troubleshooting -- **Check your spam or junk folder** — automated emails sometimes land there. -- **Wait a few minutes.** Delivery can take a little time; avoid requesting it over and over. -- **Make sure you entered the correct email** — the one you actually used to create your account. -- If nothing arrives after several minutes and a spam check, contact support. +### The one-time code did not arrive -:::note -If reset emails (or other Kite emails) consistently don't reach you, your mail provider may be filtering them. See [Email sending troubleshooting](/troubleshooting/email-sending). -::: +- **Check your spam or junk folder.** +- **Wait a minute before requesting another.** Codes can take a moment to arrive, and each new request replaces the last code. +- **Make sure you typed the right email.** +- If nothing arrives after a few minutes, open **Chat with us** on kite.ai. ### "Session has already ended" or login errors when you return -If you come back later and see a "session has already ended" message or another login error: +- **Start the login again from kite.ai** rather than reloading an old page. +- **Close any stale tabs** left open from a previous session. +- Sign in fresh in a single, new tab. + +### Kite is in Slack but you cannot open the browser workspace -- **Start the login again from the home page** rather than reloading an old page. -- **Close any stale or old tabs** that were left open from a previous session — they can hold an expired session and cause errors. -- Try signing in fresh in a single, new tab. +Click the **Connect Kite account** button in Slack to link your Slack identity to the team, or ask a team owner or admin to add you. If you are not sure who that is, open **Chat with us** with your Slack workspace name. -### Still can't get in? +### Still cannot get in? -If none of the above works, contact support and include the email address on your account so the team can locate it. +Open **Chat with us** on kite.ai and include the email address you sign in with and your Slack workspace name. ## Related help -- [Account & Settings](/account/) — overview of your account and data options. -- [Email sending troubleshooting](/troubleshooting/email-sending) — when Kite emails don't arrive. -- [Delete Your Account & Data](/account/delete-account) — if you need to remove your account. +- [Add Kite to Slack](/get-started/add-kite-to-slack) +- [Team access](/slack/team-access) +- [Delete Your Account & Data](/account/delete-account) diff --git a/website/docs/building/README.md b/website/docs/building/README.md index 9f243ca..b719d15 100644 --- a/website/docs/building/README.md +++ b/website/docs/building/README.md @@ -1,35 +1,34 @@ --- title: Building & Editing Your Site -description: Learn how to build and refine your website with Kite by describing what you want in plain language and letting Kite's AI generate and edit it for you. +description: Learn how to build and refine the website Kite hosts for you by describing what you want in plain language, or by clicking an element and changing it directly. --- # Building & Editing Your Site -With Kite, you build a website by chatting. You describe what you want in plain language, and Kite's AI generates the pages, layout, copy, and styling for you. When you want to change something, you ask again — or point at it directly on the page. +Building and hosting your website is one of the ways Kite executes your growth strategy. You describe what you want in plain language, and Kite generates the pages, layout, copy, and styling. When you want to change something, you ask again, or you point at it directly on the page. ## How building with Kite works -1. **Describe your site.** Tell Kite what you're building (for example, "a one-page site for my bakery with a menu, hours, and a contact form"). -2. **Review what Kite generates.** Kite creates a full site you can preview right away. +1. **Describe your site.** Tell Kite what you need (for example, "a site for our clinic scheduling product with a homepage, a pricing page, a comparison page against Acme Scheduling, and a demo request form"). +2. **Pick a design.** Kite shows three design options, with chips to restyle the colors or fonts, combine options, or generate more. 3. **Refine it.** Ask for changes in chat, or use **Point & Edit** to click an element and change it directly. -4. **Publish.** When you're happy, you publish your site so visitors can see it. +4. **Publish.** When you are happy, publish the site so visitors can see it. Kite handles hosting, security, and deploys. -You don't need to write code, manage files, or know design tools. You describe the outcome you want, and Kite handles the build. +You do not need to write code, manage files, or know design software. :::tip The clearer and more specific your request, the better Kite's result. Name the page, the section, the exact text, and the exact color whenever you can. ::: -## In this section +## Site work from Slack -- [Editing Your Site](/building/editing-your-site) — the two ways to make changes, plus prompt tips and what to check when an edit doesn't appear. -- [Images & Logos](/building/images-and-logos) — upload and replace images, add a logo, handle transparent backgrounds, and manage the image frame. -- [Fonts & Media](/building/fonts-and-media) — use brand fonts, upload custom font files, and add other media. -- [Mobile & Responsive Design](/building/responsive-design) — how your site adapts to phones and tablets, and how to fix mobile-specific issues. -- [Pages & Navigation](/building/pages-and-navigation) — add pages, link them in your menu, and keep clean URLs. -- [Templates & Duplicating a Site](/building/templates-and-duplicating) — start from a design, choose among options, and reuse a design for another project. +You can also ask for pages and changes in Slack. Kite builds them as drafts and posts a card with **Preview** and **Review** buttons. Reply "publish it" and Kite deploys, or open the editor and publish yourself. See [Website building](/capabilities/website-building). -## Where to go next +## In this section -- New to Kite? Start with the [Quickstart](/get-started/quickstart) and [How Kite Works](/get-started/how-kite-works). -- Ready to go live? See [Publishing](/publishing/). +- [Editing Your Site](/building/editing-your-site): the two ways to make changes, plus request tips and what to check when an edit does not appear. +- [Images & Logos](/building/images-and-logos): upload and replace images, add a logo, generate or edit images, and manage the image frame. +- [Fonts & Media](/building/fonts-and-media): choose fonts by name, and add video and other media. +- [Mobile & Responsive Design](/building/responsive-design): how your site adapts to phones and tablets, and how to fix mobile-specific issues. +- [Pages & Navigation](/building/pages-and-navigation): add pages, link them in your menu, and keep clean URLs. +- [Starting Designs & Duplicating a Site](/building/templates-and-duplicating): the three design options, restyling, and duplicating a site. diff --git a/website/docs/building/editing-your-site.md b/website/docs/building/editing-your-site.md index f9c89a7..ea55ec6 100644 --- a/website/docs/building/editing-your-site.md +++ b/website/docs/building/editing-your-site.md @@ -1,6 +1,6 @@ --- title: Editing Your Site -description: Make changes to your Kite site by describing them in chat or using Point & Edit to click an element directly — plus prompt tips and what to do when an edit doesn't show up. +description: Make changes to your Kite site by describing them in chat or using Point & Edit to click an element directly, plus prompt tips and what to do when an edit doesn't show up. --- # Editing Your Site @@ -20,7 +20,7 @@ Tell Kite what to change in plain language. The more specific you are, the more > Make the heading bigger and change the color. **Specific (better):** -> On the **Home** page, in the hero section, change the heading to "Fresh Bread, Baked Daily" and make it dark brown (#3B2417). +> On the **Home** page, in the hero section, change the heading to "Scheduling that saves your front desk an hour a day" and make it navy (#1B2A4A). ## Option 2: Point & Edit @@ -44,7 +44,7 @@ Use **Point & Edit** when an element is hard to describe in words, or when there - **Say what to keep.** If you only want one thing changed, you can add "leave everything else the same." :::note -If a change comes out wrong, you can ask Kite to undo or revert it. You can also review earlier states of your site in [Version History](/troubleshooting/version-history). +If a change comes out wrong, restore an earlier version with **Restore to this point** beneath Kite's earlier response. See [Version History](/troubleshooting/version-history). ::: ## "Kite said it's done, but I don't see the change" @@ -53,7 +53,7 @@ This is one of the most common frustrations, and it's usually one of a few thing 1. **You're looking at the live site, not the latest edit.** Edits in the editor don't appear on your published site until you publish again. Check that you've published. 2. **Your browser is showing a cached version.** Refresh the page, or do a hard refresh, and try again. -3. **Kite changed a different page or section than you expected.** Ask Kite to confirm exactly which page, section, or file it changed — for example, "Which page and section did you just edit?" If it edited the wrong place, point it to the right one (using **Point & Edit** helps here). +3. **Kite changed a different page or section than you expected.** Ask Kite to confirm exactly which page, section, or file it changed, for example, "Which page and section did you just edit?" If it edited the wrong place, point it to the right one (using **Point & Edit** helps here). :::caution If you keep editing without publishing, your changes pile up in the editor but never reach visitors. When something looks "stuck," confirming publish status is almost always the first thing to check. @@ -64,4 +64,4 @@ If you keep editing without publishing, your changes pile up in the editor but n - **Edit reported done but not visible on the live site:** Publish again, then refresh your browser. See [Changes Not Showing](/publishing/changes-not-showing). - **Kite edited the wrong section:** Ask it which page/section it changed, then redirect it with **Point & Edit**. - **You want to go back to an earlier version:** See [Version History](/troubleshooting/version-history). -- **The editor seems frozen or unresponsive:** See [Editor Frozen](/troubleshooting/editor-frozen). +- **A chat turn is stuck:** Press **Stop**, then see [Chat Stuck or Page Crashed](/troubleshooting/editor-frozen). diff --git a/website/docs/building/fonts-and-media.md b/website/docs/building/fonts-and-media.md index bc832d8..dbf838e 100644 --- a/website/docs/building/fonts-and-media.md +++ b/website/docs/building/fonts-and-media.md @@ -1,17 +1,17 @@ --- title: Fonts & Media -description: Use your brand or custom fonts on your Kite site, upload font files, add video, and follow general tips for working with media. +description: Choose any Google Font by name for your Kite site, add video and images within the supported formats and sizes, and follow general tips for media. --- # Fonts & Media -Your fonts and media are a big part of your brand. Kite lets you apply custom fonts and add media so your site looks and feels like yours, not a template. +Your fonts and media are a big part of your brand. Kite lets you choose fonts and add media so your site looks and feels like yours. -## Using brand or custom fonts +## Choosing fonts -You can ask Kite to use a specific font across your site or in a particular spot. +Kite sites use Google Fonts, so you can ask for any font in the Google Fonts library by name. You do not upload font files. -1. Decide where the font should apply — the whole site, just headings, or one section. +1. Decide where the font should apply: the whole site, just headings, or one section. 2. Tell Kite the font name. For example: > Use "Poppins" for all headings and "Inter" for body text across the whole site. @@ -22,46 +22,32 @@ You can ask Kite to use a specific font across your site or in a particular spot Be specific about where the font goes. "Use this font for headings" gives a cleaner result than "change the font," which can leave some text behind. ::: -## Uploading a custom font file - -If your brand uses a font that isn't a common web font, you can upload the font file. - -1. Have your font file ready in a supported format: `.otf` or `.woff2`. -2. Upload the font file. -3. Ask Kite to apply it — for example: - -> Apply the font I just uploaded to all headings on the site. - -:::note -If you have your font in both formats, `.woff2` is generally the most efficient choice for the web. -::: - -:::caution -Make sure you have the right to use any custom font you upload. Some fonts require a license for use on a website. +:::note Custom font files +Kite does not accept uploaded font files (`.otf`, `.woff2`, and so on). If your brand font is not on Google Fonts, ask Kite to suggest the closest Google Font. ::: ## Adding video -You may be able to add video to your site — for example a background clip or an embedded clip in a section. - -To try it, describe what you want: +You can upload video in **MP4, WebM, MOV, or OGG**, up to **100 MB** per file. > Add a background video to the hero section on the **Home** page using the file I'm uploading. -If video isn't available the way you need it, a common alternative is to embed a hosted video (for example from a video platform) — ask Kite what's supported. +For longer or larger videos, upload to a video platform and ask Kite to embed it. + +## Adding images - +Images can be **PNG, JPG, WebP, GIF, HEIC, SVG, TIFF, BMP, ICO, or AVIF**, up to **10 MB** per file. See [Images & Logos](/building/images-and-logos). ## General media tips -- **Keep files reasonably sized.** Very large media files can slow down your page for visitors. -- **Use good source quality.** Kite can't improve a low-quality original. -- **Check mobile.** Media that looks great on desktop can crop or overflow on phones — see [Mobile & Responsive Design](/building/responsive-design). -- **Make one change at a time.** Apply a font, preview it, then move on, so it's easy to see what each change did. +- **Keep files reasonably sized.** Very large media files slow down your page for visitors. +- **Use good source quality.** Kite cannot improve a low-quality original. +- **Check mobile.** Media that looks great on desktop can crop or overflow on phones. See [Mobile & Responsive Design](/building/responsive-design). +- **Make one change at a time.** Apply a font, preview it, then move on. ## Troubleshooting -- **Font didn't apply everywhere:** Tell Kite specifically which text should use it (headings, body, buttons), one area at a time. -- **Uploaded font won't load:** Confirm the file is a supported format (`.otf` or `.woff2`) and try re-uploading. -- **Video won't add or play:** Confirm video support with Kite, and consider an embedded hosted video instead. -- **A media change isn't showing live:** Publish again and refresh — see [Changes Not Showing](/publishing/changes-not-showing). +- **Font did not apply everywhere:** Tell Kite specifically which text should use it (headings, body, buttons), one area at a time. +- **Font not found:** Check the spelling against [fonts.google.com](https://fonts.google.com). +- **Video will not upload:** Check the format and the 100 MB limit, or embed a hosted video instead. +- **A media change is not showing live:** Publish again and refresh. See [Changes Not Showing](/publishing/changes-not-showing). diff --git a/website/docs/building/images-and-logos.md b/website/docs/building/images-and-logos.md index 5561ddb..01293ff 100644 --- a/website/docs/building/images-and-logos.md +++ b/website/docs/building/images-and-logos.md @@ -1,11 +1,11 @@ --- title: Images & Logos -description: Upload and replace images, add your logo, get a transparent background, manage Kite's auto-applied image frame, and fix image replacements that fail or lose quality. +description: Upload and replace images, add your logo, generate or edit images, get a transparent background, and manage the image frame. --- # Images & Logos -Images and logos give your site its personality. With Kite you can upload your own pictures, swap out the ones Kite generated, and adjust how images are framed and presented — all from chat or **Point & Edit**. +Images and logos give your site its personality. With Kite you can upload your own pictures, swap out the ones Kite generated, and adjust how images are framed and presented, all from chat or **Point & Edit**. ## Upload and replace an image @@ -13,7 +13,7 @@ Images and logos give your site its personality. With Kite you can upload your o 2. Choose to upload a new image, and pick the file from your device. 3. Confirm, then preview the result. -You can also ask in chat — for example: +You can also ask in chat, for example: > Replace the photo in the hero section on the **Home** page with the image I'm uploading. @@ -25,18 +25,26 @@ Upload images at a good size and resolution. Large, clear images look sharp; tin 1. Use **Point & Edit** to click your current logo (often in the header), or ask Kite where your logo lives. 2. Upload your logo file. -3. Check it on both desktop and mobile — see [Mobile & Responsive Design](/building/responsive-design). +3. Check it on both desktop and mobile. See [Mobile & Responsive Design](/building/responsive-design). Prompt example: > Replace the logo in the header with the file I'm uploading, and keep it the same size. +## Generate or edit an image + +Kite can generate images, edit existing ones, and remove backgrounds. Ask in chat: + +> Generate a hero image of a calm clinic front desk, soft morning light, no people. + +> Remove the background from the logo I just uploaded. + ## Getting a transparent background A transparent background lets your logo sit cleanly over any color or photo, without a white box around it. -1. Upload a logo that already has a transparent background (usually a `.png` file). -2. If your logo has a solid background you want removed, ask Kite to help — for example: +1. Upload a logo that already has a transparent background (a `.png`, `.svg`, or `.webp` file). +2. If your logo has a solid background you want removed, ask Kite to remove it, for example: > Can you remove the white background from my logo so it's transparent? @@ -46,7 +54,7 @@ The cleanest results come from a logo file that's already transparent. If you ha ## The image frame (and how to remove it) -Kite often applies a **frame** to images automatically — for example a border, rounded corners, or a shadow — to make them look polished. If you want a plain, edge-to-edge image instead, just ask: +Kite often applies a **frame** to images automatically (for example a border, rounded corners, or a shadow) to make them look polished. If you want a plain, edge-to-edge image instead, just ask: > Remove the frame from the image in the hero section so it has no border, no rounded corners, and no shadow. @@ -61,11 +69,11 @@ You can also ask Kite to change the frame rather than remove it: - **The replacement didn't take:** Try again with **Point & Edit** so Kite knows exactly which image you mean, then confirm which image it changed. - **The new image looks blurry or pixelated:** Upload a higher-resolution source file. Kite can't add detail that isn't in the original. - **The image looks stretched or squished:** Ask Kite to keep the original aspect ratio, or to fit the image without distorting it. -- **The change isn't showing on your live site:** Publish again and refresh — see [Changes Not Showing](/publishing/changes-not-showing). +- **The change isn't showing on your live site:** Publish again and refresh. See [Changes Not Showing](/publishing/changes-not-showing). ## Troubleshooting -- **Upload didn't work:** Try a different file or a smaller file size, and make sure it's a common image format. +- **Upload did not work:** Check the file is under 10 MB and in a supported format (PNG, JPG, WebP, GIF, HEIC, SVG, TIFF, BMP, ICO, or AVIF). - **Wrong image got replaced:** Use **Point & Edit** to target the exact image, then ask Kite to confirm which one it changed. - **Logo has an unwanted white box:** Use a transparent file, or ask Kite to remove the background. - **Image looks great in the editor but not when published:** See [Changes Not Showing](/publishing/changes-not-showing). diff --git a/website/docs/building/pages-and-navigation.md b/website/docs/building/pages-and-navigation.md index 77a6353..8e40fb0 100644 --- a/website/docs/building/pages-and-navigation.md +++ b/website/docs/building/pages-and-navigation.md @@ -5,7 +5,7 @@ description: Add pages like About, Contact, and Pricing to your Kite site, link # Pages & Navigation -As your site grows, you'll want more than one page — an About page, a Contact page, maybe Pricing. Kite can add pages, link them in your menu, and keep your URLs clean, all from chat. +As your site grows, you'll want more than one page: an About page, a Contact page, maybe Pricing. Kite can add pages, link them in your menu, and keep your URLs clean, all from chat. ## Adding a page @@ -18,10 +18,10 @@ As your site grows, you'll want more than one page — an About page, a Contact Common pages people add: -- **About** — `/about` -- **Contact** — `/contact` -- **Pricing** — `/pricing` -- **Services** — `/services` +- **About**: `/about` +- **Contact**: `/contact` +- **Pricing**: `/pricing` +- **Services**: `/services` :::tip Add one page at a time and review it before moving on. It's easier to get each page right than to fix several at once. @@ -39,7 +39,7 @@ You can also ask Kite to rename, reorder, or remove menu links: ## Clean URLs -Clean URLs are short and readable — like `yoursite.com/about` instead of something long and cluttered. Kite generally creates clean URLs for your pages. If a page URL isn't what you want, ask: +Clean URLs are short and readable, like `yoursite.com/about` instead of something long and cluttered. Kite generally creates clean URLs for your pages. If a page URL isn't what you want, ask: > Change the URL of the About page to /about. @@ -47,24 +47,24 @@ Clean URLs are short and readable — like `yoursite.com/about` instead of somet ## Common issue: a subpage shows the homepage on the live site -A frequent problem is this: in the editor your **About** (or other) page looks correct, but on your **published** site, visiting `/about` shows your homepage content instead of the About content. This is usually a **routing** issue — the URL isn't pointing to the right page on the live site. +A frequent problem is this: in the editor your **About** (or other) page looks correct, but on your **published** site, visiting `/about` shows your homepage content instead of the About content. This is usually a **routing** issue: the URL isn't pointing to the right page on the live site. To fix it: 1. Confirm the page exists and looks right in the editor. -2. Ask Kite to fix the routing — for example: +2. Ask Kite to fix the routing, for example: > On the live site, /about is showing the homepage instead of the About page. Please fix the routing so /about loads the About page content. 3. Publish again, then visit the page in a fresh browser tab (or hard-refresh). :::caution -This often looks like "my edit didn't save," but the content is usually fine — the live URL just isn't routing to it. Publish and refresh first, then ask Kite to fix routing if the wrong page still loads. See [Changes Not Showing](/publishing/changes-not-showing). +This often looks like "my edit didn't save," but the content is usually fine. The live URL just isn't routing to it. Publish and refresh first, then ask Kite to fix routing if the wrong page still loads. See [Changes Not Showing](/publishing/changes-not-showing). ::: ## Troubleshooting - **New page isn't in the menu:** Ask Kite to add a nav link to it, and say where in the order it should go. -- **A subpage shows the homepage when published:** Ask Kite to fix the routing for that URL, then publish and refresh — see [Changes Not Showing](/publishing/changes-not-showing). +- **A subpage shows the homepage when published:** Ask Kite to fix the routing for that URL, then publish and refresh. See [Changes Not Showing](/publishing/changes-not-showing). - **Wrong or messy URL:** Ask Kite to set the page's URL to the clean path you want. - **Menu link goes to the wrong page:** Tell Kite which link and which page it should point to. diff --git a/website/docs/building/responsive-design.md b/website/docs/building/responsive-design.md index a02a096..6a06465 100644 --- a/website/docs/building/responsive-design.md +++ b/website/docs/building/responsive-design.md @@ -5,7 +5,7 @@ description: See how your Kite site adapts to phones and tablets, preview the mo # Mobile & Responsive Design -Most of your visitors will see your site on a phone, so it needs to look great at every size. Kite builds responsive sites that adapt to phones, tablets, and desktops automatically — and when something doesn't look right on one size, you can ask Kite to fix just that. +Most of your visitors will see your site on a phone, so it needs to look great at every size. Kite builds responsive sites that adapt to phones, tablets, and desktops automatically, and when something doesn't look right on one size, you can ask Kite to fix just that. ## How your site adapts @@ -18,7 +18,7 @@ You don't have to design three separate sites. You design once, and Kite adapts Before you publish, check how your site looks on a phone. 1. Open the preview. -2. Switch to the mobile (or tablet) view to see how the layout changes. +2. Click the viewport button in the preview bar. It cycles through Desktop, Tablet (768 px wide), and Mobile (375 px wide). 3. Scroll through every page and check headings, images, buttons, and the menu. :::tip @@ -47,5 +47,5 @@ When you report a mobile issue, name the screen size (mobile, tablet, or desktop - **Images crop or cut off on mobile:** Ask Kite to show the full image on mobile, or to change how the image fits on small screens. - **Hamburger menu appears on desktop:** Ask Kite to show the full menu on desktop and only collapse to a hamburger on mobile. - **Text overflows or buttons run off the edge on phones:** Tell Kite which page and section, and that it's happening on mobile. -- **Mobile looks fine in preview but wrong when published:** Publish again and refresh on your phone — see [Changes Not Showing](/publishing/changes-not-showing). -- **The preview itself won't load:** See [Preview Not Loading](/troubleshooting/preview-not-loading). +- **Mobile looks fine in preview but wrong when published:** Publish again and refresh on your phone. See [Changes Not Showing](/publishing/changes-not-showing). +- **The preview itself won't load:** See [Preview Won't Start](/troubleshooting/preview-not-loading). diff --git a/website/docs/building/templates-and-duplicating.md b/website/docs/building/templates-and-duplicating.md index bae1ae3..cab627f 100644 --- a/website/docs/building/templates-and-duplicating.md +++ b/website/docs/building/templates-and-duplicating.md @@ -1,37 +1,37 @@ --- -title: Templates & Duplicating a Site -description: Start your Kite site from a template or design, choose among the design options Kite generates, ask for more options, and reuse an existing site's design for another project or client. +title: Starting Designs & Duplicating a Site +description: Start your Kite site from a generated design, choose among the design options Kite generates, ask for more options, and reuse an existing site's design for another project. --- -# Templates & Duplicating a Site +# Starting Designs & Duplicating a Site -You don't have to start from a blank page. Kite can generate a design for you to build on, give you several options to pick from, and help you reuse a design you already like for a new project. +You do not have to start from a blank page. Kite generates a starting design for you to build on, gives you several options to pick from, and helps you reuse a design you already like for a new project. -## Starting from a template or design +## Starting from a generated design -When you describe your site, Kite generates a starting design based on your prompt. The more detail you give about your style and goals, the closer the first design will be to what you want. +When you describe your site, Kite generates a starting design based on your request. The more detail you give about your style and goals, the closer the first design will be to what you want. -1. Describe your site, including the vibe you're going for. For example: +1. Describe your site, including the feel you are going for. For example: -> Build a modern, minimal site for a wedding photographer, with lots of large photos and a soft, neutral color palette. +> Build a clean, modern site for Northstar, scheduling software for multi-location clinics. Use a calm blue palette, lots of white space, and a demo request button in the header. 2. Review the design Kite generates. -3. Refine it with chat edits or **Point & Edit** — see [Editing Your Site](/building/editing-your-site). +3. Refine it with chat edits or **Point & Edit**. See [Editing Your Site](/building/editing-your-site). :::tip -Mention your style, colors, and mood in your first prompt. "Bold and colorful" versus "calm and minimal" leads to very different starting designs. +Mention your style, colors, and mood in your first request. "Bold and colorful" versus "calm and minimal" leads to very different starting designs. ::: ## Choosing among generated design options -Kite may show you more than one design option to choose from. +Kite shows you three design options. Above them are chips to restyle the **Colors** or **Fonts**, **Combine** elements you like from different options, or **Generate more options**. 1. Look over each option. -2. Pick the one closest to what you want — you don't need the perfect one, just the best starting point. +2. Pick the one closest to what you want. You do not need the perfect one, just the best starting point. 3. Build from there with edits. :::note -Choose the option that's closest in layout and feel, then refine it. It's usually faster to adjust a near-match than to start over. +Choose the option that is closest in layout and feel, then refine it. It is usually faster to adjust a near-match than to start over. ::: ## Asking for more options @@ -40,32 +40,31 @@ If none of the designs feel right, ask Kite to try again: > None of these feel right. Can you show me a few more options that are warmer and use a serif font? -Give Kite direction on what to change — colors, layout, mood, fonts — so the next round moves closer to what you want. +Give Kite direction on what to change (colors, layout, mood, fonts) so the next round moves closer to what you want. -## Reusing a design for another project or client +## Reusing a design for another project -If you've built a site you love and want to use its design for another project or client, you have a couple of routes. +If you have built a site you love and want to use its design for another product line or a second brand, you have a couple of routes. -- **If a one-click duplicate exists:** Look for a **Duplicate** option on your site or project. -- **Workaround if there's no duplicate:** Describe the existing design to Kite as the starting point for the new project — for example: +- **Duplicate the site.** In your websites list, open the row menu for the site and choose **Duplicate website**. Kite creates a new, unpublished copy with a fresh chat, and you swap in the new content from there. +- **Or describe the design.** Ask Kite to use an existing site as the starting point for a new one. For example: -> Build a new site that uses the same layout, fonts, and color style as my "Bakery" site, but for a coffee shop called "Daybreak." +> Build a new site that uses the same layout, fonts, and color style as our "Northstar" site, but for our new product, "Northstar Payments." Then swap in the new content, images, and copy. :::caution -Reusing a design for a different client usually still happens as a separate site, so each project stays independent. Confirm in Kite how new projects are created and billed. +A duplicated site is a separate project with its own chat, versions, and publish state. Building on it uses credits like any other site. ::: ## Troubleshooting -- **The starting design is far from what you want:** Give Kite a more detailed prompt about style, colors, and mood, and ask for new options. -- **You can't find a duplicate option:** Use the workaround above — describe the existing design as the starting point for the new site. -- **The reused design doesn't match the original:** Point Kite to specifics (the exact fonts, colors, and layout) rather than asking it to "make it like the other site." +- **The starting design is far from what you want:** Give Kite a more detailed request about style, colors, and mood, and ask for new options. +- **The reused design does not match the original:** Point Kite to specifics (the exact fonts, colors, and layout) rather than asking it to "make it like the other site." ## Related - [Editing Your Site](/building/editing-your-site) - [Images & Logos](/building/images-and-logos) - [Pages & Navigation](/building/pages-and-navigation) -- For pricing questions when starting new projects, see [How Credits Work](/pricing-credits/how-credits-work). +- For credit questions when starting new projects, see [How Credits Work](/pricing-credits/how-credits-work). diff --git a/website/docs/capabilities/README.md b/website/docs/capabilities/README.md new file mode 100644 index 0000000..b0ef9df --- /dev/null +++ b/website/docs/capabilities/README.md @@ -0,0 +1,22 @@ +--- +title: What Kite Can Do +description: An overview of the work Kite does for your team, from research and growth plans to content, launches, conversion work, website building, initiatives, and workflows. +--- + +# What Kite Can Do + +Kite is your AI marketer in Slack. It researches your business, builds a growth strategy, and ships the work that brings you new customers. This section describes the kinds of work to ask for, and the few things Kite starts on its own. + +## In this section + +- [Research and growth plans](/capabilities/research-and-growth-plan): competitor, keyword, and customer research, website audits, the Growth Grader report, and initiatives. +- [Content, outreach, and channels](/capabilities/content-and-outreach): landing pages, comparison pages, email sequences, prospect lists, and posts for the networks you connect. +- [Product marketing and launches](/capabilities/product-marketing): the product page, announcement, and email campaign for your next release. +- [Conversion work](/capabilities/conversion-fixes): audits, A/B experiments, and fixes on the pages you already have. +- [Website building](/capabilities/website-building): Kite builds, hosts, and updates your website, and you can edit it yourself in the browser editor. +- [Initiatives, reports, and workflows](/capabilities/initiatives-reports-and-workflows): the initiatives board, hosted reports and dashboards, scheduled and webhook-triggered workflows, and custom agents. +- [Tools on kite.ai](/capabilities/free-tools): Growth Grader, LinkedIn to Website, and Website Makeover. + +## What Kite is not + +Kite is not a replacement for a marketing hire. It gives a founder or a lean team marketing capacity before there is a marketer on staff, and it works alongside that person once there is. diff --git a/website/docs/capabilities/content-and-outreach.md b/website/docs/capabilities/content-and-outreach.md new file mode 100644 index 0000000..c7b6246 --- /dev/null +++ b/website/docs/capabilities/content-and-outreach.md @@ -0,0 +1,30 @@ +--- +title: Content, Outreach, and Channels +description: The content Kite writes and ships, including landing and comparison pages, email sequences, prospect lists, and posts for the social networks your team connects. +--- + +# Content, Outreach, and Channels + +Ask Kite for the asset and it writes it, builds it, and lines it up. Give the OK and it publishes that too. + +## Content Kite drafts and ships + +- **Landing pages and comparison pages**, built directly on your Kite-hosted site as drafts. +- **Buyer guides and content briefs**, delivered in the thread or as a hosted report. +- **Email sequences and campaigns**, sent from your team's `teamslug@kite.space` address or through an email service you connect. +- **Prospect lists**, researched to your criteria. +- **Social posts**, drafted for any network and published through the networks your team has connected on the Integrations page. + +## Where Kite publishes + +Kite publishes to the channels you have connected: your Kite-hosted website, email, and any social network linked on the Integrations page in your browser workspace. It drafts for channels it is not connected to, and you post those yourself. Kite researches public forums through ordinary web search but does not post replies in them. See [Integrations](/forms-integrations/integrations). + +## Keeping your voice + +Kite writes from its research into how you describe your product. If a draft sounds wrong, say how in the thread: "more direct," "less formal," "lead with the outcome." Kite revises and learns your voice over time. See [Asking Kite to do something](/slack/asking-kite). + +## Related + +- [Research and growth plans](/capabilities/research-and-growth-plan) +- [Product marketing and launches](/capabilities/product-marketing) +- [Approvals and autonomy](/slack/approvals) diff --git a/website/docs/capabilities/conversion-fixes.md b/website/docs/capabilities/conversion-fixes.md new file mode 100644 index 0000000..2452e8c --- /dev/null +++ b/website/docs/capabilities/conversion-fixes.md @@ -0,0 +1,31 @@ +--- +title: Conversion Work +description: Ask Kite why a page is not converting and it audits the page, proposes the fix, builds it, and can run an A/B experiment to prove it. +--- + +# Conversion Work + +Traffic you already have is the cheapest growth available. Ask Kite why a page is not converting and it audits the page, finds the gap, builds the fix as a draft, and can test it against the original. + +## What to ask for + +- "Why isn't the pricing page converting?" Kite reviews the page, the analytics, and the path visitors take, then proposes a specific change with a preview. +- "Audit the site for conversion problems." Kite checks every page for missing calls to action, weak headlines, slow load times, and pages that rank but do not answer the searcher's question. +- "Run an experiment on the homepage headline." Kite sets up an A/B experiment on your Kite-hosted site with two versions and a traffic split. Starting the experiment is the one step a signed-in team member does, and the results page shows which version won. + +## Scheduling a recurring check + +If you want this to happen without asking, set up a workflow that runs a conversion check every week and posts what it finds. See [Initiatives, reports, and workflows](/capabilities/initiatives-reports-and-workflows). + +## Where the data comes from + +Every Kite-hosted site has built-in analytics with pageviews, top pages, referrers, devices, events, and funnels on paid plans, plus a Leads inbox for form submissions and a Discoverability tab with speed scores and a **Review and fix** button. See [Site analytics](/forms-integrations/analytics). + +## Making the change yourself + +Every conversion fix is a website change, so you can also make it by hand in the browser editor: describe the edit in chat or click the element to change it, preview, and publish. See [Editing your site](/building/editing-your-site). + +## Related + +- [Research and growth plans](/capabilities/research-and-growth-plan) +- [Website building](/capabilities/website-building) diff --git a/website/docs/capabilities/free-tools.md b/website/docs/capabilities/free-tools.md new file mode 100644 index 0000000..7bbf22a --- /dev/null +++ b/website/docs/capabilities/free-tools.md @@ -0,0 +1,25 @@ +--- +title: Tools on kite.ai +description: The tools offered on kite.ai, including Growth Grader, LinkedIn to Website, and Website Makeover, and what each one needs from you. +--- + +# Tools on kite.ai + +Alongside the full product, kite.ai offers a few tools that give you a quick result and a natural starting point for working with Kite. Each needs a Kite account, which takes a minute to create with Google or an email code. + +## Growth Grader + +[Growth Grader](https://kite.ai/growth-grader) takes your company domain and grades it against a 138-point checklist covering positioning, search demand, AI visibility, conversion, onboarding, reviews, unit economics, paid and outbound, owned audience, and technical blockers. Running it uses credits, and Kite announces the finished report in your Slack home channel. It is a quick way to see the kind of research Kite does before you put it to work. + +## LinkedIn to Website + +[LinkedIn to Website](https://kite.ai/linkedin) turns a LinkedIn profile into a published website in a few minutes. It is the fastest way to get a site live if you do not have one yet. Once the site exists, you can edit it in the browser editor and connect your own domain. See [Website building](/capabilities/website-building). + +## Website Makeover + +[Website Makeover](https://kite.ai/your-website-makeover) takes your existing website and shows you what a rebuilt version could look like. It is useful when you already have a site and want to see what Kite would change before committing. + +## Related + +- [Add Kite to Slack](/get-started/add-kite-to-slack) +- [Website building](/capabilities/website-building) diff --git a/website/docs/capabilities/initiatives-reports-and-workflows.md b/website/docs/capabilities/initiatives-reports-and-workflows.md new file mode 100644 index 0000000..59189de --- /dev/null +++ b/website/docs/capabilities/initiatives-reports-and-workflows.md @@ -0,0 +1,30 @@ +--- +title: Initiatives, Reports, and Workflows +description: The initiatives board where Kite's plans live, the hosted reports and dashboards it produces, scheduled and webhook-triggered workflows, and custom agents and skills. +--- + +# Initiatives, Reports, and Workflows + +Beyond individual tasks, Kite organises its work into initiatives, delivers longer results as hosted reports and dashboards, runs workflows on a schedule or a trigger, and can be extended with custom agents and skills. This page introduces each. + +## Initiatives + +An initiative is a goal with tasks under it. Kite proposes initiatives in Slack with an **Approve** button; click it and Kite breaks the initiative into tasks and starts. You can also create and track initiatives on the initiatives board in your browser workspace. Kite's hourly scan of your team's Slack messages is matched against active initiatives, which is how it finds the next move and posts a digest. + +## Reports and dashboards + +When a result is too large for a Slack thread, Kite delivers it as a hosted report or dashboard and posts the link. Reports can be pinned from Slack so they stay easy to find. + +## Workflows + +A workflow is a piece of work Kite runs on its own, either on a schedule (a weekly conversion check, a monthly competitor sweep) or when a webhook fires (a release goes out, a form is submitted). Workflows are how you turn a one-off request into something that keeps happening. + +## Custom agents and skills + +Teams can give Kite custom agents and skills for work specific to their business. This is an advanced feature; ask Kite in Slack how to set one up. + +## Related + +- [Research and growth plans](/capabilities/research-and-growth-plan) +- [Conversion work](/capabilities/conversion-fixes) +- [What Kite posts in Slack](/slack/what-kite-posts) diff --git a/website/docs/capabilities/product-marketing.md b/website/docs/capabilities/product-marketing.md new file mode 100644 index 0000000..64725ee --- /dev/null +++ b/website/docs/capabilities/product-marketing.md @@ -0,0 +1,34 @@ +--- +title: Product Marketing and Launches +description: Tell Kite what is shipping and it prepares the product page, the announcement, and the email campaign, then publishes them when you give the word. +--- + +# Product Marketing and Launches + +Tell Kite what is shipping and when, and it gets the launch ready before the code is. + +## How a launch runs + +1. **Tell Kite about the release** in a thread: what changed, who it is for, and when it lands. Paste the pull request description or the release notes if you have them. +2. **Kite prepares the assets** and posts them in the thread: + - A product or feature page, written in language search engines can find, built as a draft on your site. + - An announcement, ready for your blog and your connected social networks. + - An email campaign, ready to send. +3. **You read it once.** Reply with changes, or with "ship it." +4. **Kite publishes** the page, sends the email, and posts the announcement to the networks you have connected. + +Your team merges the pull request. Kite launches the release. + +## Keeping launches on a rhythm + +If you ship on a schedule, set up a workflow so Kite runs the launch checklist each time, or trigger it from a webhook when a release goes out. See [Initiatives, reports, and workflows](/capabilities/initiatives-reports-and-workflows). + +## Why this matters for lean teams + +On most small teams, launch marketing happens after the engineering work, if it happens at all. With Kite, shipping a feature and telling customers about it happen in the same week. + +## Related + +- [Content, outreach, and channels](/capabilities/content-and-outreach) +- [Website building](/capabilities/website-building) +- [Integrations](/forms-integrations/integrations) diff --git a/website/docs/capabilities/research-and-growth-plan.md b/website/docs/capabilities/research-and-growth-plan.md new file mode 100644 index 0000000..3478075 --- /dev/null +++ b/website/docs/capabilities/research-and-growth-plan.md @@ -0,0 +1,36 @@ +--- +title: Research and Growth Plans +description: How Kite researches your product, customers, competitors, and search demand, what the Growth Grader report covers, and how initiatives turn research into a plan. +--- + +# Research and Growth Plans + +Kite's work rests on research. Ask it to look at a competitor, a keyword, a customer segment, or your own site, and it comes back with evidence and a recommended move. Larger plans live on the initiatives board. + +## Research you can ask for + +- **Competitor research.** How a competitor positions itself, what it charges, where it shows up, and where you can beat it. +- **Keyword and search demand research.** What your prospects search for and which pages could win those searches. +- **Customer research.** Who buys, what they say, and what they are trying to get done. +- **Website audits.** Where your own site is weak on positioning, speed, conversion, or discoverability. +- **AI visibility.** How AI answer engines currently describe your company and your category, and where you are missing. + +Every recommendation comes with the evidence behind it: the competitor page Kite read, the search volumes it found, the thread it spotted. Kite finds what needs doing. You see why. + +## The Growth Grader report + +Growth Grader takes a company domain and grades it against a 138-point checklist covering positioning, search demand, AI visibility, conversion, onboarding, reviews, unit economics, paid and outbound, owned audience, and technical blockers. Running it from inside Kite needs a signed-in team member and uses credits. For teams that sign up on the website, Kite announces the finished report in the home Slack channel. See [Tools on kite.ai](/capabilities/free-tools). + +## Initiatives: research turned into a plan + +An initiative is a goal with tasks under it, for example "Win the comparison searches against Acme" or "Launch the clinic-network tier." Kite proposes initiatives in Slack with an **Approve** button; click it and Kite breaks the initiative into tasks and starts. You can also create initiatives yourself on the initiatives board. Kite's hourly scan of your team's Slack messages is matched against active initiatives, which is how it spots the next move and posts a digest. See [Initiatives, reports, and workflows](/capabilities/initiatives-reports-and-workflows). + +## Correcting Kite's research + +If Kite has something wrong about your business, say so in the thread. Kite updates its understanding, and every plan that builds on it gets better. Early corrections save credits later. + +## Related + +- [What Kite posts in Slack](/slack/what-kite-posts) +- [Content, outreach, and channels](/capabilities/content-and-outreach) +- [Conversion work](/capabilities/conversion-fixes) diff --git a/website/docs/capabilities/website-building.md b/website/docs/capabilities/website-building.md new file mode 100644 index 0000000..8345831 --- /dev/null +++ b/website/docs/capabilities/website-building.md @@ -0,0 +1,41 @@ +--- +title: Website Building +description: Kite builds, hosts, and updates your website as part of executing your growth strategy. Learn how site work fits into Kite's loop and where to find the detailed guides. +--- + +# Website Building + +Your website is where Kite's work often starts. Kite builds it, hosts it, and keeps it updated, handling hosting, security, and deploys so your team can focus on the business. + +## How website work happens + +There are two ways site work gets done, and most teams use both: + +- **From Slack.** Ask for a page or a change in a thread. Kite builds it as a draft and posts a card with **Preview** and **Review** buttons. Reply "publish it" and Kite deploys it, or click Review and press **Publish** in the editor yourself. +- **In the browser editor.** Open your site, describe a change in chat or click an element to change it directly, preview the result, and click **Publish**. See [Building & editing your site](/building/). + +## What Kite handles for you + +- **Building.** Kite writes the pages, layout, copy, and styling from a description of what you need, and shows you three design options to start from. +- **Hosting and deploys.** Every published site gets a free `your-site.kite.space` address, which you can rename. On the Growth or Business plan you can connect your own domain. See [Custom domains](/custom-domains/). +- **Search groundwork.** Kite generates page titles, a live sitemap, a robots file that welcomes AI crawlers, an `llms.txt`, and structured data, and on paid plans it verifies your domain with Google Search Console and submits the sitemap after publish. See [SEO & discoverability](/seo/). +- **Analytics and leads.** Built-in analytics, a Leads inbox for form submissions, and a Discoverability tab. See [Site analytics](/forms-integrations/analytics). +- **Updates.** Ask for changes in Slack or the editor and Kite makes them. + +## Bringing an existing site + +Kite can import an existing website or a GitHub repository, keep the code in sync both ways, and edit content in an external CMS such as Contentful, Sanity, Storyblok, Webflow, or Payload. See [Integrations](/forms-integrations/integrations) and [Migrate an existing site](/seo/migrate-existing-site). + +## Starting a new site + +If you do not have a site yet, describe what you need and Kite builds a first version. You can also turn a LinkedIn profile into a website in a few minutes. See [Tools on kite.ai](/capabilities/free-tools). + +## Detailed guides + +The full website guides live under [Website Building](/website-building): + +- [Building & editing](/building/): editing, images, fonts, mobile layout, and pages. +- [Publishing](/publishing/): going live, your kite.space address, and fixing changes that do not show. +- [Custom domains & DNS](/custom-domains/): connect your own domain. +- [SEO & discoverability](/seo/): titles, sitemaps, social previews, and migrations. +- [Forms & integrations](/forms-integrations/): contact forms, analytics, and integrations. diff --git a/website/docs/custom-domains/README.md b/website/docs/custom-domains/README.md index f8e9034..ef5df04 100644 --- a/website/docs/custom-domains/README.md +++ b/website/docs/custom-domains/README.md @@ -1,37 +1,36 @@ --- title: Custom Domains & DNS -description: Learn how to connect your own domain name to your published Kite site, set up DNS, and troubleshoot common domain issues. +description: Learn how to connect your own domain name to your published Kite site on the Growth or Business plan, set up DNS, and troubleshoot common domain issues. --- # Custom Domains & DNS -A custom domain is your own web address (like `yourbusiness.com`) instead of the free Kite address that ends in `.kite.space`. Connecting one makes your site look professional and easy to remember. This section walks you through everything from your first connection to fixing a domain that isn't behaving. +A custom domain is your own web address (like `yourcompany.com`) instead of the free Kite address that ends in `.kite.space`. Connecting one makes your site look professional and easy to remember. This section walks you through everything from your first connection to fixing a domain that is not behaving. ## What is a custom domain? -When you build a site with Kite, it's published to a free address such as `your-site.kite.space`. A custom domain lets visitors reach that same site at a name you own, such as `www.yourbusiness.com`. You buy or already own the domain from a registrar (the company you bought it from, like GoDaddy or Squarespace), and then you point it at Kite using DNS settings. +When you build a site with Kite, it is published to a free address such as `your-site.kite.space`. A custom domain lets visitors reach that same site at a name you own, such as `www.yourcompany.com`. You buy or already own the domain from a registrar (the company you bought it from, like GoDaddy or Squarespace), and then you point it at Kite using DNS settings. :::note What is DNS? -DNS (Domain Name System) is like the internet's phone book. It tells browsers which server to load when someone types your domain. Connecting a domain to Kite means adding a couple of DNS records so your domain points to Kite's servers. +DNS (Domain Name System) is like the internet's phone book. It tells browsers which server to load when someone types your domain. Connecting a domain to Kite means adding a few DNS records so your domain points to Kite's servers. ::: ## Before you start -A few things need to be true before you can connect a custom domain: +1. **Publish your site first.** A custom domain points to a published site. See [How to publish](/publishing/how-to-publish). +2. **Be on Growth or Business, or in the 5-day trial.** Custom domains require an active subscription. Moving to Free disconnects them. See [Plans & Pricing](/pricing-credits/plans-and-trial). +3. **You need access to your domain's DNS settings,** either through the one-click flow or by logging in to your registrar. +4. **One custom domain per site.** To change it, disconnect the current one first. -1. **You must publish your site first.** A custom domain points to a published site, so there has to be something live to point at. See [How to publish](/publishing/how-to-publish). -2. **Connecting a custom domain requires a paid plan.** Free sites use the `.kite.space` address only. See [Plans & trial](/pricing-credits/plans-and-trial). -3. **You need access to your domain's DNS settings** — either through the one-click flow or by logging in to your registrar. - -:::tip You don't have to buy your domain from Kite -It doesn't matter where you bought your domain. What matters is that its DNS points to Kite. See [Connect a domain from your registrar](/custom-domains/registrar-guides). +:::tip You do not have to buy your domain from Kite +It does not matter where you bought your domain. What matters is that its DNS points to Kite. See [Connect a domain from your registrar](/custom-domains/registrar-guides). ::: ## Articles in this section -- [Connect a Custom Domain](/custom-domains/connect-a-custom-domain) — the core how-to, covering both the one-click Entri flow and manual DNS setup. -- [Connect a Domain from Your Registrar](/custom-domains/registrar-guides) — where to find DNS settings at Squarespace, GoDaddy, Namecheap, OVH, Google Domains, Cloudflare, and more. -- [www vs. Root Domain (and SSL)](/custom-domains/www-vs-root) — choosing a primary address and avoiding "Connection Not Private" warnings. -- [Transferring a Domain & Keeping Your Email](/custom-domains/transfer-and-email) — what happens to your registrar and your email when you connect to Kite. -- [Move, Switch, or Reuse a Domain Across Sites](/custom-domains/switch-or-reuse-domain) — changing which site a domain points to. -- [Troubleshoot a Connected Domain](/custom-domains/troubleshooting) — fixes for 404s, old sites showing, SSL errors, and more. +- [Connect a Custom Domain](/custom-domains/connect-a-custom-domain): the core how-to, covering both the one-click Entri flow and manual DNS setup. +- [Connect a Domain from Your Registrar](/custom-domains/registrar-guides): where to find DNS settings at Squarespace, GoDaddy, Namecheap, OVH, Cloudflare, and more. +- [www and Root Domain (and SSL)](/custom-domains/www-vs-root): how Kite handles both addresses and avoids "Connection Not Private" warnings. +- [Connecting a Domain & Keeping Your Email](/custom-domains/transfer-and-email): what happens to your registrar and your email when you connect to Kite. +- [Move, Switch, or Reuse a Domain Across Sites](/custom-domains/switch-or-reuse-domain): changing which site a domain points to. +- [Troubleshoot a Connected Domain](/custom-domains/troubleshooting): fixes for 404s, verification needed, SSL errors, and more. diff --git a/website/docs/custom-domains/connect-a-custom-domain.md b/website/docs/custom-domains/connect-a-custom-domain.md index 605624a..8260548 100644 --- a/website/docs/custom-domains/connect-a-custom-domain.md +++ b/website/docs/custom-domains/connect-a-custom-domain.md @@ -1,16 +1,16 @@ --- title: Connect a Custom Domain -description: Step-by-step guide to connecting your own domain to your Kite site using the one-click Entri flow or manual DNS setup. +description: Step-by-step guide to connecting your own domain to your Kite site using the one-click Entri flow or manual DNS setup, or buying a domain through Kite. --- # Connect a Custom Domain -This article shows you how to point your own domain (like `yourbusiness.com`) at your published Kite site. You can connect a domain you already own or buy one directly through Kite. +This article shows you how to point your own domain (like `yourcompany.com`) at your published Kite site. You can connect a domain you already own or buy one directly through Kite. ## Before you start -- **Publish your site first.** You can only connect a domain to a live site. The **Add custom domain** button stays disabled until you publish. See [How to publish](/publishing/how-to-publish). -- **Custom domains require a paid Kite plan.** See [Plans & trial](/pricing-credits/plans-and-trial) or [kite.ai](https://kite.ai/) for current plan options. +- **Publish your site first.** The **Add custom domain** button stays disabled until you publish. See [How to publish](/publishing/how-to-publish). +- **Be on Growth or Business, or in the trial.** Custom domains require an active subscription. See [Plans & Pricing](/pricing-credits/plans-and-trial). - Have your domain handy if you already own one. It does not matter where you bought it. See [Connect a domain from your registrar](/custom-domains/registrar-guides). ## Open the publish panel @@ -21,7 +21,7 @@ This article shows you how to point your own domain (like `yourbusiness.com`) at If the button is grayed out, publish your site first. You will see the hint: *"Publish your website to add a custom domain"*. -If Kite asks you to upgrade, follow the on-screen steps to choose a plan that includes custom domains. +If Kite asks you to upgrade, follow the on-screen steps to choose Growth or Business. ![Add custom domain button after publish](/img/docs/add-custom-domain-enabled.png) @@ -39,8 +39,8 @@ Kite gives you two options: ### Enter your domain 1. Click **Connect a domain you own**. -2. Type your domain name (for example, `example.com`). -3. Optional: check **I want to use a subdomain** if you want an address like `www.example.com` or `shop.example.com`. +2. Type your domain name (for example, `example.com`). Connecting the root domain covers `www.example.com` automatically. +3. Optional: check **I want to use a subdomain** if you want an address like `shop.example.com`. If you connect `www.example.com` this way, the bare `example.com` will not work, so connect the root domain unless you have a reason not to. 4. Click **Connect domain**. ![Connect your domain form](/img/docs/connect-your-domain.png) @@ -51,10 +51,10 @@ You only add a few settings at the company where you bought your domain. Kite wa ### Set up DNS with Entri -After you click **Connect domain**, the **Entri** modal opens. This is the tool Kite uses to set up your DNS. +After you click **Connect domain**, the **Entri** modal opens. This is the service Kite uses to set up your DNS. :::note What is Entri? -**Entri** is a service that connects to your domain provider and adds the right DNS records automatically, so you usually don't have to touch any technical settings yourself. +**Entri** connects to your domain provider and adds the right DNS records automatically, so you usually do not have to touch any technical settings yourself. ::: ![DNS setup guide](/img/docs/dns-setup-modal.png) @@ -63,60 +63,50 @@ You can finish setup in one of two ways: #### Method A: One-click setup with Entri (recommended) -This is the easiest path and works with most popular domain providers. - 1. In the **Entri** modal, find and select your domain provider from the list (for example, GoDaddy, Namecheap, or Cloudflare). 2. Sign in to your provider when prompted. This lets Entri add the DNS records for you. 3. Confirm the changes Entri shows you and let it apply them. -4. Close the modal when it reports success. -5. Back in Kite, you may need to **republish** your site for the domain to go fully live. See [How to publish](/publishing/how-to-publish). - -:::tip -If your provider is in the list, always try this method first. It avoids typing DNS records by hand and reduces mistakes. -::: +4. Close the modal when it reports success. Kite republishes your site for you. #### Method B: Manual DNS setup -Use this if your provider isn't listed in Entri, or if someone else manages your DNS. +Use this if your provider is not listed in Entri, or if someone else manages your DNS. 1. In the **Entri** modal, scroll to the **end of the providers list**. 2. Click **Go to our manual setup**. -3. Entri shows you all the DNS records you need to add. Keep this screen open. +3. Entri shows you all the DNS records to add. Keep this screen open. 4. Add those records in your domain provider's DNS settings (see [Connect a domain from your registrar](/custom-domains/registrar-guides) for where to find them). 5. Save the records at your provider. 6. When you have finished at your provider, confirm in Kite. -7. Back in Kite, **republish** your site if prompted. ##### Handing the records to someone else -If a colleague, web person, or IT contact manages your DNS, you don't have to do it yourself: - 1. On the manual setup screen, click **Forward instructions to a colleague**. 2. This generates a link that contains all the DNS records. -3. Send that link to whoever manages your DNS, and they can add the records for you. +3. Send that link to whoever manages your DNS. -##### DNS records you'll typically add +##### The records you will see -If you're adding records by hand, these are the values seen in real setups: +The website records are always these two: | Type | Host / Name | Value / Points to | |------|-------------|-------------------| | `A` | `@` | `76.76.21.21` | | `CNAME` | `www` | `cname.vercel-dns.com` | +You will also see a few **MX** and **TXT** records. Those let Kite send email on your domain's behalf (for example, campaigns from your team's address) and, on paid plans, verify your domain with Google Search Console. They sit on their own labels and do not touch your existing mailbox. See [Connecting a domain & keeping your email](/custom-domains/transfer-and-email). + :::note What these mean -- An **A record** points a domain to a server's numeric address (an IP address). The host `@` means the root of your domain (for example, `yourbusiness.com` with no `www`). -- A **CNAME record** points one name at another name. Here it points `www.yourbusiness.com` at Kite's hosting. +- An **A record** points a domain to a server's numeric address. The host `@` means the root of your domain. +- A **CNAME record** points one name at another name. Here it points `www.yourcompany.com` at Kite's hosting. ::: -:::caution Always confirm the exact values in Entri -Use the records that **Entri shows you** for your specific domain rather than copying these from memory. Values can change. The table above is a reference for what they tend to look like. +:::caution Always use the exact values in Entri +Use the records that **Entri shows you** for your specific domain rather than copying them from here. Values can change. ::: ## Buy a domain through Kite -If you do not own a domain yet, you can buy one directly in Kite: - 1. Under **Buy a new domain**, search for the name you want. 2. Pick an option marked **Available** and review the price and renewal cost. 3. Click **Confirm purchase**. @@ -129,27 +119,25 @@ Domain purchases are non-refundable. You are charged right away for the registra ## After you connect -After you connect or buy a domain, Kite shows a **Setting up** status while your new address spreads across the internet. +After you connect or buy a domain, Kite shows a notice while your new address spreads across the internet: -![Domain setting up status](/img/docs/domain-setting-up.png) +> Your domain is connecting. This usually takes a few minutes but can take up to 24 hours. -- This usually takes a few minutes. -- In some cases it can take up to 24 hours. +- Kite republishes your site automatically once the connection succeeds. - Try opening your domain in a browser to see if it is live. +- When setup is complete, the notice disappears and your custom domain becomes your site's main address. -> This domain is being set up across the internet. It usually takes a few minutes, but can take up to 24 hours. You can try opening the domain to see if it's live. - -When setup is complete, the status changes to **Connected** and your custom domain becomes your site's main address. +### Verification needed -- **Republish if prompted.** After connecting, your site may need a fresh publish for the domain to serve the latest version. +If your domain was previously used on another hosting account, the panel shows **Verification needed** and a TXT record to add at your DNS provider. For a root domain, both the bare domain and `www` need verifying. Add the record, wait a few minutes, and the notice clears. This is the most common reason a domain seems never to connect. :::info -Want to set up `www` and the root domain correctly, and avoid security warnings? See [www vs. Root Domain (and SSL)](/custom-domains/www-vs-root). +Want to understand how `www` and the root domain work together and avoid security warnings? See [www and Root Domain (and SSL)](/custom-domains/www-vs-root). ::: ## Disconnect a custom domain -To remove a custom domain from your site, go to your site's **Settings** and click **Disconnect custom domain**. Your site will go back to using its `yoursite.kite.space` address. +To remove a custom domain from your site, open your site's **Settings** and click **Disconnect custom domain**. Your site returns to its `yoursite.kite.space` address. Once a domain is connected, the **Add custom domain** button no longer appears in the publish panel; Settings is the only place to change it. To move a domain to a different site, see [Move, switch, or reuse a domain](/custom-domains/switch-or-reuse-domain). @@ -158,11 +146,11 @@ To move a domain to a different site, see [Move, switch, or reuse a domain](/cus | Issue | What to do | | --- | --- | | **Add custom domain** is disabled | Publish your site first | -| Upgrade prompt appears | Follow the upgrade steps shown in Kite, or see [Plans & trial](/pricing-credits/plans-and-trial) | +| Upgrade prompt appears | Choose Growth or Business, or see [Plans & Pricing](/pricing-credits/plans-and-trial) | +| **Verification needed** | Add the TXT record shown, for both root and `www` | | Setup was cancelled | Click **Connect domain** and start again | -| Domain not loading after 24 hours | Double-check that the settings at your domain provider match what Kite showed | +| Domain not loading after 24 hours | Check that the records at your domain provider match what Entri showed | -- **Domain still shows the old `.kite.space` address or a 404.** Try republishing, then wait for DNS to propagate. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). -- **"Domain already connected to another website."** The domain is attached to a different Kite app. Disconnect it there first, or contact support. See [Move, switch, or reuse a domain](/custom-domains/switch-or-reuse-domain). -- **"Connection Not Private" / SSL warning.** This often clears on its own as the security certificate is issued, especially once both `www` and root are set. See [www vs. Root Domain (and SSL)](/custom-domains/www-vs-root). -- **Changes aren't showing up.** This is usually DNS propagation or a needed republish. See [Changes not showing](/publishing/changes-not-showing). +- **Domain still shows a 404.** See [Troubleshoot a connected domain](/custom-domains/troubleshooting). +- **"Domain already connected to another website."** The domain is attached to a different site you still have. Disconnect it there first. See [Move, switch, or reuse a domain](/custom-domains/switch-or-reuse-domain). +- **"Connection Not Private" / SSL warning.** This usually clears on its own as the security certificate is issued. See [www and Root Domain (and SSL)](/custom-domains/www-vs-root). diff --git a/website/docs/custom-domains/registrar-guides.md b/website/docs/custom-domains/registrar-guides.md index 0e3a252..0ff43b7 100644 --- a/website/docs/custom-domains/registrar-guides.md +++ b/website/docs/custom-domains/registrar-guides.md @@ -8,7 +8,7 @@ description: Find your DNS settings at popular domain registrars so you can poin It doesn't matter where you bought your domain. What matters is that its DNS points to Kite. This article shows you where the DNS settings live at the most common registrars so you can add the records Kite needs. :::note Registrar vs. DNS -Your **registrar** is the company you bought the domain from. **DNS** is the set of records that tell browsers where to send visitors. You don't move the domain anywhere — you just edit its DNS records to point at Kite. +Your **registrar** is the company you bought the domain from. **DNS** is the set of records that tell browsers where to send visitors. You don't move the domain anywhere. You just edit its DNS records to point at Kite. ::: ## The general process @@ -18,7 +18,7 @@ No matter which registrar you use, the steps are the same: 1. Connect your domain in Kite first. See [Connect a custom domain](/custom-domains/connect-a-custom-domain). 2. If the one-click **Entri** flow supports your provider, sign in and let it do the work. 3. If you're doing it manually, log in to your registrar, open its DNS settings, and add the records Entri shows you. -4. Save, then return to Kite and **republish** if prompted. +4. Save. Kite republishes your site for you once the connection succeeds. :::tip Use Entri's one-click flow when you can Most of the registrars below are supported in Entri, which adds the records for you. Only dig into the menus below if your provider isn't listed or someone else manages your DNS. @@ -64,7 +64,7 @@ Google Domains was migrated to **Squarespace**, so if you bought a domain throug 3. Add the records from Entri. :::caution Common mistake: editing the wrong place when Cloudflare is in the middle -If your domain's **nameservers** are pointed (delegated) to Cloudflare, then Cloudflare is in charge of your DNS — not the registrar you originally bought the domain from. In that case you must edit the records **inside Cloudflare**, not at the original registrar. Records added at the old registrar will be ignored. +If your domain's **nameservers** are pointed (delegated) to Cloudflare, then Cloudflare is in charge of your DNS, not the registrar you originally bought the domain from. In that case you must edit the records **inside Cloudflare**, not at the original registrar. Records added at the old registrar will be ignored. A **nameserver** is the server that answers DNS questions for your domain. Whichever service your nameservers point to is the one you edit. ::: @@ -75,7 +75,7 @@ If you're not sure, look at your domain's nameservers at your registrar. If they ## My registrar isn't listed -You can still connect manually. Log in to your registrar, find its DNS or "DNS zone" settings, and add the records that Entri shows you. The record types are standard (`A` and `CNAME`), so any registrar can host them. See the record reference in [Connect a custom domain](/custom-domains/connect-a-custom-domain#dns-records-youll-typically-add). +You can still connect manually. Log in to your registrar, find its DNS or "DNS zone" settings, and add the records that Entri shows you. The record types are standard (`A`, `CNAME`, `MX`, and `TXT`), so any registrar can host them. See the record reference in [Connect a custom domain](/custom-domains/connect-a-custom-domain#the-records-you-will-see). ## Troubleshooting diff --git a/website/docs/custom-domains/switch-or-reuse-domain.md b/website/docs/custom-domains/switch-or-reuse-domain.md index 4386457..22268a0 100644 --- a/website/docs/custom-domains/switch-or-reuse-domain.md +++ b/website/docs/custom-domains/switch-or-reuse-domain.md @@ -1,66 +1,49 @@ --- title: Move, Switch, or Reuse a Domain Across Sites -description: Change which Kite site a domain points to, reconnect a domain after deleting an app, and fix a domain that's blocked as "already connected." +description: Change which Kite site a domain points to, reuse a domain after deleting a site, and fix the "already connected to another website" message. --- # Move, Switch, or Reuse a Domain Across Sites -Sometimes you need to move a domain you already connected — maybe you rebuilt your site as a new app, or you want one domain to point at a different site. This article covers changing a domain, reconnecting it after deleting the original app, and what to do when Kite says the domain is "already connected to another website." +Sometimes you need to move a domain you already connected. Maybe you rebuilt your site as a new project, or you want one domain to point at a different site. This article covers each case. -## Change the domain on a site - -If you want a site to use a different domain than the one it currently has: - -1. Open the site in Kite. -2. Click **Publish** in the top-right corner. -3. Go to the custom domain settings (where you originally connected the domain). -4. Disconnect or remove the old domain, then add the new one with **Add Custom Domain** → type the domain → **Connect Domain**. -5. **Republish** if prompted. - -See [Connect a custom domain](/custom-domains/connect-a-custom-domain) for the full connection flow. - -## Reuse a domain on a different (or rebuilt) site +## The one rule -A domain can only be actively connected to **one** Kite site at a time. If you want to point it at a different site, you first have to free it from the old one. +A domain can be connected to **one** Kite site at a time, and a site can have **one** custom domain. To move a domain, disconnect it from the old site first, then connect it on the new one. -1. Open the **old** site/app that currently holds the domain. -2. Disconnect the domain there. -3. Open the **new** site and connect the domain following [Connect a custom domain](/custom-domains/connect-a-custom-domain). -4. **Republish** the new site. +## Change the domain on a site -## "Domain already connected to another website" +1. Open the site in Kite and go to **Settings**. +2. Click **Disconnect custom domain**. The site returns to its `kite.space` address. +3. Click **Publish** in the top-right corner, then **Add custom domain**, and connect the new domain. See [Connect a custom domain](/custom-domains/connect-a-custom-domain). -This is the most common blocker when reusing a domain. It usually happens when: +## Move a domain to a different site -- You deleted the original app **without disconnecting the domain first**, so Kite still has the domain tied to that old (now-gone) app. -- The domain is still attached to another site you own. +1. Open the **old** site, go to **Settings**, and click **Disconnect custom domain**. +2. Open the **new** site and connect the domain from its publish panel. +3. Kite republishes the new site once the connection succeeds. -What to do: +## Reuse a domain after deleting a site -1. If the old app still exists, open it and **disconnect the domain** there, then connect it on the new site. -2. If you already **deleted** the old app and can no longer disconnect it, the domain may stay flagged as in use. In that case, **contact support** to have it released. +Deleting a website releases its domain automatically, so you can connect the domain to another site straight away. You do not need to disconnect first or ask support. -:::tip Disconnect before you delete -To avoid this entirely, always disconnect a custom domain from a site **before** you delete that app. It saves you from a stuck "already connected" state later. -::: +## "Domain already connected to another website" -## Forwarding still shows the `.kite.space` URL in the browser +This message means the domain is attached to a different site that still exists in your account. Open that site, go to **Settings**, click **Disconnect custom domain**, and try again. -If you connected your domain but the browser address bar still shows the `your-site.kite.space` URL (instead of your custom domain), that's a sign your domain is **forwarding/redirecting** to the Kite URL rather than being served directly on your domain. +## The browser still shows the `.kite.space` URL -What to check: +If you connected your domain but the address bar still shows `your-site.kite.space`, your registrar is **forwarding** the domain to the Kite URL instead of **pointing** it with DNS records. -1. Make sure you used Kite's DNS records (`A` / `CNAME`) rather than a **URL forwarding / redirect** option at your registrar. URL forwarding sends visitors to the `.kite.space` address and shows it in the bar. -2. Remove any registrar-side forwarding rule for the domain. -3. Re-add the proper DNS records from Entri. See [Connect a custom domain](/custom-domains/connect-a-custom-domain). -4. **Republish** and allow time for DNS to propagate. +1. Remove any URL forwarding or redirect rule for the domain at your registrar. +2. Add the DNS records from Entri. See [Connect a custom domain](/custom-domains/connect-a-custom-domain). +3. Allow time for DNS to propagate. -:::note Forwarding vs. pointing -**Forwarding** bounces visitors to another address (and shows that address). **Pointing** (with DNS records) serves your site directly on your own domain, so the address bar keeps showing your domain. You want pointing. +:::note Forwarding versus pointing +**Forwarding** bounces visitors to another address (and shows that address). **Pointing** with DNS records serves your site directly on your own domain. You want pointing. ::: ## Troubleshooting -- **Domain shows a 404 or an old site after switching.** The domain may still be attached to the old deployment. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). -- **Stuck on "already connected."** Disconnect from the old app, or contact support if the app was deleted. -- **Changes not appearing after switching.** Usually DNS propagation or a needed republish. See [Changes not showing](/publishing/changes-not-showing). +- **Domain shows a 404 or an old site after switching.** Propagation may still be in progress, or a stale record is in place. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). +- **Changes not appearing after switching.** Usually DNS propagation. See [Changes not showing](/publishing/changes-not-showing). diff --git a/website/docs/custom-domains/transfer-and-email.md b/website/docs/custom-domains/transfer-and-email.md index ade1452..f710aaa 100644 --- a/website/docs/custom-domains/transfer-and-email.md +++ b/website/docs/custom-domains/transfer-and-email.md @@ -1,48 +1,48 @@ --- -title: Transferring a Domain & Keeping Your Email -description: How connecting a domain to Kite affects your registrar and your domain-linked email — and what stays exactly the same. +title: Connecting a Domain & Keeping Your Email +description: How connecting a domain to Kite affects your registrar and your domain-linked email, which records Kite adds, and what stays exactly the same. --- -# Transferring a Domain & Keeping Your Email +# Connecting a Domain & Keeping Your Email -A common worry when connecting a domain is "Will I lose my email?" or "Do I have to move my whole domain to Kite?" The short answer: you keep your domain where it is, and your email keeps working. This article explains exactly what changes and what doesn't. +A common worry when connecting a domain is "Will I lose my email?" or "Do I have to move my whole domain to Kite?" The short answer: you keep your domain where it is, and your email keeps working. This article explains exactly what changes and what does not. -## Kite doesn't take over your domain +## Kite does not take over your domain -Kite does **not** take over full registration or management of your domain from your registrar. Your domain stays registered exactly where it is today (GoDaddy, Squarespace, Namecheap, and so on). To connect it to your site, you only **point its DNS** at Kite — you don't transfer ownership. +Kite does not take over registration or management of your domain from your registrar. Your domain stays registered where it is today (GoDaddy, Squarespace, Namecheap, and so on). To connect it to your site, you point its DNS at Kite. You do not transfer ownership. -:::note What this means in plain terms -You're not handing your domain to Kite. You're leaving it where you bought it and just changing a couple of DNS records so your website loads from Kite. -::: +## Your existing email is not affected -## Your email is not affected +Your domain-linked email (for example, `you@yourcompany.com`) keeps working. Email is controlled by **MX records**, and Kite does not change the MX records for your domain's root. -Your domain-linked email (for example, `you@yourbusiness.com`) keeps working. Here's why: email is controlled by different DNS records (called **MX records**) than your website. When you connect to Kite, only the **website** records change — your **mail** records stay exactly as they are. +## Which records Kite adds -:::note What is an MX record? -An **MX record** tells the internet which server handles email for your domain. Your website uses `A` and `CNAME` records; your email uses `MX` records. They live side by side and don't interfere with each other. -::: +The DNS setup shows more than the two website records: + +- **A and CNAME records** point your domain at your Kite site. +- **MX and TXT records on their own labels** let Kite send email on your domain's behalf (for example, outreach and campaigns from your team's address). Because they live on separate labels, they sit alongside your existing mail records without interfering. +- **A TXT record for Google Search Console**, on paid plans, so Kite can verify your domain and submit your sitemap. -:::caution Don't delete records you don't recognize -When you add the Kite website records, **leave your existing MX records (and any other mail-related records) in place**. The mistake that causes email problems is deleting mail records, not connecting a website. If you only add the `A` and `CNAME` records Kite asks for, your email is untouched. +:::caution Add records; do not delete the ones you have +The mistake that causes email problems is deleting your existing MX records, not adding Kite's. Add what Entri shows and leave everything else in place. ::: ## Answering the common worries **Do I have to stop paying my current registrar?** -No. Your domain registration stays with them, so you keep renewing it there as usual. Connecting to Kite doesn't cancel or move that. +No. Your domain registration stays with them, so you keep renewing it there as usual. **Does connecting cost extra on top of my domain?** -Connecting a custom domain is part of a Kite paid plan. You still pay your registrar separately for the domain itself, just like before. See [Plans & trial](/pricing-credits/plans-and-trial). +Custom domains are included in Growth and Business. You still pay your registrar separately for the domain itself. See [Plans & Pricing](/pricing-credits/plans-and-trial). **Will my email go down during the change?** -It shouldn't. Because you're only changing website records and leaving mail records alone, your inbox keeps receiving mail throughout. The only thing that "switches over" is which site loads when someone visits your domain. +No. Your mail records are left alone, so your inbox keeps receiving mail throughout. -**What if I'm using a separate email provider (like Google Workspace or Microsoft 365)?** -That's fine — those services rely on your MX records, which you're not changing. Keep them as they are and only add the website records Kite asks for. +**I use Google Workspace or Microsoft 365.** +That is fine. Those services rely on your existing MX records, which you are not changing. ## Troubleshooting -- **Worried email stopped after connecting.** Check that your `MX` records are still present at your DNS provider. If they were removed, re-add them from your mail provider's instructions. See also [Email sending issues](/troubleshooting/email-sending). +- **Worried email stopped after connecting.** Check that your original `MX` records are still present at your DNS provider. If they were removed, re-add them from your mail provider's instructions. - **Not sure where your DNS is managed.** See [Connect a domain from your registrar](/custom-domains/registrar-guides), including the note about Cloudflare nameservers. -- **Website connected but not loading.** That's a website issue, not an email one. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). +- **Website connected but not loading.** See [Troubleshoot a connected domain](/custom-domains/troubleshooting). diff --git a/website/docs/custom-domains/troubleshooting.md b/website/docs/custom-domains/troubleshooting.md index 8b66873..ebe0756 100644 --- a/website/docs/custom-domains/troubleshooting.md +++ b/website/docs/custom-domains/troubleshooting.md @@ -1,79 +1,70 @@ --- title: Troubleshoot a Connected Domain -description: Fix common custom-domain problems on Kite — 404 errors, an old site showing, SSL warnings, "already connected," and changes not appearing. +description: Fix common custom-domain problems on Kite, including 404 errors, verification needed, an old site showing, SSL warnings, and "already connected." --- # Troubleshoot a Connected Domain -If your domain is connected but something isn't right, this article maps the symptom you're seeing to a fix. Most domain issues come down to one of three things: the domain needs reattaching to the current deployment, an old DNS record is still in place, or DNS just hasn't finished propagating. +If your domain is connected but something is not right, this article maps the symptom you are seeing to a fix. Most domain issues come down to one of three things: the domain needs verifying, an old DNS record is still in place, or DNS has not finished propagating. :::note DNS takes time -**Propagation** is how long DNS changes take to spread across the internet — usually minutes, but sometimes up to about 48 hours. Before assuming something is broken, give a recent change time to settle. +**Propagation** is how long DNS changes take to spread across the internet: usually a few minutes, sometimes up to 24 hours. Before assuming something is broken, give a recent change time to settle. ::: -## Symptom → fix +## Symptom and fix | Symptom | Likely cause | Fix | |---------|--------------|-----| -| **404 / DEPLOYMENT_NOT_FOUND** | Domain isn't attached to your current live deployment | Republish, then reattach the domain to the current deployment | +| **Verification needed** in the panel | The domain was used on another hosting account | Add the TXT record shown, for both root and `www` | +| **404 / DEPLOYMENT_NOT_FOUND** | DNS points at Kite but the domain is not attached to a live deployment | Make an edit and publish; if it persists, disconnect and reconnect the domain | | **Shows an old or different site** | A DNS record (often `CNAME`) still points somewhere else | Update the records to Kite's values and remove old ones | -| **"Connection Not Private" / SSL error** | Certificate not issued yet, or only one of www/root set | Give it time; make sure both `www` and root are configured | -| **"Domain already connected to another website"** | Domain still tied to a different/deleted Kite app | Disconnect from the old app, or contact support | -| **Changes not appearing** | DNS propagation or a missing republish | Wait for propagation; republish | +| **"Connection Not Private" / SSL error** | Certificate not issued yet, or one of the www/root records is missing | Give it time; check both records | +| **"Domain already connected to another website"** | Domain is attached to another site you still have | Disconnect it in that site's Settings | +| **Changes not appearing** | DNS propagation or browser cache | Wait; hard-refresh | -## 404 or DEPLOYMENT_NOT_FOUND +## Verification needed + +If your domain was previously connected to another hosting account, Kite cannot attach it until you prove you control it. The panel shows **Verification needed** and a TXT record. Add it at your DNS provider (for a root domain, both the bare domain and `www` need it), wait a few minutes, and the notice clears. -Your domain reaches Kite, but you get a 404 page or an error mentioning **DEPLOYMENT_NOT_FOUND**. This means the domain isn't pointing at a current, live version of your site. +## 404 or DEPLOYMENT_NOT_FOUND -1. Open your site in Kite and click **Publish** to republish. -2. If it persists, reattach the domain to the current deployment: go to the custom domain settings, disconnect the domain, then reconnect it with **Add Custom Domain** → **Connect Domain**. -3. Allow a little time, then reload. +Your domain reaches Kite, but you get a 404 page or an error mentioning **DEPLOYMENT_NOT_FOUND**. -See [Connect a custom domain](/custom-domains/connect-a-custom-domain). +1. Make a small edit in the editor and click **Publish**. +2. If it persists, open your site's **Settings**, click **Disconnect custom domain**, then reconnect it from the publish panel. +3. Allow a few minutes, then reload. ## Domain shows an old or different site -If your domain loads a previous site (or someone else's), a DNS record is still pointing at the old host. +A DNS record is still pointing at the old host. 1. Open your DNS settings at your registrar (see [Connect a domain from your registrar](/custom-domains/registrar-guides)). 2. Check your `A` and `CNAME` records. A leftover `CNAME` pointing at an old host is the usual culprit. -3. Replace them with the exact values Entri shows you, and delete any stale records. -4. **Republish** and wait for propagation. +3. Replace them with the exact values Entri showed you, and delete any stale records. +4. Wait for propagation. :::caution Cloudflare in the middle If your nameservers point to Cloudflare, edit the records **in Cloudflare**, not at the original registrar. See the note in [Connect a domain from your registrar](/custom-domains/registrar-guides). ::: -## SSL "Connection Not Private" / broken certificate - -The padlock is missing or the browser warns the connection isn't private. +## SSL "Connection Not Private" -1. **Give it time.** SSL certificates are issued automatically after the domain connects and can take a little while to appear. -2. **Make sure both `www` and the root are configured.** If only one is set up, the other may throw a certificate warning. See [www vs. Root Domain (and SSL)](/custom-domains/www-vs-root). -3. If it still fails after the records are correct and you've waited, contact support. +1. **Give it time.** Certificates are issued automatically after the domain connects and can take a little while. +2. **Check both records.** If only the root or only `www` is set up, the other may throw a warning. See [www and Root Domain (and SSL)](/custom-domains/www-vs-root). +3. If it still fails after the records are correct and you have waited, open **Chat with us**. ## "Domain already connected to another website" -The domain is still attached to a different Kite app — often one you deleted without disconnecting the domain first. - -1. If the old app still exists, open it and disconnect the domain there. -2. If you deleted the old app, contact support to release the domain. -3. Then reconnect on your current site. - -Full details: [Move, switch, or reuse a domain](/custom-domains/switch-or-reuse-domain). +The domain is attached to a different site that still exists in your account. Open that site, go to **Settings**, click **Disconnect custom domain**, then reconnect on your current site. Deleting a site releases its domain automatically. See [Move, switch, or reuse a domain](/custom-domains/switch-or-reuse-domain). ## Changes not appearing -You updated your site or DNS but nothing changed in the browser. - -1. **Republish** your site so the latest version is live. -2. Wait for DNS propagation (up to ~48 hours for DNS changes). -3. Try a hard refresh or a private/incognito window to rule out browser caching. - -See [Changes not showing](/publishing/changes-not-showing). +1. Make an edit and **Publish** so the latest version is live. +2. Wait for DNS propagation (up to 24 hours). +3. Hard-refresh or use a private window to rule out browser caching. ## Still stuck? - Re-read the connection steps in [Connect a custom domain](/custom-domains/connect-a-custom-domain). -- Confirm you're editing DNS in the right place in [Connect a domain from your registrar](/custom-domains/registrar-guides). -- For anything that won't clear after correct setup plus propagation time, contact support. +- Confirm you are editing DNS in the right place in [Connect a domain from your registrar](/custom-domains/registrar-guides). +- For anything that will not clear after correct setup plus propagation time, open **Chat with us** in Kite. diff --git a/website/docs/custom-domains/www-vs-root.md b/website/docs/custom-domains/www-vs-root.md index 903281d..af03f59 100644 --- a/website/docs/custom-domains/www-vs-root.md +++ b/website/docs/custom-domains/www-vs-root.md @@ -1,49 +1,35 @@ --- -title: www vs. Root Domain (and SSL) -description: Understand the difference between your root domain and www, pick a primary address, and avoid SSL "Connection Not Private" warnings. +title: www and Root Domain (and SSL) +description: How Kite serves both your root domain and www, why connecting the root is the right choice, and how to avoid "Connection Not Private" warnings. --- -# www vs. Root Domain (and SSL) +# www and Root Domain (and SSL) -Your domain can work with or without `www` at the front, and how you set this up affects both search ranking and the little padlock (SSL) in the browser. This article explains the difference and helps you pick a primary address so visitors always land in the right place — securely. +Your domain can be typed with or without `www` at the front. This article explains how Kite handles both and how to keep the padlock (SSL) working. -## Root vs. www: what's the difference? +## Root versus www -- **Root domain** (also called the **apex** or **naked** domain): your bare domain with nothing in front, like `yourbusiness.com`. -- **www subdomain**: the same domain with `www.` in front, like `www.yourbusiness.com`. +- **Root domain** (also called the **apex** or **naked** domain): your bare domain, like `yourcompany.com`. +- **www subdomain**: the same domain with `www.` in front, like `www.yourcompany.com`. -These are technically two different addresses. A visitor could type either one, so you want both to work and to lead to the same site. +These are technically two different addresses, so you want both to work and to lead to the same site. -:::note Why "apex"? -The root/apex domain is the top level of your name (`yourbusiness.com`). `www` is a subdomain that sits underneath it. Both can point to your Kite site. -::: - -## Pick a primary, redirect the other - -Best practice is to choose one as your **primary** address and have the other **redirect** to it. For example, choose `www.yourbusiness.com` as primary and have `yourbusiness.com` redirect to it (or the other way around). +## Connect the root and Kite covers both -Doing this matters for two reasons: +When you connect your root domain, Kite sets up both records (an `A` record for the root and a `CNAME` for `www`) and attaches both addresses to your site. Visitors who type either one reach your site, and the address you typed when connecting is treated as the canonical one for search engines. There is no separate "primary" setting to choose. -1. **SEO / duplicate content.** If `www` and the root both serve your site as separate addresses, search engines can see them as two copies of the same content, which can dilute your ranking. A redirect keeps everything pointing at one canonical address. -2. **SSL certificate coverage.** SSL is what gives you `https://` and the padlock. If only one of the two addresses is configured, visitors who reach the other one may see a **"Connection Not Private"** warning because the security certificate doesn't cover that exact address. - -:::caution The classic "www shows Connection Not Private" problem -A very common symptom is that the root domain works fine but `www` shows a security warning (or vice versa). This usually means only one of the two was set up. Make sure **both** the root and the `www` records are connected so the certificate covers both. -::: +If you connect `www.yourcompany.com` as a subdomain instead, only `www` is set up, and the bare `yourcompany.com` will not work. Connect the root unless you have a specific reason not to. -## How to set both up in Kite +## SSL -1. Connect your domain following [Connect a custom domain](/custom-domains/connect-a-custom-domain). -2. Make sure both records are in place — typically an `A` record for the root (`@`) and a `CNAME` for `www`. The one-click **Entri** flow normally adds both for you. -3. **Republish** your site if prompted. -4. Give SSL a little time. The certificate is issued automatically after the domain connects, and the padlock may take a short while to appear. +SSL is what gives you `https://` and the padlock. Kite issues the certificate automatically after the domain connects. It can take a little while to appear. -:::tip -If you're adding records by hand, use the exact values Entri shows you. See the record reference in [Connect a custom domain](/custom-domains/connect-a-custom-domain#dns-records-youll-typically-add). +:::caution "www shows Connection Not Private" +If the root works but `www` shows a security warning (or the reverse), one of the two records is missing at your DNS provider. Check that both the root (`@`) record and the `www` record match what Entri showed, then give the certificate a few minutes. ::: ## Troubleshooting -- **`www` works but root doesn't (or the reverse).** One of the two records is missing. Add both the root (`@`) and `www` records. -- **"Connection Not Private" / SSL warning.** Often clears on its own once the certificate is issued and both addresses are configured. Give it time. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). -- **Still seeing the wrong page after redirect.** This can be DNS propagation or a stale record. See [Changes not showing](/publishing/changes-not-showing). +- **`www` works but root does not (or the reverse).** Add the missing record. See [Connect a custom domain](/custom-domains/connect-a-custom-domain#the-records-you-will-see). +- **"Connection Not Private" / SSL warning.** Usually clears on its own once the certificate is issued and both records are in place. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). +- **You connected www as a subdomain and the bare domain does not work.** Disconnect it in your site's **Settings** and connect the root domain instead. diff --git a/website/docs/forms-integrations/README.md b/website/docs/forms-integrations/README.md index f2476d9..5b4d96d 100644 --- a/website/docs/forms-integrations/README.md +++ b/website/docs/forms-integrations/README.md @@ -1,32 +1,27 @@ --- title: Forms & Integrations -description: Add forms to capture leads and connect your Kite site to the third-party tools you already use. +description: Add contact forms that feed a Leads inbox, read your site's analytics, add third-party scripts, and connect Kite to GitHub, social networks, email services, and more than 3,000 integrations. --- # Forms & Integrations -Your website does more than look good — it can collect messages, grow your mailing list, chat with visitors, and plug into the tools you already use. This section covers how to add forms and connect outside services to your Kite site. +Your website does more than look good. It collects leads, tracks visitors, and plugs into the services your team already uses. This section covers forms, analytics, scripts, and the Integrations page. ## What you can do here -- **Add contact forms and newsletter signups** so visitors can reach you or subscribe. -- **Add a chat widget** (like Tawk.to) and other embed scripts (like HubSpot). -- **Track visitors** with Kite's built-in analytics or an external tool like Google Analytics. -- **Connect other tools** through integrations. +- **Add contact forms and newsletter signups.** Submissions are emailed to your site's contact address and saved in the Leads inbox. +- **Read your analytics.** Every site has built-in analytics with a Leads inbox, a Discoverability tab, and an Errors tab. +- **Add third-party scripts** such as a chat widget or a tracking snippet. +- **Connect services** from the Integrations page: GitHub, social networks, email services, an external CMS, and a catalog of more than 3,000 integrations. ## In this section -- [Contact Forms & Lead Capture](/forms-integrations/contact-forms) — add a form and decide where submissions go. -- [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts) — add live chat and third-party embed scripts. -- [Site Analytics](/forms-integrations/analytics) — see who visits and connect external analytics. -- [Integrations](/forms-integrations/integrations) — connect tools like GitHub to your site or app. - -:::tip Publish first -Many of these features only work on your live, published site — not in the editor preview. If something looks broken, [publish your site](/publishing/how-to-publish) and test again. -::: +- [Contact Forms & Lead Capture](/forms-integrations/contact-forms): add a form, set the contact email, and find submissions in the Leads inbox. +- [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts): add live chat and third-party embed scripts. +- [Site Analytics](/forms-integrations/analytics): the four tabs and what each plan sees. +- [Integrations](/forms-integrations/integrations): the Integrations page, GitHub sync, social networks, email, and CMS connections. ## Related - [Publishing your site](/publishing/) -- [Email sending issues](/troubleshooting/email-sending) -- [Custom domains](/custom-domains/) +- [What Kite can do](/capabilities/) diff --git a/website/docs/forms-integrations/analytics.md b/website/docs/forms-integrations/analytics.md index a360eed..e6b0e49 100644 --- a/website/docs/forms-integrations/analytics.md +++ b/website/docs/forms-integrations/analytics.md @@ -1,73 +1,52 @@ --- title: Site Analytics -description: Use Kite's built-in visitor analytics and connect external tools like Google Analytics to understand your traffic. +description: Every Kite site has built-in analytics with four tabs (Site insights, Leads inbox, Discoverability, Errors). Learn what each plan sees and how to connect an external tool. --- # Site Analytics -Analytics tell you how many people visit your site, which pages they look at, and where they come from. Kite includes built-in analytics, and you can also connect an external tool if you prefer. +Every Kite-hosted site has built-in analytics. Open your site in the browser workspace and choose **Analytics** to see four tabs. -## Kite's built-in analytics +## The four tabs -Kite tracks basic visitor activity on your published site so you can see how it's performing — typically things like visits, page views, and top pages. +- **Site insights.** On paid plans: pageviews, pages per visit, bounce rate, time on site, top pages, referrers, countries, devices, events, and funnels. On the Free plan: a single visitor count. +- **Leads inbox.** Every contact form submission. Free-plan teams see the count; paid plans see the submissions. See [Contact forms](/forms-integrations/contact-forms). +- **Discoverability.** Page speed scores, an AI analysis of how findable your site is, and a **Review and fix** button that hands the findings to Kite. See [SEO & discoverability](/seo/). +- **Errors.** Problems visitors hit on the live site. -1. Open your project in Kite. -2. Find the **Analytics** area for your site. -3. Review your visitor numbers and most-visited pages. - - +Kite's analytics are powered by a dedicated PostHog project for each site. Reads are cached, so a short delay before a visit shows up is normal. :::tip Publish before you measure -Analytics only count visits to your **live, published** site. If you haven't published yet, or you only viewed the editor preview, you won't see meaningful numbers. See [How to publish](/publishing/how-to-publish). +Analytics count visits to your **live, published** site. Editor previews are not counted. ::: -## Connect external analytics - -Prefer a tool you already use? You can add an external analytics service by embedding its tracking script. - -Commonly requested tools: - -- **Google Analytics** (GA4) -- **PostHog** -- **Mixpanel** +## Connect an external analytics tool - +Prefer a tool you already use? Add its tracking script the same way as any embed script. -To connect one: +1. Create your property in the analytics tool and copy its tracking snippet or measurement ID. +2. Ask Kite to add it, for example, "Add this Google Analytics tag to every page," and paste it. +3. Publish your site. +4. Use the tool's real-time view to confirm your visit is recorded. -1. Create your property/project in the analytics tool and copy its **tracking snippet** or measurement ID. -2. In the Kite editor, ask Kite to add the snippet — for example, "Add this Google Analytics tag to every page," and paste it. -3. [Publish your site](/publishing/how-to-publish). -4. In the analytics tool, use its real-time view to confirm your visit is being recorded. - -:::note Adding scripts -External analytics are added the same way as any embed script. If the tracker doesn't load, it may be blocked by your site's Content Security Policy — see [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts). -::: +See [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts). ## "My visitor count looks wrong or too low" -A lower-than-expected number is usually normal, not a bug. Common reasons: - -- **You only just published.** It can take time before visits show up, and a brand-new site simply has few visitors. -- **Your own visits may not count.** Some analytics filter out repeat visits from you, the owner. -- **Preview views don't count.** Only your published site is tracked. -- **Ad blockers and privacy tools** stop some visitors from being counted — so real traffic is often a bit higher than analytics show. This affects every analytics tool, not just Kite. -- **Two tools won't match exactly.** Kite's built-in numbers and Google Analytics use different methods, so their totals will differ. That's expected. +- **You only just published.** A brand-new site has few visitors, and reads are cached briefly. +- **Preview views do not count.** +- **Ad blockers and privacy tools** stop some visitors from being counted, so real traffic is often a bit higher than analytics show. This affects every analytics tool. +- **Two tools will not match exactly.** Kite's numbers and Google Analytics use different methods. :::tip Compare trends, not single numbers -Don't obsess over one day's count. Watch the trend over weeks — is traffic growing, steady, or dropping? That's the useful signal. +Watch the trend over weeks. Is traffic growing, steady, or dropping? That is the useful signal. ::: -## Troubleshooting - -**No data at all.** -Confirm your site is [published](/publishing/how-to-publish) and that you (or a test visitor) actually loaded the live URL. Give it a little time, then check again. +## Ask Kite about your numbers -**External tracker isn't recording.** -Verify the snippet is complete and the measurement ID is correct, check for a CSP/blocked-script error in your browser console, and ask Kite to allow the tracker's domain if needed. See [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts). +You can also ask Kite in Slack: "What did the comparison page do for traffic this week?" Kite reads the analytics and answers. See [Conversion work](/capabilities/conversion-fixes). ## Related -- [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts) -- [SEO basics](/seo/seo-basics) -- [How to publish](/publishing/how-to-publish) +- [Contact Forms & Lead Capture](/forms-integrations/contact-forms) +- [SEO & discoverability](/seo/) diff --git a/website/docs/forms-integrations/chat-and-scripts.md b/website/docs/forms-integrations/chat-and-scripts.md index 6ca2c10..ca9b41e 100644 --- a/website/docs/forms-integrations/chat-and-scripts.md +++ b/website/docs/forms-integrations/chat-and-scripts.md @@ -1,87 +1,57 @@ --- title: Chat Widgets & Custom Scripts -description: Add a live chat widget like Tawk.to, embed third-party scripts like HubSpot, and remove a chat widget if it won't go away. +description: Add a live chat widget like Tawk.to or an embed script like a HubSpot tracker to your Kite site, and remove one cleanly. --- # Chat Widgets & Custom Scripts -Want a live chat bubble in the corner of your site, or a marketing tool's tracking snippet? You can add third-party widgets and scripts to your Kite site. Here's how — and how to clean them up if one sticks around. +Want a live chat bubble in the corner of your site, or a marketing service's tracking snippet? You can add third-party widgets and scripts to your Kite site. Here is how to add them, and how to remove one. ## Add a chat widget (for example, Tawk.to) -Most chat tools give you a small snippet of code to paste into your website. - 1. Create an account with your chat provider (for example, [Tawk.to](https://www.tawk.to/)) and set up your chat widget there. 2. Copy the **embed code** (a `