w3c / w3c/guide

[manual of style] Describe how styling works, and point to examples

Open
#408 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

manual-of-style
Dominant language
HTML
Stars
84
Forks
69
Avg merge
14h 52m
Merged PRs (30d)
2

Description

I just scanned through the Manual of Style thinking that it might tell me about styling, and discovered that it only mentions CSS in a few places, and doesn't do some things that I think could be helpful:

  1. Explain how styling is applied by default, i.e. that there's a W3C stylesheet, and a fixup script
  2. Note that it doesn't cover everything, and how to add more styling - is it better to include inline styling or reference an additional stylesheet? (I've always added an inline style block, but maybe people have other opinions!)
  3. Include some pointers to examples where folk have worked around practices or Process requirements that the stylesheet doesn't (yet) support, for example:
    a. indicating embedded Registry sections. e.g. in DAPT's two registry sections (such as <content-descriptor>);
    b. styling the "Tests" details sections e.g. in CSS Fonts Level 4);
    c. indicating features that contribute to fingerprintability (PING Fingerprinting Guidance best practice 3)

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.

Research direction

Locate the Manual of Style and review its existing CSS references first. Document the default W3C stylesheet and fixup script, explain how contributors should add styling, and link the DAPT, CSS Fonts Level 4, and PING Fingerprinting Guidance examples. Done means the styling guidance and all three example categories are clearly covered.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.