Any documentation out there on recommended class renaming philosophy/approach?
Getting to the point in the build where we're pretty set on our selected layouts/components. Perhaps it may not be necessary but I'm assuming theres some cleanup-related benefits to culling down the class list and systemizing some of the naming? And theres always room to add more layouts at some point so just trying to find the right when & how to start tackling that process.
Thanks!
are you familiar with Client-First? If you are and you are looking for something beyond that, and maybe some examples, let me know and I'd be happy to help out there.
Otherwise, our style guide and components are based on Client-First and the naming conventions set forth there.
I do have a doc that is queued up for the next couple of weeks to go over how to extend our components in a Client-First way which seems also related to your question.