You are hereadvanced features / groups / Digital Vision Fellows Group / Should all public posts go on the RDVP frontpage?
Should all public posts go on the RDVP frontpage?
Currently, every public blog post appears on the rdvp.org frontpage. Does that make sense?
I've been talking to some people about this and wanted to get others' feedback on the idea that you would like your posts to become public (that is, other people should be able to view them without logging in) but that you would not necessarily want them to show up on the RDVP public homepage. My specific example is detailed project progress that our guidelines had suggested we leave off the frontpage. There are pros and cons to adding an option such as this and I list some below. I hope people have opinions about this and that we can work out a decision using this forum (as Vi has recently asked us to do).
Why should fellows be able to decide whether their public posts go on the RDVP frontpage:
- If posting about a project, it allows us to get very detailed in our descriptions because we know readers will be interested in our project
- Allows us to invite people to casually check out our project pages without having to login
- Encourages us to take our progress reports and personal/project musings to the collaboration site as opposed to some other site dedicated only to personal/project posts
Why should all public posts go to the RDVP frontpage:
- All projects and fellows are part of the program, so even if the content is project-specific or personal, it should be highlighted on the frontpage.
- If we don't do this, there will be no posts to the frontpage.
- It makes creating a post more complicated
Please note that I have set up an on-line survey to make it easier for everyone to "vote" on this issue/request. Click here to answer the simple 3 multiple choice questions survey now...
This is one of the most critical issues that fellows want to be addressed. Although fellows currently can select their posts to be private and visible only to members of specific user groups, there seems to be a need for posting content that is public but that is not profiled in the front page.
The need for "Not Private but Not Publicized either"
Why would someone want to post content that is public but not portraitedd on the front page?
If a fellow makes a post private, it's only visible to members of the specific user group(s) he/she selects and is a member of. For users to see this post, they need to be a member of this group.
This creates 2 limitations:
How could this be done
The solution can be as simple as
From the user's point of view, this would be a simple action and we can make sure the user is aware and remembers this by adding a visible note in the form.
From a developer's point of view, option 1 is more complicated, given the way the application works and the way the collaboration framework communicates with the front page (via RSS Feeds). Option 2 (setting up a category) can be implemented immediately if fellows agree on this request.
Another simple question (but more difficult from the programming side) is if by default the "show post on front page" should be selected or not.
Perhaps the Usability Group can provide some guideline or direction toward a user-friendly, minimal impact way of implementing this option.
Fellows should express their preference and also be informed of this change when implemented to make sure they are aware of it and how to take advantage of it.
Implications
The inmediate consequence could be a decrease in the number of posts that make it to the front page as it is usual for people to be self-conscious of their writings and more often than not they may choose not to be portraited on the front page.
On the other hand, it could trigger an increase in the number of posts by the fellows once they feel liberated from been profiled on the front page. Many fellows have explicitely expressed their reserves in posting their ideas to avoid been profiled on their front page.
The Open Space Paradigm
This issue also uncovers another phenomenom: the paradigm of formal content and spaces. For more users, www.RDVP.org is seen as a formal publication and they would not like to be profiled there with a casual comment.
Others, in particular those with past experiences participating in virtual communities, do not see it as such and are comfortable and familiar with casual comments being profiled and constantly rotated on the front page of any publication. Such is the current and acceptable trend of blogs, on-line collaborative spaces such as forums and virtual learning environments and even formal publications such as newspapers and magazines.
More and more, casual posts are not seen as a negative thing, but as an indication of activity and engagement by users and members.
But on the other hand, we should be able to acommodate and serve our users diverse perceptions and preferences.
So another question arises, are fellows only uncomfortable with their posts being portraited by default on http://www.rdvp.org or are they troubled also by their posts being listed on the initial page (and side blocks) of the collaboration framework?
Summary
Please, indicate your preferences...
Note that I have set up an on-line survey with the above questions to make it easier for everyone to "vote" on this issue/request. Click here to go to the simple 3 multiple choice questions survey now...
---
Con paciencia y calma,
sube un burro a una palma
I'm unclear about the distinction being made between visitors to rdvp.org and fellows.rdvp.org. Is there a big difference? Judging from the hits fellows.rdvp.org is getting, traffic seems comparable to the two. So is there something you'd want to mention on one but not the other?
While www.rdvp.org is commonly perceived as an official or formal website for the fellowship, http://fellows.rdvp.org may be perceived as a "collaboration environment", less formal and more appropriate for casual comments or unfinished ideas. But that's entirely up to the users.
---
Con paciencia y calma,
sube un burro a una palma
Post new comment