Skip to content

Commit dda90a0

Browse files
chore: bootstrap website as exact copy of Create-Node-App/website
Literal snapshot of Create-Node-App/website main for Create-Python-App adaptation. No CPA-specific changes in this commit. Co-authored-by: Cursor <cursoragent@cursor.com>
0 parents  commit dda90a0

168 files changed

Lines changed: 25753 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.checkov.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Checkov configuration — keep GHA scans, skip noisy false positives if any remain.
2+
compact: true
3+
quiet: true
4+
framework:
5+
- github_actions
6+
soft-fail: false

.cspell.json

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,104 @@
1+
{
2+
"version": "0.2",
3+
"language": "en",
4+
"words": [
5+
"addons",
6+
"AGENTS",
7+
"alstr",
8+
"animatedgradient",
9+
"Behaviour",
10+
"Chakra",
11+
"checkov",
12+
"clsx",
13+
"cmdk",
14+
"cna",
15+
"codepaths",
16+
"commitlint",
17+
"contenido",
18+
"controlado",
19+
"copypaste",
20+
"cpath",
21+
"crect",
22+
"cspell",
23+
"csvg",
24+
"dangerfile",
25+
"dompurify",
26+
"dotenv",
27+
"Elipssis",
28+
"embla",
29+
"esbuild",
30+
"eslintcache",
31+
"extraida",
32+
"extraída",
33+
"grype",
34+
"hookform",
35+
"interactiva",
36+
"jeremias",
37+
"jscoverage",
38+
"jscpd",
39+
"jspm",
40+
"jumpstart",
41+
"linaria",
42+
"lintstagedrc",
43+
"lucide",
44+
"megalinter",
45+
"mermaid",
46+
"minimatch",
47+
"misconfig",
48+
"nextjs",
49+
"npmjs",
50+
"nums",
51+
"Pagespeed",
52+
"PBAC",
53+
"pgvector",
54+
"picomatch",
55+
"pids",
56+
"preconfigured",
57+
"radix",
58+
"Reakit",
59+
"recharts",
60+
"bunx",
61+
"Codegen",
62+
"Lingui",
63+
"makepkg",
64+
"paru",
65+
"PKGBUILD",
66+
"saas",
67+
"Supabase",
68+
"Selenoid",
69+
"shadcn",
70+
"sonner",
71+
"srcset",
72+
"SSCCE",
73+
"stefanzweifel",
74+
"syft",
75+
"tailwindcss",
76+
"transpiling",
77+
"trivy",
78+
"trufflehog",
79+
"turborepo",
80+
"Turborepo",
81+
"ulises",
82+
"ulisesjeremias",
83+
"unmemoized",
84+
"unvetted",
85+
"vaul",
86+
"vercel",
87+
"vite",
88+
"vitest",
89+
"vlang",
90+
"Vlang",
91+
"webextension",
92+
"workdir",
93+
"wscript"
94+
],
95+
"ignorePaths": [
96+
"node_modules/**",
97+
".next/**",
98+
"pnpm-lock.yaml",
99+
"megalinter-reports/**",
100+
"public/**",
101+
"**/*.svg",
102+
"tools/danger/package-lock.json"
103+
]
104+
}

.editorconfig

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# http://editorconfig.org
2+
3+
root = true
4+
5+
[*]
6+
charset = utf-8
7+
indent_style = space
8+
indent_size = 2
9+
end_of_line = lf
10+
insert_final_newline = true
11+
trim_trailing_whitespace = true
12+
13+
[*.md]
14+
insert_final_newline = true
15+
trim_trailing_whitespace = false

