2 Replies Latest reply on Mar 31, 2016 12:43 PM by Jennifer Kelley

    Seeking advice: Changing hierarchy of Jive instance & addin a public space

    kristamahler

      Hello!

      I'm seeking the advice from the JC! 

       

      After being so inspired at jiveworld2016, we are gaining some ground in (hopefully) expanding our Jive instance for more use cases for our company.  Yay!

      That being said, if we do get to move forward with moving our .com blog over to our Jive community we will have to make a lot of changes in the structure of how our instance was built in the first place.  We currently have Jive-x, but it is completely gated for our customers.  We will however have to have an open space where the blog would live for SEO purposes etc.  We also will likely have to redesign EVERYTHING and basically add a higher space level to the hierarchy so that we can make it look like our .com look/feel. 

       

      Does anyone have experience with expanding your Jive instance to other use cases and adding a public space to a currently gated community and/or moving current spaces down a level in the hierarchy so that the homepage can host the public space, while the gated spaces are down a level? 

       

      I'm just looking for advice and maybe some tips to make sure we don't mess anything up.  I'm thinking we may need to work with Jive and/or an outside company to make all these changes so that everything can function in the intended way. 

       

      Also, let me know if you need any clarification on my questions/set up/etc. 

      Thanks!

        • Re: Seeking advice: Changing hierarchy of Jive instance & addin a public space
          adina.schoeneman

          We also have an entirely gated community and am thinking about adding a public portion and am interested how others have approached this

          • Re: Seeking advice: Changing hierarchy of Jive instance & addin a public space
            Jennifer Kelley

            Thanks Krista (and glad you found JW16 so inspiring!) and Adina for your interest also.

             

            Here are some very quick thoughts and then to define and validate a solid plan for expanding your use cases / archicture / footprint I probably would recommend engaging with a strategist from Jive or one of our certified partners to make this as smooth as possible.

             

            But with few exceptions there are huge benefits to having at least a portion of your community content public, whether you are focused more on support or thought leadership.  Namely, search engines and SEO are an important way that users find your content and community.  And second it can give "public" audiences (prospects of even just un-registered users) visibility into your culture, value and how you engage with your customers/partners/users.

             

            Jive's permissions and entitlements are flexible and make it pretty easy for you to "have your cake and eat it too" with regard to having some content public but not all/most.  You'll want to sit down and do some planning to figure out what approach (or progressive steps) is right for you.  On the simplest end would be adding a single space that is public and populating it with some relevant content and maybe a blog.  Maybe you also want to allow for some general questions?  (Users would have to register to participate still.)  On the more complex end of things would be rethinking your who content strategy / site architecture to make more topics or areas public, and for that you'll want to be more strategic and have a business rationale or set of criteria.

             

            Some tactical things to call out - and again all things a Jive PS or partner consultant can help facilitate for your individual community -

            • you'll may likely want to modify your permissions model to differentiate guest/anonymous users from "all registered" and then possibly from actual customers or otherwise validated users.  Core Help
            • you may want to tweak the profile visibility settings so that only registered users can see more about your members in the directory / profile
            • make sure to communicate and support users through the transition, so they understand which areas are public vs private and where to engage on what topics etc

             

            Hope that helps and there's a related, recent thread on blogs that might interest you: SEO Blog Comparisons

            3 people found this helpful