From 73db1a5953ce0a16d7a9bccc7e7232485428cf20 Mon Sep 17 00:00:00 2001 From: Stacey Levine Date: Thu, 11 Jun 2026 18:11:28 -0400 Subject: [PATCH] docs: add initial Kite help center MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a task-oriented help center covering the most common user questions mined from Kite support, feedback, and issues Slack channels. Sections: Get Started, Building & Editing, Publishing, Custom Domains & DNS, SEO & Discoverability, Forms & Integrations, Plans/Pricing/Credits, Account & Settings, and Troubleshooting (49 articles + welcome page), wired into a manual sidebar. Drafts are sourced from real support conversations rather than product spec. Inferred specifics (prices, plan names, exact UI paths, DNS values) are marked with comments for product review before publish. Verified with `docusaurus build` (onBrokenLinks: throw) — all cross-links resolve. Co-Authored-By: Claude Opus 4.8 (1M context) --- website/docs/account/README.md | 30 +++++ website/docs/account/delete-account.md | 68 ++++++++++++ website/docs/account/export-your-site.md | 55 +++++++++ website/docs/account/login-and-signup.md | 72 ++++++++++++ website/docs/building/README.md | 35 ++++++ website/docs/building/editing-your-site.md | 67 +++++++++++ website/docs/building/fonts-and-media.md | 67 +++++++++++ website/docs/building/images-and-logos.md | 75 +++++++++++++ website/docs/building/pages-and-navigation.md | 70 ++++++++++++ website/docs/building/responsive-design.md | 51 +++++++++ .../building/templates-and-duplicating.md | 71 ++++++++++++ website/docs/custom-domains/README.md | 37 +++++++ .../custom-domains/connect-a-custom-domain.md | 95 ++++++++++++++++ .../docs/custom-domains/registrar-guides.md | 83 ++++++++++++++ .../custom-domains/switch-or-reuse-domain.md | 66 +++++++++++ .../docs/custom-domains/transfer-and-email.md | 48 ++++++++ .../docs/custom-domains/troubleshooting.md | 79 +++++++++++++ website/docs/custom-domains/www-vs-root.md | 49 +++++++++ website/docs/forms-integrations/README.md | 32 ++++++ website/docs/forms-integrations/analytics.md | 73 ++++++++++++ .../forms-integrations/chat-and-scripts.md | 87 +++++++++++++++ .../docs/forms-integrations/contact-forms.md | 82 ++++++++++++++ .../docs/forms-integrations/integrations.md | 62 +++++++++++ website/docs/get-started/README.md | 22 ++++ website/docs/get-started/how-kite-works.md | 61 ++++++++++ website/docs/get-started/quickstart.md | 65 +++++++++++ website/docs/intro.md | 30 ++++- website/docs/pricing-credits/README.md | 38 +++++++ website/docs/pricing-credits/buy-credits.md | 46 ++++++++ .../docs/pricing-credits/how-credits-work.md | 69 ++++++++++++ .../pricing-credits/manage-subscription.md | 57 ++++++++++ .../docs/pricing-credits/plans-and-trial.md | 54 +++++++++ .../docs/pricing-credits/remove-kite-badge.md | 42 +++++++ website/docs/publishing/README.md | 28 +++++ .../docs/publishing/changes-not-showing.md | 47 ++++++++ website/docs/publishing/how-to-publish.md | 37 +++++++ website/docs/publishing/publish-failures.md | 57 ++++++++++ website/docs/publishing/unpublish.md | 35 ++++++ website/docs/publishing/your-kite-url.md | 42 +++++++ website/docs/seo/README.md | 47 ++++++++ website/docs/seo/migrate-existing-site.md | 64 +++++++++++ website/docs/seo/seo-basics.md | 76 +++++++++++++ website/docs/seo/sitemap-and-robots.md | 67 +++++++++++ website/docs/seo/social-previews.md | 40 +++++++ website/docs/troubleshooting/README.md | 33 ++++++ website/docs/troubleshooting/database-ssl.md | 37 +++++++ website/docs/troubleshooting/editor-frozen.md | 37 +++++++ website/docs/troubleshooting/email-sending.md | 41 +++++++ .../troubleshooting/preview-not-loading.md | 40 +++++++ .../docs/troubleshooting/version-history.md | 46 ++++++++ website/sidebars.js | 104 ++++++++++++++++++ 51 files changed, 2815 insertions(+), 1 deletion(-) create mode 100644 website/docs/account/README.md create mode 100644 website/docs/account/delete-account.md create mode 100644 website/docs/account/export-your-site.md create mode 100644 website/docs/account/login-and-signup.md create mode 100644 website/docs/building/README.md create mode 100644 website/docs/building/editing-your-site.md create mode 100644 website/docs/building/fonts-and-media.md create mode 100644 website/docs/building/images-and-logos.md create mode 100644 website/docs/building/pages-and-navigation.md create mode 100644 website/docs/building/responsive-design.md create mode 100644 website/docs/building/templates-and-duplicating.md create mode 100644 website/docs/custom-domains/README.md create mode 100644 website/docs/custom-domains/connect-a-custom-domain.md create mode 100644 website/docs/custom-domains/registrar-guides.md create mode 100644 website/docs/custom-domains/switch-or-reuse-domain.md create mode 100644 website/docs/custom-domains/transfer-and-email.md create mode 100644 website/docs/custom-domains/troubleshooting.md create mode 100644 website/docs/custom-domains/www-vs-root.md create mode 100644 website/docs/forms-integrations/README.md create mode 100644 website/docs/forms-integrations/analytics.md create mode 100644 website/docs/forms-integrations/chat-and-scripts.md create mode 100644 website/docs/forms-integrations/contact-forms.md create mode 100644 website/docs/forms-integrations/integrations.md create mode 100644 website/docs/get-started/README.md create mode 100644 website/docs/get-started/how-kite-works.md create mode 100644 website/docs/get-started/quickstart.md create mode 100644 website/docs/pricing-credits/README.md create mode 100644 website/docs/pricing-credits/buy-credits.md create mode 100644 website/docs/pricing-credits/how-credits-work.md create mode 100644 website/docs/pricing-credits/manage-subscription.md create mode 100644 website/docs/pricing-credits/plans-and-trial.md create mode 100644 website/docs/pricing-credits/remove-kite-badge.md create mode 100644 website/docs/publishing/README.md create mode 100644 website/docs/publishing/changes-not-showing.md create mode 100644 website/docs/publishing/how-to-publish.md create mode 100644 website/docs/publishing/publish-failures.md create mode 100644 website/docs/publishing/unpublish.md create mode 100644 website/docs/publishing/your-kite-url.md create mode 100644 website/docs/seo/README.md create mode 100644 website/docs/seo/migrate-existing-site.md create mode 100644 website/docs/seo/seo-basics.md create mode 100644 website/docs/seo/sitemap-and-robots.md create mode 100644 website/docs/seo/social-previews.md create mode 100644 website/docs/troubleshooting/README.md create mode 100644 website/docs/troubleshooting/database-ssl.md create mode 100644 website/docs/troubleshooting/editor-frozen.md create mode 100644 website/docs/troubleshooting/email-sending.md create mode 100644 website/docs/troubleshooting/preview-not-loading.md create mode 100644 website/docs/troubleshooting/version-history.md diff --git a/website/docs/account/README.md b/website/docs/account/README.md new file mode 100644 index 0000000..f0835f3 --- /dev/null +++ b/website/docs/account/README.md @@ -0,0 +1,30 @@ +--- +title: Account & Settings +description: Manage your Kite account, sign in, and control your data — including deleting your account or exporting your site. +--- + +# 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. + +## 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. + +:::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. +::: + +## 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. + +## 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. diff --git a/website/docs/account/delete-account.md b/website/docs/account/delete-account.md new file mode 100644 index 0000000..c4332c7 --- /dev/null +++ b/website/docs/account/delete-account.md @@ -0,0 +1,68 @@ +--- +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. +--- + +# 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). +::: + +## Account deletion vs. canceling your subscription + +These two actions are easy to mix up, but they do very different things: + +- **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, 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 + + + +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. + +:::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. +::: + +## Before you delete + +A few things worth doing first: + +- **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/). + +## 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. + +## 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 deleted by mistake + +Because deletion is permanent, recovery may not be possible. Contact support as soon as possible with your account email — but treat deletion as final. + +## 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. diff --git a/website/docs/account/export-your-site.md b/website/docs/account/export-your-site.md new file mode 100644 index 0000000..1083d95 --- /dev/null +++ b/website/docs/account/export-your-site.md @@ -0,0 +1,55 @@ +--- +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. +--- + +# 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. + +:::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. +::: + +## What you can and can't get today + + + +What's available may change, but here's the current picture: + +- **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. + +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). + +## 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). +::: + +## 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 + +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). + +## 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. diff --git a/website/docs/account/login-and-signup.md b/website/docs/account/login-and-signup.md new file mode 100644 index 0000000..9570066 --- /dev/null +++ b/website/docs/account/login-and-signup.md @@ -0,0 +1,72 @@ +--- +title: Login & Sign Up +description: Create your Kite account, sign in, and fix common problems like missing verification or password-reset emails. +--- + +# 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. + +## Create an account + +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. + +:::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. +::: + +## Sign in + +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. + +:::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: + +- **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. + +### Password-reset email not arriving + +If you requested a password reset and the email hasn't shown up: + +- **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. + +:::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). +::: + +### "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 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. + +### Still can't get in? + +If none of the above works, contact support and include the email address on your account so the team can locate it. + +## 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. diff --git a/website/docs/building/README.md b/website/docs/building/README.md new file mode 100644 index 0000000..9f243ca --- /dev/null +++ b/website/docs/building/README.md @@ -0,0 +1,35 @@ +--- +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. +--- + +# 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. + +## 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. +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. + +You don't need to write code, manage files, or know design tools. You describe the outcome you want, and Kite handles the build. + +:::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 + +- [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. + +## Where to go next + +- 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/). diff --git a/website/docs/building/editing-your-site.md b/website/docs/building/editing-your-site.md new file mode 100644 index 0000000..f9c89a7 --- /dev/null +++ b/website/docs/building/editing-your-site.md @@ -0,0 +1,67 @@ +--- +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. +--- + +# Editing Your Site + +There are two ways to edit your Kite site: describe the change in chat, or use **Point & Edit** to click an element on the page and change it. Both work together, so use whichever feels faster for the change you're making. + +## Option 1: Describe the change in chat + +Tell Kite what to change in plain language. The more specific you are, the more likely Kite gets it right the first time. + +1. Open the chat. +2. Describe the change. Include **which page**, **which section**, the **exact text**, and the **exact color** (or other detail) where you can. +3. Send your message and wait for Kite to apply the change. +4. Preview the result. + +**Vague (harder for Kite):** +> 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). + +## Option 2: Point & Edit + +**Point & Edit** lets you click an element directly on the page instead of describing where it is. + +1. Turn on **Point & Edit**. +2. Click the element you want to change (a heading, button, image, or block). +3. Describe the change for that element, or edit it directly. +4. Preview the result. + +:::tip +Use **Point & Edit** when an element is hard to describe in words, or when there are several similar items (like three pricing cards) and you want to be sure Kite changes the right one. +::: + +## Tips for effective edit prompts + +- **One clear change at a time.** Instead of bundling five changes into one message, make them one by one so it's easy to see what worked. +- **Name the page and section.** "On the **About** page, in the team section…" beats "on that part with the photos." +- **Paste exact copy.** If you want specific wording, paste the exact text rather than describing it. +- **Be exact about colors.** Use a hex code (like `#1A73E8`) or a precise name when you can. +- **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). +::: + +## "Kite said it's done, but I don't see the change" + +This is one of the most common frustrations, and it's usually one of a few things: + +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). + +:::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. +::: + +## Troubleshooting + +- **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). diff --git a/website/docs/building/fonts-and-media.md b/website/docs/building/fonts-and-media.md new file mode 100644 index 0000000..bc832d8 --- /dev/null +++ b/website/docs/building/fonts-and-media.md @@ -0,0 +1,67 @@ +--- +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. +--- + +# 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. + +## Using brand or custom fonts + +You can ask Kite to use a specific font across your site or in a particular spot. + +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. + +3. Preview and check that text is still readable at all sizes. + +:::tip +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. +::: + +## 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: + +> 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. + + + +## 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. + +## 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). diff --git a/website/docs/building/images-and-logos.md b/website/docs/building/images-and-logos.md new file mode 100644 index 0000000..5561ddb --- /dev/null +++ b/website/docs/building/images-and-logos.md @@ -0,0 +1,75 @@ +--- +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. +--- + +# 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**. + +## Upload and replace an image + +1. Use **Point & Edit** to click the image you want to replace. +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: + +> Replace the photo in the hero section on the **Home** page with the image I'm uploading. + +:::tip +Upload images at a good size and resolution. Large, clear images look sharp; tiny or blurry source files will look low-quality on the page no matter what. +::: + +## Upload a logo + +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). + +Prompt example: + +> Replace the logo in the header with the file I'm uploading, and keep it the same size. + +## 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: + +> Can you remove the white background from my logo so it's transparent? + +:::note +The cleanest results come from a logo file that's already transparent. If you have one, use it. +::: + +## 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: + +> Remove the frame from the image in the hero section so it has no border, no rounded corners, and no shadow. + +You can also ask Kite to change the frame rather than remove it: + +> Make the image corners more rounded and add a soft shadow. + + + +## When an image replacement fails or quality drops + +- **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). + +## Troubleshooting + +- **Upload didn't work:** Try a different file or a smaller file size, and make sure it's a common image format. +- **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). + +:::tip +For more on adding fonts and other media, see [Fonts & Media](/building/fonts-and-media). +::: diff --git a/website/docs/building/pages-and-navigation.md b/website/docs/building/pages-and-navigation.md new file mode 100644 index 0000000..77a6353 --- /dev/null +++ b/website/docs/building/pages-and-navigation.md @@ -0,0 +1,70 @@ +--- +title: Pages & Navigation +description: Add pages like About, Contact, and Pricing to your Kite site, link them in your navigation menu, keep clean URLs, and fix a subpage that shows your homepage instead of its own content. +--- + +# 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. + +## Adding a page + +1. Tell Kite what page you want and what goes on it. For example: + +> Add an **About** page with our story, a team section, and a photo. + +2. Review the new page in the preview. +3. Refine the content with more chat edits or **Point & Edit**. + +Common pages people add: + +- **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. +::: + +## Linking a page in the navigation + +Adding a page doesn't always add it to your menu automatically. If a new page isn't in the nav, ask: + +> Add a link to the **About** page in the main navigation menu, between "Home" and "Contact." + +You can also ask Kite to rename, reorder, or remove menu links: + +> In the nav, rename "Services" to "What We Do" and move it before "Pricing." + +## 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: + +> Change the URL of the About page to /about. + + + +## 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. + +To fix it: + +1. Confirm the page exists and looks right in the editor. +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). +::: + +## 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). +- **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 new file mode 100644 index 0000000..a02a096 --- /dev/null +++ b/website/docs/building/responsive-design.md @@ -0,0 +1,51 @@ +--- +title: Mobile & Responsive Design +description: See how your Kite site adapts to phones and tablets, preview the mobile view, and ask Kite to fix mobile-specific problems like cropped images or a hamburger menu showing on desktop. +--- + +# 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. + +## How your site adapts + +Kite designs your site to be **responsive**, meaning the layout adjusts to the visitor's screen. On smaller screens, content typically stacks vertically, text reflows, and the navigation menu often collapses into a **hamburger menu** (the three-line icon) to save space. + +You don't have to design three separate sites. You design once, and Kite adapts it across screen sizes. + +## Previewing the mobile view + +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. +3. Scroll through every page and check headings, images, buttons, and the menu. + +:::tip +Always preview mobile before publishing. A layout that looks perfect on desktop can crop an image or push a button off-screen on a phone. +::: + +## Asking Kite to fix mobile-specific issues + +You can ask Kite to fix how something looks on one screen size without changing the others. Be specific about the screen size and the problem. + +**Cropped or truncated images on mobile:** +> On mobile, the hero image is cropped and cuts off people's faces. Please show the full image on mobile without cropping. + +**A hamburger menu showing at desktop widths:** +> The navigation is collapsing into a hamburger menu on desktop. On desktop, show the full menu with all links visible; only use the hamburger menu on mobile. + +**Different image positioning per breakpoint:** +> On desktop, keep the photo on the right of the text. On mobile, put the photo above the text and center it. + +:::note +When you report a mobile issue, name the screen size (mobile, tablet, or desktop) and describe what you see now versus what you want. That helps Kite change the right breakpoint. +::: + +## Troubleshooting + +- **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). diff --git a/website/docs/building/templates-and-duplicating.md b/website/docs/building/templates-and-duplicating.md new file mode 100644 index 0000000..bae1ae3 --- /dev/null +++ b/website/docs/building/templates-and-duplicating.md @@ -0,0 +1,71 @@ +--- +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. +--- + +# Templates & 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. + +## Starting from a template or 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. + +1. Describe your site, including the vibe you're going for. For example: + +> Build a modern, minimal site for a wedding photographer, with lots of large photos and a soft, neutral color palette. + +2. Review the design Kite generates. +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. +::: + +## Choosing among generated design options + +Kite may show you more than one design option to choose from. + +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. +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. +::: + +## Asking for more options + +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. + +## Reusing a design for another project or client + +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 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: + +> Build a new site that uses the same layout, fonts, and color style as my "Bakery" site, but for a coffee shop called "Daybreak." + + 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. +::: + +## 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." + +## 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). diff --git a/website/docs/custom-domains/README.md b/website/docs/custom-domains/README.md new file mode 100644 index 0000000..f8e9034 --- /dev/null +++ b/website/docs/custom-domains/README.md @@ -0,0 +1,37 @@ +--- +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. +--- + +# 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. + +## 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. + +:::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. +::: + +## Before you start + +A few things need to be true before you can connect a custom domain: + +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). +::: + +## 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. diff --git a/website/docs/custom-domains/connect-a-custom-domain.md b/website/docs/custom-domains/connect-a-custom-domain.md new file mode 100644 index 0000000..27af0a4 --- /dev/null +++ b/website/docs/custom-domains/connect-a-custom-domain.md @@ -0,0 +1,95 @@ +--- +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. +--- + +# Connect a Custom Domain + +This article shows you how to point your own domain (like `yourbusiness.com`) at your published Kite site. There are two ways to do it: a fast one-click flow called **Entri** that does the setup for you, and a manual option where you add DNS records yourself. + +## Before you start + +- **Publish your site first.** You can only connect a domain to a live site. See [How to publish](/publishing/how-to-publish). +- **A paid plan is required** to connect a custom domain. See [Plans & trial](/pricing-credits/plans-and-trial). +- Have your domain handy. It's fine if you bought it anywhere — see [Connect a domain from your registrar](/custom-domains/registrar-guides). + +## Start connecting your domain + +These first steps are the same for both methods. + +1. Open your site in Kite. +2. Click **Publish** in the top-right corner. +3. Click **Add Custom Domain**. +4. Type your domain (for example, `yourbusiness.com`) and click **Connect Domain**. +5. The **Entri** modal opens. This is the tool Kite uses to set up your DNS. Continue with one of the two methods below. + +:::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. +::: + +## 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. +::: + +## Method B: Manual DNS setup + +Use this if your provider isn't 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. +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. 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. + +### DNS records you'll typically add + +If you're adding records by hand, these are the values seen in real setups: + +| Type | Host / Name | Value / Points to | +|------|-------------|-------------------| +| `A` | `@` | `76.76.21.21` | +| `CNAME` | `www` | `cname.vercel-dns.com` | + +:::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. +::: + +:::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. +::: + +## After you connect + +- **Republish if prompted.** After connecting, your site may need a fresh publish for the domain to serve the latest version. +- **DNS changes take time to spread.** This is called propagation. It can be just a few minutes, but it can take up to about 48 hours for the change to reach everyone on the internet. If your domain isn't working right away, give it some time before assuming something is wrong. + +:::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). +::: + +## Troubleshooting + +- **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). diff --git a/website/docs/custom-domains/registrar-guides.md b/website/docs/custom-domains/registrar-guides.md new file mode 100644 index 0000000..0e3a252 --- /dev/null +++ b/website/docs/custom-domains/registrar-guides.md @@ -0,0 +1,83 @@ +--- +title: Connect a Domain from Your Registrar (Squarespace, GoDaddy, OVH, Cloudflare, etc.) +description: Find your DNS settings at popular domain registrars so you can point any domain to your Kite site. +--- + +# Connect a Domain from Your Registrar (Squarespace, GoDaddy, OVH, Cloudflare, etc.) + +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. +::: + +## The general process + +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. + +:::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. +::: + +## Where DNS settings live, by registrar + +The exact menu names change over time, so treat these as pointers. + +### Squarespace (and former Google Domains) + +Google Domains was migrated to **Squarespace**, so if you bought a domain through Google, you now manage it in Squarespace. + +1. Sign in at Squarespace and open **Domains**. +2. Select your domain. +3. Open **DNS** / **DNS Settings**. +4. Add the records from Entri under the custom records section. + +### GoDaddy + +1. Sign in and go to **My Products** → your domain. +2. Click **DNS** or **Manage DNS**. +3. Add or edit records under **Records**. + +### Namecheap + +1. Sign in and open **Domain List**. +2. Click **Manage** next to your domain. +3. Open the **Advanced DNS** tab. +4. Add records under **Host Records**. + +### OVH + +1. Sign in to the OVH control panel. +2. Open **Web Cloud** → **Domain names** → your domain. +3. Open the **DNS zone** tab. +4. Add or edit the records there. + +### Cloudflare + +1. Sign in and select your domain (site). +2. Open the **DNS** → **Records** section. +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. + +A **nameserver** is the server that answers DNS questions for your domain. Whichever service your nameservers point to is the one you edit. +::: + +:::tip How to tell who controls your DNS +If you're not sure, look at your domain's nameservers at your registrar. If they read something like `something.ns.cloudflare.com`, your DNS is managed in Cloudflare and that's where you make changes. +::: + +## 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). + +## Troubleshooting + +- **Edited DNS but nothing changed.** Make sure you edited DNS where your nameservers actually point (see the Cloudflare caution above), then allow time for propagation. See [Troubleshoot a connected domain](/custom-domains/troubleshooting). +- **Not sure which records to add.** Use the exact records Entri displays for your domain rather than guessing. See [Connect a custom domain](/custom-domains/connect-a-custom-domain). diff --git a/website/docs/custom-domains/switch-or-reuse-domain.md b/website/docs/custom-domains/switch-or-reuse-domain.md new file mode 100644 index 0000000..4386457 --- /dev/null +++ b/website/docs/custom-domains/switch-or-reuse-domain.md @@ -0,0 +1,66 @@ +--- +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." +--- + +# 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." + +## 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 + +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. + +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. + +## "Domain already connected to another website" + +This is the most common blocker when reusing a domain. It usually happens when: + +- 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. + +What to do: + +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. + +:::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. +::: + +## Forwarding still shows the `.kite.space` URL in the browser + +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. + +What to check: + +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. + +:::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. +::: + +## 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). diff --git a/website/docs/custom-domains/transfer-and-email.md b/website/docs/custom-domains/transfer-and-email.md new file mode 100644 index 0000000..ade1452 --- /dev/null +++ b/website/docs/custom-domains/transfer-and-email.md @@ -0,0 +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. +--- + +# Transferring 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. + +## Kite doesn't 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. + +:::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 email is not affected + +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. + +:::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. +::: + +:::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. +::: + +## 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. + +**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). + +**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. + +**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. + +## 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). +- **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). diff --git a/website/docs/custom-domains/troubleshooting.md b/website/docs/custom-domains/troubleshooting.md new file mode 100644 index 0000000..8b66873 --- /dev/null +++ b/website/docs/custom-domains/troubleshooting.md @@ -0,0 +1,79 @@ +--- +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. +--- + +# 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. + +:::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. +::: + +## Symptom → 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 | +| **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 | + +## 404 or DEPLOYMENT_NOT_FOUND + +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. + +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. + +See [Connect a custom domain](/custom-domains/connect-a-custom-domain). + +## 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. + +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. + +:::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. + +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. + +## "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). + +## 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). + +## 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. diff --git a/website/docs/custom-domains/www-vs-root.md b/website/docs/custom-domains/www-vs-root.md new file mode 100644 index 0000000..903281d --- /dev/null +++ b/website/docs/custom-domains/www-vs-root.md @@ -0,0 +1,49 @@ +--- +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. +--- + +# www vs. 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. + +## Root vs. www: what's the difference? + +- **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`. + +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. + +:::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). + +Doing this matters for two reasons: + +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. +::: + +## How to set both up in Kite + +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. + +:::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). +::: + +## 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). diff --git a/website/docs/forms-integrations/README.md b/website/docs/forms-integrations/README.md new file mode 100644 index 0000000..f2476d9 --- /dev/null +++ b/website/docs/forms-integrations/README.md @@ -0,0 +1,32 @@ +--- +title: Forms & Integrations +description: Add forms to capture leads and connect your Kite site to the third-party tools you already use. +--- + +# 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. + +## 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. + +## 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. +::: + +## Related + +- [Publishing your site](/publishing/) +- [Email sending issues](/troubleshooting/email-sending) +- [Custom domains](/custom-domains/) diff --git a/website/docs/forms-integrations/analytics.md b/website/docs/forms-integrations/analytics.md new file mode 100644 index 0000000..a360eed --- /dev/null +++ b/website/docs/forms-integrations/analytics.md @@ -0,0 +1,73 @@ +--- +title: Site Analytics +description: Use Kite's built-in visitor analytics and connect external tools like Google Analytics to understand your traffic. +--- + +# 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. + +## Kite's built-in analytics + +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. + +1. Open your project in Kite. +2. Find the **Analytics** area for your site. +3. Review your visitor numbers and most-visited pages. + + + +:::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). +::: + +## 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** + + + +To connect one: + +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). +::: + +## "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. + +:::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. +::: + +## 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. + +**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). + +## Related + +- [Chat Widgets & Custom Scripts](/forms-integrations/chat-and-scripts) +- [SEO basics](/seo/seo-basics) +- [How to publish](/publishing/how-to-publish) diff --git a/website/docs/forms-integrations/chat-and-scripts.md b/website/docs/forms-integrations/chat-and-scripts.md new file mode 100644 index 0000000..6ca2c10 --- /dev/null +++ b/website/docs/forms-integrations/chat-and-scripts.md @@ -0,0 +1,87 @@ +--- +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. +--- + +# 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. + +## 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 `