I like the concept of Spaces, But...

I have a perfect application in mind for 'Spaces', but consider this:

I will have at minimum, 50 top level parent spaces. Each of those parent spaces may have hundreds of child spaces.
The method of posting content, is not workable, How can anyone be expected tosroll through a list of hundreds of visibility options every single time they want to post content? The answer is, they can't, and they won't. The spaces module is in dire need of a self-contained add content button, If there ever was an urgent need for something, this is it. Without it, adding content is confusing to users, and puts projects like my current one at a dead standstill.
What do I have to do to get this done?

  • Up vote
    1
    Down vote
  • View
    556
  • More
Replies (13)

    • 1. Often Spaces are set up in a way that people only join (or are programmatically added to) a few spaces, not all. For example, where spaces are used for regions, people can be added to space based on their address postcode, or based on their location, or both. In this case, when posting, they only see a few spaces as options. 

      2. Alternatively, you can enable the "Add content" form inside of the space and use the Spaces browsing page for selection. 

      Do you mean a button inside of the Space/Group/"context..." like "Add..." with dropdown selection of content items similar to the site-wide button? It would make sense for sure, too. 

      • Yes, similar to the site wide  button. The only dissimilarity being the its association with any given space would have to be obvious and not be mistaken for the site wide button

        To be clear, every single parent/child space should have an 'add content' button.  Most end users will expect it to work this way.  I'd suggest putting it wh.ere the 'Leave Space button is now, and push the leave button all the way to the right.  The current method is fine for adding top level content, but when that content belong to a unique space, group, event, etc., it needs to be treated differently. It doesn't mean you have to change everything about the existing method, just add a new method. Multiple ways to accomplish the same thing is rarely a bad thing.  I do believe this new method will have a big positive impact on end user understanding and usability of una based sites.

        If it takes custom paid work to get it done in a hurry, I'll be watching for a price quote.  I have a complex application where I will have 50 or more top level parent spaces, and eventually thousands child spaces in the hierarchy.  The idea is unworkable without being able to add content by a direct method.

        • https://github.com/unaio/una/issues/3204 - Alex T⚜️ please review for v13

          Mark Purser please organize a quote

          • Yes, similar to the site wide  button. The only dissimilarity being the its association with any given space would have to be obvious and not be mistaken for the site wide button

            To be clear, every single parent/child space should have an 'add content' button.  Most end users will expect it to work this way.  I'd suggest putting it wh.ere the 'Leave Space button is now, and push the leave button all the way to the right.  The current method is fine for adding top level content, but when that content belong to a unique space, group, event, etc., it needs to be treated differently. It doesn't mean you have to change everything about the existing method, just add a new method. Multiple ways to accomplish the same thing is rarely a bad thing.  I do believe this new method will have a big positive impact on end user understanding and usability of una based sites.

            If it takes custom paid work to get it done in a hurry, I'll be watching for a price quote.  I have a complex application where I will have 50 or more top level parent spaces, and eventually thousands child spaces in the hierarchy.  The idea is unworkable without being able to add content by a direct method.

            I think "Add content..." block behaves almost like this, what is your variant compared to existing "Add content..." block ? or how your variant should work in more descriptive way, it would be great if you can make some sketches ?

            Also we plan to redesign Privacy field to make it like a popup, so you will be able to search for groups/spaces/etc where you can post.

            • What "Add Content" block are you referring to.  I've been using una for about one month now, and I have no idea what you're talking about

              • What "Add Content" block are you referring to.  I've been using una for about one month now, and I have no idea what you're talking about

                This one, you need to add it to Group view page:


                • If by chance, you are talking about the Create Post (Context) block, that i just discovered and added to the 'View Space' page, the behavior is indeed close. But for 'Spaces' an add content function really should be on the actions menu, so you can see it regarles of what space content you are viewing. So... I think we are talking about adding an Action button that pops up a menu where you select the type of content to be added
                  If there's an easy way to put this on the navigation menu. that would be a good start. The alternative would be to place the Create Post (Context) block in a dozen different places.

                  That said, I find the find the behavior of Spaces a bit odd.  While you are on the Space View page, you have the Space menu will all its various items, you can navigate around, and still have the feel of being in a "Space".  However. once you post content, or view content, the Space menu is gone, as you are navigated away from the 'Space' you thought you were viewing, and you immediately feel disconnected from the space... because you are. It's not an elegant feel when you have to hit the browser back button to return to where you were.  I'm surprised no one has griped about this.  

                  •  - @alex please review for v13

                    organize a quote

                    Yes,,please please pretty please with sugar on top, organize a quote.

                    The problem with the "Create Post (Context)" block, is that it is a system block, and as such. there is no control over the type of content I want users to be able to post to Spaces.  I hate to keep picking on the Recipe module, because it's a great module for the site in general. but it has no business in 'Spaces' as I intend to use them.  I can remove 'Recipes' easily enough from the Spaces navigation menu, but when I place a system block like that Create Post (Context), there's the Recipes, on the menu (No pun intended)

                    What I really need, in fact what everybody needs, is:

                    1. A method to post content directly to 'Spaces'

                    2. Admin controls over what types of content are to be posted to Spaces

                    There's other odd behavior of Spaces and Groups, but these two things have me dead in the water.

                    A Bare minimum solution would be a new system block, let's call it "Create Post (Spaces)" . Let's say this block would work off the content items I have enabled on the "View Space Submenu" ,  Preferrably, the 'Add New..' would be placed on the space navigation menu so that it's always visible.

                    • BTW... not allowing me to post links is driving me up the friggin wall.

                      • No quote yet.  I am beginning to thinks you guys don't love me anymore... say it ain't so :'(       What am I supposed to do with all this money burning a hole in my pocket?

                        • No quite yet.  I am beginning to thinks you guys don't love me anymore... say it ain't so :'(       What am I supposed to do with all this money burning a hole in my pocket?

                          Sorry for delay. Actually such modification requires some changes which aren't fitting the UNA structure well, since posting into context can be done from different places, also there are roles in group based modules which will require quite complicated interface to specify which content is allowed to post for different roles, which could overlap some privacy settings in a group. 

                          As an intermediate solution I would suggest some simple workaround, just add the following CSS code into RAW block on Space view page, it will hide specified items from "Create Post (Context)" block menu:

                          <style>
