Lotus Technical Information and Education Community Kickoff

download Lotus Technical Information and Education Community Kickoff

If you can't read please download the document

Transcript of Lotus Technical Information and Education Community Kickoff

IBM Presentations: Blue Pearl Asterisk template

WhoWhatWhen

Wiki development TeamMeet with Steve Castledine (Open NTF Chef) on process for IDC to participate
(Contribute to Open NTF: a) IDC reqs, b) IDC code to community, c) community code to IDC)

Q1 - 2/5/2009

Wiki development TeamAssess Domino 8.5 Xpages to size work required to move to new template Necessary before plan dates can be definedQ1 - 2/20/2009

Wiki architecture and development TeamPrioritize current set of wiki features to determine what would be developed in an upcoming Domino 8.5 iteration or we would wait for Quickr

Q1 Preliminary assessment is complete as of 1/30/2009- Scheduling reviewed with wiki IAs and leadership team

Wiki development TeamJoin Lotus Connections 2.5 design partner program

Q1 tentatively starts 2/27/2009

Product doc Action TeamPresent initial requirements that will be used to help assess strategic wiki platform for product documentation

Q1

Product doc Action TeamPresent potential workflows and process for product documentation in wikis.

Q1

Wiki translation Action TeamPilot Chinese and Portuguese Brazil wikis

Q1

Product doc Action TeamPresent prioritized designs for wiki features necessary to move product documentation to wikis

Q2


Community Kickoff Meeting


May 26, 2009

Lotus Technical Information & Education Community

Who we are

Lotus Information Development Center

IDC Mission:

Develop and deliver information that helps our customers, partners and IBMers get the most out of Lotus and WebSphere Portal products.

Joyce DavisCommunity Managertwitter.com/jadintx

Agenda

Community orientation

Community member spotlights

Chris Toohey, Clearframe LLC, Inc.

Paul Bastide, IBM

Special topic Domino XPages design preview

Q&A

Community building strategy

Goal: Grow, enable, and encourage the community to expand and improve Lotus and WebSphere Portal technical content

Supporting roles

Community manager

Community advocates

Wiki program manager and wiki leads

Communication & education

Social media

Incentives to drive contributions

Ongoing customer feedback

Vision:

A self-sustaining and vibrant online community, driven by subject matter experts inside and outside of IBM.

Community Manager Joyce Davis

Establish community building strategy

Serve as point person for community advocates

Coordinate community meetings

Communicate community benefits and successes to wider stakeholder groups

Drive participation of internal IBM community members

Wiki Program Manager - Amanda Bauman

Communicate wiki development plans

Listen to feedback from community advocates, take feedback to appropriate teams

Field questions and serve as point of contact for wiki program

Manage wiki submissions for author achievement program

Wiki lead responsibilities

Measure success of wikis

Test new wiki features

Wiki content development

Monitor wiki content

Social media to build community

IBMers

Business Partners

Customers

Blogs

LotusConnections

@LotusTechInfo (all products)

Product wikis

Lotus Greenhouse

Showcases Lotus' emerging technology

Lotus Connections for community management & collaboration

Profiles

Communities

Blogs

Dogear

Activities

Lotus Sametime to chat with members

Lotus Forms Turbo for community surveys

http://greenhouse.lotus.com

Building community action team

Cara Viktorov, IBM

Information Developer, IBM Lotus ActiveInsight

Goals:

Drive use of social media to facilitate community interaction

Enable the community through communication and education

Increase contributions and contributors through incentives

Lead customer feedback activities

Anna O'Neal, IBM

Information Developer, IBM Mashup Center

Community member spotlight

Chris Toohey, Clearframe LLC, Inc.

Lead Community Advocate

Paul Bastide, IBM

Technical Enablement, Symphony

Lotus product wikis

Wiki for every Lotus & WebSphere Portal product

Domino-based wikis hosted on dW:Lotus

