Great, that sounds perfect. Thanks a lot for the information. It’s definitely confirmed the direction that I’d like to take when approaching this project!
Basically the purpose would be exactly what Roger is describing. The main site contains information about a non-profit organization. They would like to have an area for the members of the organization to discuss events and make connections. They want two very different experiences.
That is why I was inquiring about the WordPress Network/Multisite for this project.
Did this work well for you Roger? If so, I believe that this will be the approach I take for the project.
The main site is being used primarily as an organization website. There is a blog page, but for the most part, they are just pages filled with information utilizing WordPress so that the client does not need to use code to manage their website.
So what you’re saying is follow the steps that will allow the organization theme to play nicely with Buddypress?
The purpose would be to completely eliminate all Buddypress functionality from the root site. The client wants to link to the /community subdirectory from the root, but does not want admin bars or any of the associated features in the root.
Ideally, Buddypress would be entirely contained in the /community subdirectory. The admin bar and all its functionality would be here. It’s almost as if they were two completely different websites that were associated with one another, but also share a userbase.
Sorry, I’m just trying to explain this clearly. Before I commit the time to the project, I’d like to have a clear idea of what I’m doing and the best way to do it.
