...
A couple of 3rd party options were considered but both options would require maintaining hard coded configuration datacontext specific configurations and/or extensive integration into the client app. This would make implementation less flexible and incur tech debt as these configs would have to be updated whenever new props are added by a developermaintained.
A more flexible approach is one in which the application parses the CSS DOM for implemented CSS custom props and returns an object that can be used to generate the UI controls dynamically. We have proven this approach out in this prototype:
...
Higher risk of bugs early on to roll our own property management solution since there is a smaller test pool than a published 3rd party solution
Ensuring adequate cross platform compatibility as the solution requires the use of some lesser used JS methods and CSS DOM parsing techniques.
Malformed props might be introduced into the system by developers (note: we plan to mitigate this with prop validation)
...
How will we save, recall, and publish CSS theme props?
...