Any registered user can contribute and edit content (LDD login; same as forums)

Over 1,100 contributors

Over 4,200 contributions

Experience-based information

Subscribe to RSS feeds for any new content, or just certain categories

http://www.ibm.com/developerworks/lotus/community/wikis.html

XPages wiki design preview

Jennifer Heins, IBM

Wiki and Technical Content

Architect and Strategist

Introducing the new Domino 8.5 XPages Wiki Template

A new spotlight section has been added to the right side of the page.

Article views have been updated to include more information, making it easier for you to determine which article is most relevant to you.

Updates to the wiki user interface continued (1 of 2)

Updated One UI design

New Media gallery

Collapsible sections in the navigation

New Article views

Tagging section includes a slider, total number of tags

New One UI footer

Forgot user name / password

Issues that are fixed:

In the current wikis, when you add graphics via the Notes client you can simply copy and paste them in, just as you would in an email. This was fine until someone edited that article from the Web. Then the graphics would disappear after the article was saved.

With the new template, graphics are always added as attachments and then referenced via wiki markup, regardless of where you create or edit the article, whether in Notes or on the Web.

Support for inline bracketed code samples is achieved using wiki markup if you would like the code samples to be formatted to look like code samples. You use the wiki markup code tags. You can specify alternate line highlighting and numbers. If you simply want to allow bracketed code to pass through unrendered, you can use the {{no wiki}} tagging. This will treat the contents inside the brackets as text and the browser ignores any HTML type tags.

Updates to the wiki user interface (2 of 2)

Updated article listing

Show originator

Date created

Tags

First paragraph of article

New spotlight section

Wiki leads can update this to highlight time
sensitive articles, or popular articles

6 customizable boxes where wiki leads feature
information for the wiki and the product

A new spotlight section has been added to the right side of the page.

Article views have been updated to include more information, making it easier for you to determine which article is most relevant to you.

Getting around the wiki

New views:

Alphabetical

Recently added

Recently edited

Articles I created

By author

Pagination of results: search
results and categories

Breadcrumbs on articles

Friendly URLs based on article name

Issues that are fixed:

In the current wikis, when you add graphics via the Notes client you can simply copy and paste them in, just as you would in an email. This was fine until someone edited that article from the Web. Then the graphics would disappear after the article was saved.

With the new template, graphics are always added as attachments and then referenced via wiki markup, regardless of where you create or edit the article, whether in Notes or on the Web.

Support for inline bracketed code samples is achieved using wiki markup if you would like the code samples to be formatted to look like code samples. You use the wiki markup code tags. You can specify alternate line highlighting and numbers. If you simply want to allow bracketed code to pass through unrendered, you can use the {{no wiki}} tagging. This will treat the contents inside the brackets as text and the browser ignores any HTML type tags.

Updates to articles

Updated article design

Moved article information to the bottom

Type ahead tags

Authors can delete attachments
on the "Web"

Article revisions are numbered,
along with date and time

Issues that are fixed:

In the current wikis, when you add graphics via the Notes client you can simply copy and paste them in, just as you would in an email. This was fine until someone edited that article from the Web. Then the graphics would disappear after the article was saved.

With the new template, graphics are always added as attachments and then referenced via wiki markup, regardless of where you create or edit the article, whether in Notes or on the Web.

Support for inline bracketed code samples is achieved using wiki markup if you would like the code samples to be formatted to look like code samples. You use the wiki markup code tags. You can specify alternate line highlighting and numbers. If you simply want to allow bracketed code to pass through unrendered, you can use the {{no wiki}} tagging. This will treat the contents inside the brackets as text and the browser ignores any HTML type tags.

Updates to editing (1 of 3)

Improvements to basic formatting such
as nested lists

Wiki markup for headings:

Heading 2: ==My heading 2==

Heading 3: ===My heading 3===

Heading 4: ====My heading 4====

