https://github.com/stevenxl/css-playground

This is a playground for experimenting with and "trying things out" in CSS.
https://github.com/stevenxl/css-playground

Last synced: about 1 month ago
JSON representation

This is a playground for experimenting with and "trying things out" in CSS.

• Host: GitHub
• URL: https://github.com/stevenxl/css-playground
• Owner: StevenXL
• License: mpl-2.0
• Created: 2019-11-17T16:45:57.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2019-11-17T21:57:35.000Z (about 5 years ago)
• Last Synced: 2024-11-30T12:33:13.624Z (about 2 months ago)
• Language: HTML
• Size: 9.77 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# CSS-Playground

I have found that I learn best when I take a problem and distill it down to its

most essential parts, and work on that part independently of any context.

For example, if I want to learn what the `align-items` CSS property does, I can

start with a blank slate, hold everything else constant, and experiment only

with the `align-items` property. By starting with a blank slate, I have

confidence that the behavior I am witnessing is solely due to the `align-items`

property, and not some unknown context that is also impacting behavior.

To experiment in this playground:

0. Branch out from the `master` branch with a descriptive name - i.e. `align-items`.

0. Play in the playground.

0. Commit the changes to the branch in such a way that they tell a story. For

   example, the first commit might be simple setup. The second commit might

   change a single property, and the third commit might change that property's

   value once again.

As always, commit messages should be descriptive and explain `why` and `how`.

The `what` is the commit's changes to the codebase itself.