|
|
I noticed that since the upgrade to 852 the xpages wiki application does no longer support wiki markup in rich text.
what is a wiki application worth when it does not support wiki markup???
problem reported here also:
http://bit.ly/h9AAFF
|
|
|
Add the Facebook Like (iFrame-version) to Wiki Post footers to allow readers to click-to-share useful articles and help promote contributions beyond the typical reach of the "yellow bubble".
It's a single line of JavaScript and you're done.
|
|
|
We in the roundtable came up with a way to help promote content in wiki's. Templates. new idea for notes people. Templates, faq's and wizards. Formating tools to help choose the right format for articles, faq's, wiki entries, questions, procedures, etc. This would help people who are not writers create content.
|
|
|
I've been in SL for years now and have attended LS in the virtual site IBM/lotus had for LS. Across the street. They had, I just found out that IBM has all but pulled out of SL, a office building that housed product information and redbooks. All the land is
|
|
|
I read the Lotus Wiki's and completely forget that I am entitled to make my own contributions there. Help Lotus encourage participation and expert posts by community members by putting a large, friendly, "Contribute Now!" button at the top of every page. It can say "Post your own article" or something of that
|
|
|
A quick glace through wiki pages containing example code ( example) proves a systemic usability problem.
The wikis should recognize code (through a code tag? through any <pre> tag where the contents start with a less-than character?) and automatically convert/highlight the code.
Syntax highlighters are usually done via JavaScript. Here's one example:
|
|
|
It would be helpful to have something like the following at the bottom of the various devWorks forum, blog, wiki pages to offer readers a simple UI ability (good example at bottom of this page) to tweet and otherwise easily push a forum/wiki post to other target forums/wiki/communities:
|
|
|
Answers posted in the forums can be great candidates for wiki articles. Make it easy to
create wiki articles from answered forum posts. For example, provide a button in the forum post that
opens a new wiki article in the corresponding wiki.
|
|
|
When someone posts a question in the forum, search the corresponding product wikis for related articles that might answer it. Suggest links right as the forum post is created.
|
|
|
Part of the value of a redbook has always been the organization and flow of the material. The team writing the redbook would know the content they needed to produce and would provide an organization structure for how they would proceed through the material.
If there's a Lotus Domino Designer Wiki,
|
|
|
I have lost track of how many Lotus Wiki solutions are now out there, but it seems like there are quite a few. I can appreciate that we need to have separate wiki implimentations for Lotus Connections, Lotus Notes etc, but why do we need to have completely different markup
|
|
|
On the Lotus ID wikis, give top non-IBM contributors their own personal wiki page. They can use the page for almost anything they want... as a contact page, an online brochure for their company and their products, a company announcement page, or whatever. Contribution can be measured by number of
|
|
|
A customer posted a feedback comment stating that the "Using ESM in a cluster" documentation is confusing unless you have a comprehensive understanding of TAM. After speaking with the ESM and Cluster developers, it was decided that this is too complex to describe in the InfoCenter and would be best
|
|
|
It would be great if there was a migration toolkit that allowed organis[z]ations who already have exisiting wiki content to be able to migrate to connections.
My company for example has deployed Confluence by Atlassian as the IBM/Lotus portfolio has lacked a decent wiki. If there was a migration path/tool it
|
|
|
With the upcoming 2.5 release of Connections, the new wiki engine certainly looks the goods. The issue is, many peole have already deployed Wiki software and it may be problematic to support two engines.
I would like to see a Wiki migration tool so that we can import content from existing
|
|
|
Create language-specific product support wikis off of the main (English) wikis and let the native language communities grow the content. The wikis should be 'seeded' with the most basic outline already provided in the native language and then customers, consumers and interested IBM/Lotus sales, support and development personnel can translate existing content into there, write
|
|
|
Becomming good enough in those things ajax is kind of a learning curve. Now Lotus has anounced that dojo is their favourite library. And I think this anouncement creates interest in dojo even among us more or less proficient prototype, jquery,ex.nd users or pure-javaScript aficionados. As a bibliophile developer I
|
|
|
A new wiki has been set up to help people plan and have fun around Lotusphere.
It won't work if you don't go play. Everyone gets to be an editor!
Go make good things happen, people. I set it up, but I've totally opened it and left it open
|
|
|
In the Domino 6 & 7 forums, we're always redirecting newbies back to existing questions. It would be cool to have a repository for routines with some sort of structure.
Example of structure....
Exporting
- To Microsoft Excel
- To Lotus 1-2-3
- To MS Word via DDE
- To CSV
That would give us somewhere
|