Search DominoPower's 11,441 Lotus-related article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
Building an XML based Content Management System using Lotus Domino: overview of the content administration system (continued)

If you want to build a large sized Lotus Domino application and you want it to be maintainable, understandable, expandable, functional, and simple, then you must use clear plastic crates. More specifically, you have to put work into making the whole Lotus Domino application fit together smoothly. You have to try hard to make everything as consistent as possible, and you have to try to simplify, wherever possible. Make it simple, simple, simple. The simpler your solution is, the less likely there are to be errors and the easier it will be for you or anyone else to understand.

You want to be able to go inside the application and quickly and easily see how things fit together and make modifications that won't break the rest of the system. You need consistent naming conventions for all database design elements including forms, views, agents, subforms, whatever. More importantly, you need to put a great deal of thought into the underlying structure of the Lotus Domino documents that will be stored in the database. Again, make it simple. Look for ways that you can make things more generic. Be consistent. Label everything clearly.

It takes a lot of work to maintain such consistency, and it takes even more work to establish consistency in an existing Domino database. The rewards are huge, however, especially if it's an application that you'll be spending a lot of time working within. You'll find that changes and fixes take much less time to implement, major new functions and features can be easily implemented, bugs and errors will take much less time to track down, and the new programmer in your department will be able to come up to speed on the application in much less time. Just like the crates, make the source and structure of your application transparent, easy to move around, easy to stack, and nice to look at.

Content administration
This month we're going to be taking an overview snapshot of the Lotus Domino based content administration portion of the content management system. Specifically, we'll be looking at the Lotus Domino documents that are stored in the content management system's database.

The good news is that there are only four different types of Lotus Domino documents stored in the database. The fact that there are only four different types of documents points to a very committed effort to reduce complexity and to make things as generic as possible. The four documents are:

  • Content document: this is an individual "page" within the Web site;

  • Menu document: each menu item has one document;

  • Text properties document: a set of font, size, style, and color definitions for each page element such as headline, body text, footer, etc.;

  • Site configuration document: contains global settings to be applied across the entire site, such as the background image, the home page, the default global text properties scheme, the default logo, etc.


« Previous  ·  1  ·  2  ·  3  ·  4  ·  Next »
Other articles you might like
Home > Internet Technologies > XML (11 articles)
   How to create a Web service to extract data from XML documents
   Building an XML based Content Management System using Lotus Domino: wrapping it up
   Building an XML based Content Management System using Lotus Domino: overview of the HTML display template
Home > Strategies > Content Management (10 articles)
   Lotus acquires Aptrix, announces Lotus Workplace Content Development
   Building an XML based Content Management System using Lotus Domino: wrapping it up
   Building an XML based Content Management System using Lotus Domino: overview of the HTML display template
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent DominoPower Articles
Application development, William Shatner, and the origin of the universe
Learn Domino Designer 8.5 for free
The (near) future of Sametime, Quickr, Connections, and Symphony
Inside the IBM Innovations lab
Lotusphere 2010: Hot fixes and cool news for Notes, Domino, and LotusLive
Lotusphere 2010: mobility and collaboration
2010: A Lotusphere of change
Latest Lotus Headlines
Xpages not loading? JVM errors? - Solution
How to implement an iCalendar feed into your Notes calendar with XPages
DWA Hotfixes for Domino 8.5.1FP1 - A Gotcha
IBM Adds DB2 to Lotus Foundations SMB Package
SNTT : XPages onclick Ghosts in the machine
Ports used by Lotus Sametime 8.5 servers
Exploring a Domino Date Bug
>> Read all the news
More from the ZATZ journals
Computing Unplugged: The iPad defenders have spoken
David Gewirtz Online: CNN commentary and analysis
OutlookPower: More about disappearing text
-- Advertisement --

Find unused Lotus Notes groups and clean up your address book
Have you ever wanted to get rid of old Lotus Notes groups that were cluttering up your address book, but you weren't sure if they were used? Find Unused Groups can help.

Find Unused Groups will check your ACL, mail, multi purpose and server groups to help you determine if they are used, and who uses them.

Learn how to easily clean up your address book.

-- Advertisement --

Teamstudio Edition 25 has shipped
It's finally here! Now that Teamstudio Edition 25 has shipped, listen to our latest Tool Time audio program to find out what's changed. Updates to all your favorite Teamstudio tools will be discussed.

Plus, you'll get an introduction to Teamstudio Undo (formerly known as Teamstudio Snapper).

Tap here to get started!

ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 1998-2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login