refactor: styles

[wesleyboar]

What Did You Change?

Break up styles so "entrypoint" to contribute CSS is smaller.

Details

• Reorganized styles.
  • Offer inbox.css (free-form) and import.css (structured).
  • Hide advanced stylesheets in subdirectories.
• Renamed extra JavaScript file.
  ^{(unused, empty)}

Do You Want Support (syntax, design, etc)?

Does this structure to make CSS approachable or more intimidating?

BEFORE
One 300-line stylesheet (organized and commented).

.
├── ds-user-guide.css
└── README.md

AFTER
Many small stylesheets. One import stylesheet. One "inbox" stylesheet.

.
├── ds-user-guide
│   ├── …
│   └── …
├── for-other-repos
│   ├── …
│   └── …
├── tacc
│   ├── …
│   └── …
├── import.css
├── inbox.css
└── README.md

[netlify]

✅ Deploy Preview for ds-user-guide ready!

Name	Link
🔨 Latest commit	b84b362
🔍 Latest deploy log	https://app.netlify.com/projects/ds-user-guide/deploys/693c45ae53667000081adc9e
😎 Deploy Preview	https://deploy-preview-258--ds-user-guide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[wesleyboar]

@susanunit @rstijerina @taoteg (as time allows),

Imagine being a person who would contribute CSS to a docs repository: would this structure both welcome you and not overwhelm you? Review structure, not necessarily the styles.

No contributions expected; I just wanna know if I met my goal, and any other feedback you have.

[wesleyboar]

Description changed such that no need to review file diff! 🙂

[wesleyboar]

Consider moving newcomer info toward top of file. Remove obvious info (like stating this folder is for styles). consider similar updates to the js/README.md.

Suggestion given to me internally:

1. Create your CSS file in the appropriate folder (or inbox.css if unsure)
2. Add an @import for it in _import.css in the respective section