It depends. I like to keep everything in the same project unless I need to use the components in multiple, different projects. If this is the case, I would have a different Phoenix project for it, showcasing them using routes.
I know that having everything together with the main app is not the most scalable solution, but it works (if the components are organized, of course - thanks to the atomic design, I can manage them in a sane way). Listing all the components along with their docs in a simple route worked well in most of my use cases.
I want to explore how far I can use ex_docs (or LiveBook, idk) for documenting the components. Depending on the results, I’ll write a follow-up post.
