How to Get Support for ai-website-cloner-template: Discord and GitHub Channels

You can get support for ai-website-cloner-template through the official Discord community for real-time troubleshooting or via structured GitHub Issues for formal bug reports and feature requests.

The JCodesMore/ai-website-cloner-template repository provides dedicated channels to help users resolve issues and share feedback. Whether you need immediate community assistance or want to report a technical problem, understanding how to get support for ai-website-cloner-template ensures you receive fast, accurate help from maintainers and contributors.

Support Channels Overview

The project offers two primary support avenues defined in the repository configuration files.

Community Discord for Real-Time Help

The fastest way to get informal support is through the official Discord server. According to the repository's .github/ISSUE_TEMPLATE/config.yml, the Discord invite link is embedded in the README.md badge and serves as the primary contact for questions and discussions.

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

This channel is ideal for:

• Quick troubleshooting questions
• Sharing custom cloning pipelines
• Discussing usage patterns with other AI-assisted web cloning users

GitHub Issues for Structured Requests

For bugs, errors, or detailed feature proposals, use the GitHub Issues system. The repository ships with YAML-formatted issue templates located in .github/ISSUE_TEMPLATE/ that enforce consistent reporting standards.

Available templates include:

• Bug Report (.github/ISSUE_TEMPLATE/bug_report.yml): Requires Node version, target URL, and reproduction steps
• Feature Request (.github/ISSUE_TEMPLATE/feature_request.yml): Captures problem descriptions and proposed solutions

How to File an Effective Bug Report

To get support for ai-website-cloner-template when encountering errors, use the bug report template to supply mandatory diagnostic information. The template in .github/ISSUE_TEMPLATE/bug_report.yml requires specific fields that maintainers need to reproduce issues.

Required information includes:

• Target URL: The website you attempted to clone
• Node.js Version: Your runtime environment (e.g., v24.1.0)
• Command executed: Such as /clone-website https://example.com
• Error output: Full stack traces or screenshots

Example bug report structure:

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

How to Submit a Feature Request

When requesting enhancements, the .github/ISSUE_TEMPLATE/feature_request.yml template guides you to articulate the problem and proposed solution clearly. This structured approach helps maintainers evaluate feasibility and priority.

Example feature request format:

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.
  - type: dropdown
    id: category
    attributes:
      label: Category
      options:
        - Asset extraction

Key Support Files in the Repository

Understanding the location of support documentation helps you reference the correct resources when seeking help.

• README.md: Contains the Discord badge link and quick-start instructions at the repository root
• .github/ISSUE_TEMPLATE/config.yml: Configures the "Questions & Discussion" contact link pointing to Discord
• .github/ISSUE_TEMPLATE/bug_report.yml: Structured form requiring OS, Node version, and target URL fields
• .github/ISSUE_TEMPLATE/feature_request.yml: Form for proposing improvements with problem/solution fields

Summary

• Discord provides immediate, informal support for troubleshooting and usage questions via https://discord.gg/hrTSX5yTpB
• GitHub Issues offer structured templates in .github/ISSUE_TEMPLATE/ for bugs and features, ensuring you include required diagnostics like Node version and target URLs
• Always check recent Discord discussions before filing new issues to avoid duplicates
• Use the exact command syntax (e.g., /clone-website <url>) and error logs when reporting bugs to speed up resolution

Frequently Asked Questions

Is there a Discord server for ai-website-cloner-template?

Yes, the repository maintains an official Discord server accessible via the invite link https://discord.gg/hrTSX5yTpB. This link appears in the README.md badge and the issue template configuration at .github/ISSUE_TEMPLATE/config.yml, serving as the primary venue for real-time community support.

What information should I include in a bug report?

You must include your Node.js version, the target URL you attempted to clone, the exact command executed (such as /clone-website https://example.com), and any error output or stack traces. The .github/ISSUE_TEMPLATE/bug_report.yml enforces these fields to ensure maintainers can reproduce the issue.

Can I ask general questions in GitHub Issues?

While general questions are better suited for Discord, the repository's issue templates are configured to redirect casual inquiries to the Discord channel. According to .github/ISSUE_TEMPLATE/config.yml, GitHub Issues should be reserved for structured bug reports and feature requests using the provided YAML forms.

Where are the issue templates located?

The issue templates reside in the .github/ISSUE_TEMPLATE/ directory. Specifically, bug_report.yml handles error submissions, feature_request.yml manages enhancement proposals, and config.yml defines the contact links including the Discord server reference.

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