37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
# Support
|
|
|
|
ditto.site is an open-source project maintained on a best-effort basis.
|
|
|
|
## Questions
|
|
|
|
Use GitHub issues for concrete questions that are tied to this repository:
|
|
|
|
- setup problems that reproduce from a clean checkout,
|
|
- CLI, REST, MCP, or worker behavior,
|
|
- compiler output that looks wrong for a public, reproducible URL,
|
|
- documentation gaps that block a contributor.
|
|
|
|
Before opening an issue, search existing issues and include the command, URL,
|
|
options, Node version, operating system, and any run artifact or validation
|
|
report that helps reproduce the problem.
|
|
|
|
## Bugs And Feature Requests
|
|
|
|
Use the GitHub issue templates:
|
|
|
|
- Bug reports: [new bug report](https://github.com/ion-design/ditto.site/issues/new?template=bug_report.md)
|
|
- Feature requests: [new feature request](https://github.com/ion-design/ditto.site/issues/new?template=feature_request.md)
|
|
|
|
If a report involves a specific site, include only public URLs and scrub any
|
|
private credentials, cookies, internal hostnames, or proprietary content.
|
|
|
|
## Security
|
|
|
|
Do not open public issues for vulnerabilities. Follow [SECURITY.md](SECURITY.md)
|
|
and report privately through GitHub security advisories or email.
|
|
|
|
## Maintainer Expectations
|
|
|
|
There is no guaranteed response time or support SLA. Clear reproduction steps,
|
|
small examples, and focused pull requests are the fastest path to resolution.
|