Skip to content

docs: clarify seed code indentation and hyphenation rules #1264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
raisedadead merged 1 commit into from
Mar 18, 2026
Merged

docs: clarify seed code indentation and hyphenation rules #1264

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions src/content/docs/how-to-work-on-coding-challenges.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -268,7 +268,7 @@ Proper nouns should use correct capitalization when possible. Below is a list of

- JavaScript (capital letters in "J" and "S" and no abbreviations)
- Node.js
- Although sometimes inaccurate, non-hyphenated forms of 'back end' and 'front end' should be used, as they are more widely used.
- When referring to front-end, back-end, or full-stack, use the hyphenated form.

### The 2-minute rule

Expand Down Expand Up @@ -363,9 +363,11 @@ Overall, we prefer the internal testing library implementation.

Here are specific formatting guidelines for the challenge seed code:

- Use two spaces to indent
- Use two spaces to indent for HTML, CSS, and JavaScript
- Use four spaces to indent for Python
- JavaScript statements end with a semicolon
- Use double quotes where applicable
- Use double quotes where applicable for HTML, CSS, and JavaScript
- Use single quotes where applicable for Python

### Seed Code Comments

Expand Down