This is really great stuff and a reason to move to Notes 6. I'm currently using Notes as an IntraNet Solution because of the Rich Text support - we all use Notes mail so folks know how to make stuff look good. The biggest challange in allowing "contributors" to submit content to the web is to get it into html and out to the the web server. Java solutions are simply to expensive and require to many resources, products like InterWoven's TeamSite offer cumbersome and complex solutions. Notes is simple, fast to develop and it really amazes people with how fast and easy it all goes - workflow, security all built in.
The problem is that content comes from many databases and needs to have a single unique look or wrapper. The current solution is to include wrapper elements in all the database, but this is proving to be very unmanagable. So, I want to develop a single wrapper DB that would house the look and feel elements and "pull" content from the various DBs. Stuck on displaying documents without the support servername/DBname/DisplayForm in the URL.
This is really great stuff and a reason to move to Notes 6. I'm currently using Notes as an IntraNet Solution because of the Rich Text support - we all use Notes mail so folks know how to make stuff look good. The biggest challange in allowing "contributors" to submit content to the web is to get it into html and out to the the web server. Java solutions are simply to expensive and require to many resources, products like InterWoven's TeamSite offer cumbersome and complex solutions. Notes is simple, fast to develop and it really amazes people with how fast and easy it all goes - workflow, security all built in.
The problem is that content comes from many databases and needs to have a single unique look or wrapper. The current solution is to include wrapper elements in all the database, but this is proving to be very unmanagable. So, I want to develop a single wrapper DB that would house the look and feel elements and "pull" content from the various DBs. Stuck on displaying documents without the support servername/DBname/DisplayForm in the URL.
Any ideas?