Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CSS tutorials

Open
#279 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
css
Domain
documentation

Research direction

Locate the CSS tutorial pages and review the sections covering moving CSS into a separate file, margin shorthand, and “Styling our page further.” Update the tutorial so CSS starts in a separate file, shorthand is introduced later or as an optional aside, and the browser reset appears around that section; compare the resulting instructions with the example page.

Written by the indexing model from the issue text.

Description

Hi all!

I've been through the CSS tutorials with a good few people over the last year or so and I've found that a large amount of them fall over at a few specific places:

  1. Moving the CSS from the head into a separate file
  2. Using shorthand for margin values
  3. The lack of a browser 'reset' until the end of the document, causing marked differences between what they're seeing and the example page until that last step

There are a couple of minor issues but these are the main ones that have caused a bit of consternation for students. Would it be possible to:

  1. Start with the CSS in a separate file
  2. Not introduce shorthand so blatantly, so early, and instead introduce it as a 'side' or bonus, or something along those lines?
  3. Introduce the browser reset around the part titled, 'Styling our page further'

What are people's thoughts on this? Is there a better channel for me to have this discussion?

I'm happy to make the changes listed above.

Cheers!

Dominant language
JavaScript
Stars
268
Forks
240
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codebar/tutorials

All issues in codebar/tutorials

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.