I've been contacted by a blog reader that our way to use 'categories'/'tags' which show up in the right column is not very helpful. They are supposed to be used to navigate to certain entries and should not be used to define the author names. I agree with this assessment and propose that we define some conventions and then change the existing entries.
I still think that we need to use the author name as one of the categories since there are many different authors in this blog. I suggest however that we only use the last name.
Additionally I think it makes sense to use one of the following categories to define about which product the entry is about:
'Notes80'
'Notes801'
'Expeditor61'
'Expeditor611'
'Portal60'
'Portal61'
'LCD60'
Furthermore I think we should only use a well defined set of other categories:
'FAQ'
'Strategy'
'Tutorials'
'Samples'
'Conventions'
'Questions'
'BlogRules'
'Else'
Let me know what you think. If we can agree on this set I offer to do the changes to all existing entries.
Niklas[Read More]
Bring information and collaboration into the context of your daily business processes using composite applications
Matching:
blogrules
X
X
Usage of Categories in Blog |
Welcome to our blog
[UPDATED 11/28/06 by Jeff Calow to remove references to the internal division name that was causing confusion and added links to product home pages]
Welcome to our new group blog. It brings together all the key technical architects and user experience design professionals for the major products from the Lotus software division that provide support for user facing composite applications. These products include IBM Websphere Portal 6.0, IBM Lotus Notes 8.0, IBM Lotus Domino 8.0, IBM Lotus Expeditor 6.1 and future products to be named when they are announced. The folks that will be helping with this blog on a regular basis are: Art Thomas -> Lead architect for Domino administration Bob Balfe -> Lead architect for Portal projection in Expeditor Brian O'Donnovan -> Overall development manager for user facing composite applications Craig Wolpert -> Lead architect for Notes/Domino ISV enablement Eric Masselle -> User experience designer for composite application editing and portal document workflow Jeff Calow (me) -> Chief architect for user facing composite applications Kristina Beckley -> Lead user experience designer for composite applications in Notes/Domino Niklas Heidloff -> Lead architect for composite applications in Notes Peter Fischer -> Lead architect for Application Infrastructure in Portal Stanley Dunne -> Lead architect for composite application composition tools Thomas Stober -> Release architect for the next version of Portal The impact of composite applications is so broad that we will also be having many guest speakers from across our product lines. Our goal with this blog is provide a personal, direct line of communication between experts working in this exciting and often confusing technology area and our customers and partners. Each poster brings their own diverse perspective and ideas to the conversation, so don't expect a marketing pitch or a single voice or style :-) We'll also be "trying out" various ways of explaining what we are doing and why, so we value your feedback in helping refine our technical story to be crisp and understandable. We'll also be posting direct questions to gather your feedback in time to affect ongoing product plans. It's important to note that none of us speak officially for IBM, nor can we make product commitments or discuss products that have not been announced. As a way of starting the conversation, each of the regulars will be posting a short bio of themselves and then a short description of how the product they are associated with fits into the Lotus software composite application strategy. We'll then be posting about topics that we find personally interesting as well as looking out into the industry. If you have a topic that you're burning to get information about, let us know. Thanks, The Lotus software Composite Application Team [Read More] |
