Lotus and the IBM Redbooks authoring team have partnered together to populate this wiki with best practices from IBM, partners, and customers. This combines the quality and reputation of Redbooks publications with the dynamic and collaborative wikis that Lotus has published. Wikis are a relatively new Web browser-based technology that allows people to easily publish new and updated information as well as add comments, which results in technical information that is more accurate and current.
This is a community wiki. You are welcome to contribute to the existing pages or add new pages. Everyone is welcome to share their experiences and knowledge with the rest of the community. Because this is a relatively new type of deliverable, we welcome you to rate this deliverable and provide us with your feedback.
This community wiki focuses on best practices for building Web applications for Domino 8. Here you will find key recommendations for updating existing Domino Web applications, best practices for refining Domino application look and feel for the Web, and common tips and techniques.
Lotus Wiki: Best Practices for Domino 8.0 Web Application Development
Note: In order to contribute or comment on this wiki, you must login to the wiki. You can register for a free login user ID directly on the wiki home page.
This wiki contains the following table of contents:
2.0 Getting started
3.0 Understanding the Domino design elements
4.0 Building Domino Web applications
5.0 Extending rich client applications for Web clients
6.0 Server configuration
7.0 Developer tools and resources
In addition, a snapshot of the original content in this wiki was created in March 2008 in the form of a PDF file which you can access at the following link:
View PDF file of the original wiki content
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.