.github/CODE_OF_CONDUCT.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Code of Conduct
2+
3+
This code of conduct is derived from the Ruby code of conduct. This document provides community guidelines for a safe, respectful, productive, and collaborative place for any person who is willing to contribute to this community. It applies to all “collaborative space”, which is defined as community communications channels. Any violations of the code of conduct may be reported by contacting one or more of the project maintainers either directly.
4+
5+
- Participants will be tolerant of opposing views.
6+
- Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
7+
- When interpreting the words and actions of others, participants should always assume good intentions.
8+
- Behaviour that the project maintainers consider to be harassment will not be tolerated.
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
name: '🐛 Bug Report'
3+
description: Report a bug
4+
title: '(short issue description)'
5+
labels: [bug]
6+
body:
7+
- type: textarea
8+
id: description
9+
attributes:
10+
label: Describe the bug
11+
description: What is the problem? A clear and concise description of the bug.
12+
validations:
13+
required: true
14+
- type: textarea
15+
id: expected
16+
attributes:
17+
label: Expected Behavior
18+
description: |
19+
What did you expect to happen?
20+
validations:
21+
required: true
22+
- type: textarea
23+
id: current
24+
attributes:
25+
label: Current Behavior
26+
description: |
27+
What actually happened?
28+
29+
Please include full errors, uncaught exceptions, stack traces, and relevant logs.
30+
If service/functions responses are relevant, please include wire logs.
31+
validations:
32+
required: true
33+
- type: textarea
34+
id: reproduction
35+
attributes:
36+
label: Reproduction Steps
37+
description: |
38+
Provide a self-contained, concise snippet of code that can be used to reproduce the issue.
39+
For more complex issues provide a repo with the smallest sample that reproduces the bug.
40+
41+
Avoid including business logic or unrelated code, it makes diagnosis more difficult.
42+
The code sample should be an SSCCE. See http://sscce.org/ for details. In short, please provide a code sample that we can copy/paste, run and reproduce.
43+
validations:
44+
required: true
45+
- type: textarea
46+
id: solution
47+
attributes:
48+
label: Possible Solution
49+
description: |
50+
Suggest a fix/reason for the bug
51+
validations:
52+
required: false
53+
- type: textarea
54+
id: context
55+
attributes:
56+
label: Additional Information/Context
57+
description: |
58+
Anything else that might be relevant for troubleshooting this bug. Providing context helps us come up with a solution that is most useful in the real world.
59+
validations:
60+
required: false
61+
- type: input
62+
id: version
63+
attributes:
64+
label: Version used
65+
description: |
66+
Please provide the version of the repository or tool you are using.
67+
validations:
68+
required: true
69+
- type: textarea
70+
id: environment
71+
attributes:
72+
label: Environment details (OS name and version, etc.)
73+
validations:
74+
required: true

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: 💬 General Question
5+
url: https://github.com/Create-Node-App/create-node-app/discussions/categories/q-a
6+
about: Please ask and answer questions as a discussion thread
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
name: '📕 Documentation Issue'
2+
description: Report an issue in the Reference documentation or Developer Guide
3+
title: '(short issue description)'
4+
labels: [documentation]
5+
body:
6+
- type: textarea
7+
id: description
8+
attributes:
9+
label: Describe the issue
10+
description: A clear and concise description of the issue.
11+
validations:
12+
required: true
13+
14+
- type: textarea
15+
id: links
16+
attributes:
17+
label: Links
18+
description: |
19+
Include links to affected documentation page(s).
20+
validations:
21+
required: true
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
name: 🚀 Feature Request
3+
description: Suggest an idea for this project
4+
title: '(short issue description)'
5+
labels: [feature-request]
6+
body:
7+
- type: textarea
8+
id: description
9+
attributes:
10+
label: Describe the feature
11+
description: A clear and concise description of the feature you are proposing.
12+
validations:
13+
required: true
14+
- type: textarea
15+
id: use-case
16+
attributes:
17+
label: Use Case
18+
description: |
19+
Why do you need this feature? For example: "I'm always frustrated when..."
20+
validations:
21+
required: true
22+
- type: textarea
23+
id: solution
24+
attributes:
25+
label: Proposed Solution
26+
description: |
27+
Suggest how to implement the addition or change. Please include prototype/workaround/sketch/reference implementation.
28+
validations:
29+
required: false
30+
- type: textarea
31+
id: other
32+
attributes:
33+
label: Other Information
34+
description: |
35+
Any alternative solutions or features you considered, a more detailed explanation, stack traces, related issues, links for context, etc.
36+
validations:
37+
required: false
38+
- type: checkboxes
39+
id: ack
40+
attributes:
41+
label: Acknowledgements
42+
options:
43+
- label: I may be able to implement this feature request
44+
required: false
45+
- label: This feature might incur a breaking change
46+
required: false
47+
- type: input
48+
id: version
49+
attributes:
50+
label: Version used
51+
description: |
52+
Please provide the version of the repository or tool you are using.
53+
validations:
54+
required: true
55+
- type: input
56+
id: environment
57+
attributes:
58+
label: Environment details (OS name and version, etc.)
59+
validations:
60+
required: true

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## Description
2+
3+
Please include a summary of the changes and the related issue. List any dependencies that are required for this change.
4+
5+
Fixes # (issue)
6+
7+
## Type of Change
8+
9+
- [ ] Bug fix (non-breaking change which fixes an issue)
10+
- [ ] New feature (non-breaking change which adds functionality)
11+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
- [ ] Documentation update
13+
14+
## How Has This Been Tested?
15+
16+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
17+
18+
- [ ] Test A
19+
- [ ] Test B
20+
21+
## Checklist
22+
23+
- [ ] My code follows the style guidelines of this project
24+
- [ ] I have performed a self-review of my code
25+
- [ ] I have commented my code, particularly in hard-to-understand areas
26+
- [ ] I have made corresponding changes to the documentation
27+
- [ ] My changes generate no new warnings
28+
- [ ] Any dependent changes have been merged and published in downstream modules
29+
- [ ] I have checked my code and corrected any misspellings

0 commit comments

Comments
 (0)