-create-post-ma-popup li[class*=bx_glossary],
-create-post-ma-popup li[class*=bx_shopify],
-create-post-ma-popup li[class*=bx_snipcart],
-create-post li[class*=bx_glossary],
-create-post li[class*=bx_shopify],
-create-post li[class*=bx_snipcart] {
  display: none;
}
</style>

                          It maybe it is without sugar on top, but it should work.

                          • Sorry for delay. Actually such modification requires some changes which aren't fitting the UNA structure well, since posting into context can be done from different places, also there are roles in group based modules which will require quite complicated interface to specify which content is allowed to post for different roles, which could overlap some privacy settings in a group. 

                            I can get by with this, but it's a bandaid, not a cure.  

                            It worries me that it takes complicated changes, to give group creators the ability to decide the types of content they want in their group or space.  I do believe that this should be a feature, and I do understand that it could take a lot of time and effort.

                            In the mean time...  What if there were a derivative of the "Create Post (Context)" block that worked just like it. but only allowed posting of the content types that were enabled on the  Navigation > Items > Spaces > View Space Submenu?  It would be a way for site admins to have control over what types of content that could be posted to spaces and groups. Roles and privacy should be irrelevant in such a case... you shouldn't have to mess with those things, if all you were doing was preventing All users from posting selected content. In such an implementation, it would be wise to also provide for a way to remove groups and/or spaces from the visibility selector for site wide content posting, for obvious reasons. This doesn't do anything for group creators, but it would give site admins control over group content, and that's the most important, in my opinion.

                            •  - @alex please review for v13

                              organize a quote

                              Yes,,please please pretty please with sugar on top, organize a quote.

                              The problem with the "Create Post (Context)" block, is that it is a system block, and as such. there is no control over the type of content I want users to be able to post to Spaces.  I hate to keep picking on the Recipe module, because it's a great module for the site in general. but it has no business in 'Spaces' as I intend to use them.  I can remove 'Recipes' easily enough from the Spaces navigation menu, but when I place a system block like that Create Post (Context), there's the Recipes, on the menu (No pun intended)

                              What I really need, in fact what everybody needs, is:

                              1. A method to post content directly to 'Spaces'

                              2. Admin controls over what types of content are to be posted to Spaces

                              There's other odd behavior of Spaces and Groups, but these two things have me dead in the water.

                              A Bare minimum solution would be a new system block, let's call it "Create Post (Spaces)" . Let's say this block would work off the content items I have enabled on the "View Space Submenu" ,  Preferrably, the 'Add New..' would be placed on the space navigation menu so that it's always visible.

                              We'll release this feature in UNA 13 and already implemented this feature in dev version, it's Roles Builder for groups based module (Studio > Forms > Roles), you can already test it if you install current development version from the repository.

                              Login or Join to comment.