Why is the community side of a Web3 project usually an afterthought?
I’m working on a small Web3 project and I’m starting to think about where the community side of it should live. One thing I’m trying to avoid is building the actual product in one place and then recreating memberships, permissions, bots and everything else somewhere completely separate. That seems manageable early on, but I can see it getting messy once there are different types of users or access levels.
I’m wondering about how other builders approach this, do you use an existing community platform and connect whatever tools you need later or do you think about the community layer as part of the product from the beginning? I’m still early enough that I can go either way, so interested in what people who have already dealt with this ended up doing.