Update the website to document the end-to-end lifecycle of Compiled #1738
Conversation
kylorhall-atlassian
requested review from
JakeLane,
pancaspe87,
liamqma,
dddlr and
zesmith2
as code owners
|
✅ Deploy Preview for compiled-css-in-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
This file was used on https://compiledcssinjs.com/docs/api-css-prop, I feel it was fine to update it to be a bit more succinct and share it elsewhere.
| @@ -1,105 +1,36 @@ | |||
| import { ExampleContainer, ExampleRoot } from '@compiled/website-ui'; | |||
| import { LargeText } from '../components/example'; | |||
|
|
|||
| ## Don't change a thing | |||
There was a problem hiding this comment.
We do kinda want people to change a few things now 😄
|
Thanks @kylorhall-atlassian! |
|
A bit late - but I approve! This is a wonderful change. I've messaged you some opportunities to further build on the great work you have done 🫡 |
What is this change?
I'm updating the documentation on https://compiledcssinjs.com from internal feedback around the Compiled work as people are questioning and need to understand the differences between runtime and extraction.
Very open to feedback! It just seemed like the content on the homepage was quite important, but even I've never read it! Moving it to
/docs/how-it-worksmight help that.I did remove a few scenarios around dynamic styles, eg. the
style={{ '--abcde': props.color }}pattern, but I think it's documented elsewhere and it's best to keep it simple.PR checklist
website/