Use

[roycw]

Howdy,
I have been intrigues by this library for months now and decided to plungs and move from Tailwind.
Im trying to do Some LLM work.
Dom u have an MD file i can feed it so it can get some basic rules ?

[felix-bohlin]

Hey, I don't have that. I've thought about it but haven't prioritized it much yet. Not sure really what I could do better than just feeding the LLM the website or the API page. If you have any suggestions I'm happy to take them! :)

[roycw]

Im going all in:)
Just so i can fully understand whats going on ( and sorry for being an idio?!

Once i link theme.css it will pull in open props and everything else so i dont actually need to import anythihg else ?
Also, whats is the difference between theme 1 , 2?
If i want ,y own colors? what variables do i need to change and can i just import theme 1 and then override with lets say custom-theme.css only the colors...

Thanks a bunch!

[felix-bohlin]

First of all, yes, those files will include everything you'll need, some Open Props imports (just the ones I need) and all OPUI components. Nothing else needed to get started.

Secondly, so theme-one and theme-two are basically the exact same in terms of HTML and what you can find in the docs. They mainly differ CSS-wise. The input fields differ a lot, one is more material design inspired while two is more basic and less opinionated so to speak. If you want to override any prop you can check here or ideally look in the node_modules/opui-css/src/themes/<theme>/theme.css to check what parameters you can tweak.

Then if you're at that point where you want to start tweaking components there's nothing stopping you from going into the node_modules folder and grabbing everything and tweaking it however you want! I encourage it! :)

Happy coding!

[roycw]

HI Felix.
Ok im starting to get the hang of it!
Here are some stumbling blocks I have

1. the API document is good for humans:)_ but the LLM cant interpret it... i think the issue is that it doesnt say explicitly u need to apply "class" for the compoenent -took me a while to debug this.
2. from some kind of reason the LLM cant figure out the files input text. i guess the nested divw ith the field on top make it hard for him "to get it"

Sorry for my Focus on LLM, but its part of my app requirements.
3) as i undertsand i can import form a cdn and THEN override the theme with my own vars in lets say override.css ?
Forgot to mention but im using No build tooldig completely. i dont do Vite or any bundler...

4. ideally i want to juts add my own theme on top of a very baice already supplied css
   CAn u guide me where in the Themeonce.css i can find only the theme vars?

Just to reap (wishlist - or the way i wish it can work... :)

1. I wish i had 1 cdn import wiht bland OR default theme -- which is declared somewheer we can find
2. I can override by replacing or having another css file after it with my own vars. (just for themeing)

Again, maybe this is already there and im missing it but its alwasy hard to get stuff from another Lib :)
Looking forward...

[roycw]

Ok, i finally got it to work.
I have included the cdn for theme 2.
Override just the thymes variables in a theme.json file.

Works well and is splendid. Id love to help on this project. have many ideas, we have a huge codebase and im thinkinf of converting from tailwind.

[felix-bohlin]

Sounds like an exciting project! Imo the best way to go about it would be to at some point pull down everything locally and either:

A) just copy the entirety of theme-two into your repo, delete all components and add them in one by one on-demand.
B) grab everything locally and tweak the theme.css

At some point you're probably going to want to tweak away from the beaten path.

When it comes to new ideas to the project I'm excited to hear it! :) I'm glad you find it useful!