1/3 @Conaw the new CSS stuff is really great. The intentional surfacing of data elements and visual structure is going to be a big help as we move forward. I have one recommendation: Change the roam/css model to be like {{[[roam/js]]}}.
Recommendation: {{[[roam/css]]}}
Recommendation: {{[[roam/css]]}}
2/3 The current one page model works very well, but gets difficult to manage as the number of customization grows since everything has to be on one page.
Second, it would be nice to prototype visual designs right in the context of what you are working on.
Second, it would be nice to prototype visual designs right in the context of what you are working on.
3/3 Additionally, it would give roam/js developers flexibility in providing UI customization.
So if we had {{[[roam/css]]}} that could be defined any where, this would be useful.
So if we had {{[[roam/css]]}} that could be defined any where, this would be useful.
Bonus Tweet: problem is of course CSS precedence. allow CSS dev to provide a order of priority, Lower the number, loaded earlier, higher the number loaded later.
{{[[roam/css]]: 10}}
{{[[roam/css]]: 10}}
• • •
Missing some Tweet in this thread? You can try to
force a refresh
