As we start planning for future releases of IBM Connections, we wanted to understand how users, for example, are using Wikis to ensure that we are investing in the right areas. Just like it doesn't make sense to invest in Internet Explorer 6 these days, we want to know how users are leveraging the editors in the Wikis component of IBM Connections.
Currently, we support 3 editors in Wikis: Rich Text Editor, HTML Editor, and Wiki Text Editor. The three approaches to editing content are very different from each other and conflict at a fundamental level. Rich text editing and HTML editing gives users free control over their styling and formatting whereas wiki text is specifically designed to restrict this freedom in preference for consistent document semantics. Since Wikis allows one page to be edited in three different formats, a conversion process must take place. Converting from wiki text to rich text is relatively easy since wiki text is much less expressive than rich text (HTML). Converting from rich text to wiki text is a very different problem. A lot of content can be expressed in HTML that cannot be expressed in wiki text.
Wikis currently allows for lossless conversion from rich text to wiki text by escaping anything that cannot be converted and leaving it in a HTML form, embedded within the wiki text. A caveat of this is that the wiki text content becomes less useful as more HTML is escaped within it. The task of maintaining this wiki conversion is very expensive and difficult and we would like to spend the development time on nicer new features ;-)
We'd like to know what you think and how the community is using wiki text in IBM Connections Wikis right now. And while we are at it, it would be good to know what would be your top feature request for Wikis.
Sun, Nov 11th 2012 1:42p Joseph Russo Today I needed to contact a colleague and was using SMS text to make the contact. In doing so, I was immediately struck by my behavior. Normally I would use Sametime to interact with my friend, but, due to being mobile (walking down the hall) I was using text instead. What I noticed in my own approach was this. When I "cold call" someone over Sametime, I always use what I'll call the "Accepted Social Interrupt Protocol" ASIP - I start with a simple "Hi", wait for a response, engage in a b [read] Keywords: sametime
IBM Connections: Are you experienced?
Mon, Sep 10th 2012 7:22a Suzanne Livingston The IBM Collaboration Solutions UX/ID team is proud to announce the Experience IBM Connections site. This single-page, external site is intended to drive user adoption of IBM Connections and enhance the total client experience. This effort was inspired by feedback from customers requesting materials to help promote Notes to end users. The site includes tips and resources to learn more. It also highlights favorite tips and features from select IBMers and IBM Champions. http://learn.lotus. [read] Keywords: collaboration
IBM Sessions at SXSW 2013
Thu, Aug 16th 2012 8:46a Suzanne Livingston It's voting time! Here are the IBM sessions being proposed at SXSW 2013. Please vote for your favorites and do let me know if there are any missing! Getting Away With It: IBM Social Sells the Cloud Social and Relationships Dual Are You a Hackerâs Dream? Social, Mobile Safety Social and Relationships Dual Are you RAD enough? (Rapid Accessible Deployment) Design and Development Dual Corporate Culture Shock: when strategy isn't enough Entrepreneurialism and Business Pane [read] Keywords: ibm
Please vote for our sessions at SXSW 2013!!
Mon, Aug 13th 2012 12:46p Suzanne Livingston SXSW opens its PanelPicker app today for choosing your favorite sessions for consideration in 2013. It can be daunting to read though and vote on 3500+ sessions, so we'd like to help you find our sessions! Please vote for our sessions! Yes, that TPS Report can be social too - http://panelpicker.sxsw.com/vote/582 At your job, your have access to a lot of information throughout many systems. Imagine if you had a single, social stream of updates from all the applications you worke [read] Keywords: synch.rono.us
Intuition is a smokescreen
Wed, Aug 1st 2012 4:49p Joseph Russo Often times in design you will here people say something is intuitive or, maybe more often, something is not intuitive. And frankly, I've often found this is merely a smokescreen, to cast something they don't like and have solid argument to reason why they don't believe in the design. This happens because for some reason, people have learned that saying that something is "not intuitive" is somehow really important to design. And I want to be clear, we're talking about software here. An [read] Keywords: synch.rono.us
Pocket Veto â the unspoken tenet of Social Software
Fri, Jun 29th 2012 11:30a Joseph Russo Ok, just to be a pain, I'm starting with civics lesson. In the United States, there is a process by which âbillsâ become law. The House of Representatives vote and if the majority agrees, the bill passes to the Senate. They vote and if majority agrees it goes to the President. He can sign the bill, making it a law, or he can veto it, and it goes back to congress for rehashing...or if it's near the end of the term, he can simply âpocket vetoâ it. This allows him to safely do [read] Keywords: synch.rono.us