Automatic table of contents when wiki markup is used for headings

A table of contents is created automatically based on headings.

You use wiki markup to create headings. An = sign indicates the heading level, so for example, a heading 2 is enclosed in 2 = signs on either side of the heading text, heading 3 is enclosed in 3 = signs, and so on...

The example here shows headings 2 through 4 in wiki markup and the resulting headings.

Updates to editing (2 of 3)

Links:

[[|]]

[[link to a wiki page]] creates a new page if one with specified name is not found

Icon that indicates when a link goes outside the wiki when wiki markup is used

Images:

{{image.jpg|title}}

With positioning: {{image.jpg|title|align="right"}}

Tables:

|= for headings; | for cells:

|=|=column 1|= column 2|=Column 3

|=Row1|cell 1|cell 2|cell 3

|=Row 2|cell 1|cell 2|cell 3

Updated editing: Wiki markup for links, images, and tables.

Use wiki markup to create links, images and tables.

You create links by enclosing the URL and alias in double brackets. A pipe separates the URL from the Alias. If a link is external, a small icon appears next to the link.

Images must be attached to the article as attachments and referenced using wiki markup. You can also position the image using the align property.

Tables are created using wiki markup: a heading is specifies by =| and a cell is specified by using |. The example here shows the markup and the resulting table.

Updates to editing (3 of 3)

Improvements to bracketed inline code
samples using wiki markup:

For inline code samples:

no wiki option

{{{}}}

For larger code samples:

Code identifier {code:type|flag|height|width}

Basic code is {code:}{code} in the future
{code:xml} will mean it will format the code automatically as xml.

Specify a flag "a" for alternate lines

Specify a flag "n" for line numbering

{code:|an}{code}

Issues that are fixed:

In the current wikis, when you add graphics via the Notes client you can simply copy and paste them in, just as you would in an email. This was fine until someone edited that article from the Web. Then the graphics would disappear after the article was saved.

With the new template, graphics are always added as attachments and then referenced via wiki markup, regardless of where you create or edit the article, whether in Notes or on the Web.

Support for inline bracketed code samples is achieved using wiki markup if you would like the code samples to be formatted to look like code samples. You use the wiki markup code tags. You can specify alternate line highlighting and numbers. If you simply want to allow bracketed code to pass through unrendered, you can use the {{no wiki}} tagging. This will treat the contents inside the brackets as text and the browser ignores any HTML type tags.

Next Steps

Monthly community meetings (4th Tuesday)

Topics for future community meetings:

Becoming a published author with IBM Press

Using social media to share technical content

Join Lotus Greenhouse (greenhouse.lotus.com)

Join the Lotus Technical Information & Education community

Add the Lotus Greenhouse server community to Sametime
(host server: sametime.lotus.com)

Complete your profile in Lotus Connections Profiles so that others will know your area of expertise and interest

Participate in the community!

WhoWhatWhen

Product doc Action TeamPresent initial requirements that will be used to help assess strategic wiki platform for product documentation

Q1

Product doc Action TeamPresent prioritized designs for wiki features necessary to move product documentation to wikis

Q2

Product doc Action TeamPresent potential workflows and process for product documentation in wikis.

Q1

Wiki architecture and development TeamPrioritize current set of wiki features to determine what would be developed in an upcoming Domino 8.5 iteration or we would wait for Quickr

Q1 Preliminary assessment is complete as of 1/30/2009- To be reviewed with wiki IAs and leadership team

WPLC Information Development Center 2009 IBM Corporation

WPLC Information Development Center

2009 IBM Corporation

IBM Confidential 2009 IBM Corporation

STORY TITLE

Click to edit the outline text format

Second Outline Level

Third Outline Level

Fourth Outline Level

Fifth Outline Level

Sixth Outline Level

Seventh Outline Level

Eighth Outline Level

Ninth Outline Level

2009 IBM Corporation

2009 IBM Corporation