How to Get Support for the AI Website Cloner Template: Discord and GitHub Channels

The AI Website Cloner Template provides two primary support channels: an active Discord community for real-time troubleshooting and structured GitHub Issue templates for formal bug reports and feature requests.

When working with the JCodesMore/ai-website-cloner-template, knowing how to get support efficiently can save hours of debugging. The repository maintains dedicated resources for both informal community help and formal issue tracking, ensuring you receive timely assistance regardless of the complexity of your cloning workflow.

Community Discord for Real-Time Help

The fastest way to get answers is through the Community Discord, a real-time chat platform where contributors and users discuss usage patterns and troubleshoot together. According to the repository’s README.md, the Discord badge links directly to the official invite, while the .github/ISSUE_TEMPLATE/config.yml file explicitly points questions and discussions to this channel.

Discord provides immediate feedback for common questions about agent configurations, target URL handling, and asset extraction pipelines. Many users share their specific cloning commands and error logs in the chat, creating a searchable knowledge base of solutions.

Structured GitHub Issues for Formal Requests

For bugs requiring investigation or feature proposals needing evaluation, GitHub Issues provide a permanent, searchable record. The repository ships with pre-configured issue templates that enforce consistent formatting, making it easier for maintainers to reproduce problems.

Bug Reports

The .github/ISSUE_TEMPLATE/bug_report.yml file defines a structured form requiring critical details like Node.js version, target URL, and reproduction steps. This template ensures you include environment specifics such as OS and agent version that maintainers need to diagnose /clone-website command failures.

Feature Requests

Use the .github/ISSUE_TEMPLATE/feature_request.yml template to propose enhancements like multi-region asset downloads or new CLI flags. The form asks for a problem statement, proposed solution, and categorization, helping maintainers prioritize the roadmap.

Best Practices for Faster Responses

Following the repository’s support workflow maximizes your chances of a quick resolution. The configuration files in .github/ISSUE_TEMPLATE/ are designed to guide you toward providing the right information upfront.

• Check Discord first by browsing recent discussions; many common questions about website cloning errors are already answered there.
• Use the appropriate issue template when reporting bugs or requesting features rather than opening blank issues.
• Reference the exact command you ran (e.g., /clone-website <url>) and include full error output from the terminal.
• Specify your environment details: Node.js version, operating system, and the specific target URL causing issues.

Code Examples for Support Requests

When reaching out, use these templates to ensure your report matches the repository’s expected format.

Discord invite link:

Join the community chat: https://discord.gg/hrTSX5yTpB

Bug report structure (based on .github/ISSUE_TEMPLATE/bug_report.yml):

title: "[Bug] /clone-website fails on https://example.com"
labels: ["bug"]
body:
  - type: textarea
    id: description
    attributes:
      label: Description
      value: |
        Running `/clone-website https://example.com` throws an error after the asset-download phase.
  - type: textarea
    id: reproduction
    attributes:
      label: Steps to Reproduce
      value: |
        1. npm install
        2. claude --chrome
        3. /clone-website https://example.com
  - type: input
    id: node-version
    attributes:
      label: Node.js Version
      value: v24.1.0
  - type: input
    id: target-url
    attributes:
      label: Target URL
      value: https://example.com

Feature request structure (based on .github/ISSUE_TEMPLATE/feature_request.yml):

title: "[Feature] Add multi-region asset download"
labels: ["enhancement"]
body:
  - type: textarea
    id: problem
    attributes:
      label: Problem
      value: |
        Large sites with assets hosted on CDNs cause long download times.
  - type: textarea
    id: solution
    attributes:
      label: Proposed Solution
      value: |
        Add an optional flag `--region` to parallelise asset fetching.

Summary

• The Community Discord provides immediate, informal support for troubleshooting cloning workflows and sharing tips, linked from README.md and .github/ISSUE_TEMPLATE/config.yml.
• GitHub Issues offer structured templates for bugs and features, defined in .github/ISSUE_TEMPLATE/bug_report.yml and .github/ISSUE_TEMPLATE/feature_request.yml.
• Always include your Node.js version, target URL, and exact command when reporting issues.
• Check Discord discussions before opening an issue to find existing solutions.

Frequently Asked Questions

Where is the AI Website Cloner Template Discord invite link?

The official Discord invite is located in the README.md badge and referenced in .github/ISSUE_TEMPLATE/config.yml as the primary contact for questions and discussions. This link connects you to the community chat where users share cloning pipelines and troubleshoot together.

What information should I include in a bug report?

According to the .github/ISSUE_TEMPLATE/bug_report.yml structure, include your Node.js version, target URL, operating system, and the exact steps to reproduce the error, including the specific /clone-website command you executed. This information allows maintainers to recreate your environment and diagnose the issue quickly.

Can I open a GitHub issue for general questions?

While possible, the repository configuration in .github/ISSUE_TEMPLATE/config.yml specifically directs general questions and discussions to the Discord channel. GitHub Issues work best for confirmed bugs and feature requests using the provided templates, while Discord handles usage questions and troubleshooting.

How do I request a new feature for the template?

Use the .github/ISSUE_TEMPLATE/feature_request.yml file to submit your proposal. The template requires you to describe the problem you're solving, propose a specific solution, and categorize the feature (e.g., asset extraction or CLI improvements), which helps maintainers evaluate and prioritize community contributions.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}