POC of Design System integration via CDN stylesheet

[k1eu]

closes #55

POC of Design System integration via CDN stylesheet

• Added necessary steps to build tailwind css file
• Added serving it as static file on the same url as docs (for now, later on we will use npm and its cdn)
• Added How to use on main page with ability to copy full link rel='stylesheet' code that needs to be embeded in each project

TODO

• [ ] add README.md entry

Future plans

• [ ] npm package also with only styles.css
• [ ] npm package with tailwind.config.js for projects with tailwind

[netlify[bot]]

✅ Deploy Preview for selleo-designsystem ready!

Name	Link
🔨 Latest commit	33bd39e7df9cb1c0d4fff82062cef81aafa765dd
🔍 Latest deploy log	https://app.netlify.com/sites/selleo-designsystem/deploys/63fea550ac9a32000828adf9
😎 Deploy Preview	https://deploy-preview-64--selleo-designsystem.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 site settings.

[PoslinskiNet]

@k1eu I would consider adding @version after the file name, so the user can switch easily between releases if need so.

For instance: selleo-ds@1.0.css

[PoslinskiNet]

@k1eu also, @latest could be an option or without anything to fetch always the latest version released (maybe we can leave it as it is right now, and handle versioning once we will need it - now we don't need it so it could be premature optimization that is hard to say that someone will ever need.

[k1eu]

@PoslinskiNet Since we don't yet have proper versioning I'd maybe skip it for now? I can add @latest for now. And once we step into proper releases and versioning we can add @1.2.3 ability. Wdyt?