nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project Start

Nidhi_Agrawal

Hi All,

If in my project it is needed to store all information in database, then it is good or not to make its Interwoven implementation.
But contents are created for the site very frequently.
Site is linked with multiple sites thats why it is necessary to store whole data into the database.

Thanks in Advance for help.
Please send me your suggetions.

Nidhi A...

Find more posts tagged with

Comments

Bhargav Coca

Indeed, if you have a site which is updated "very frequently" then Interwoven is one of the Best option.(After all Teamsite was created for this basic general neccesity)

Having said that, there are any factors which decide what goes into Teamsite and what is left out and how you want your "Staic" Content varyinf trough out the site from different databases.

Simple set up as follows
Simple DCT being Populated, DCR getting deployed and XML is aprsed to the DATABASE uisng simple standalone deployment and your third party application providing security and reads from db to populate the site.

Complex thing is left to your Imagination.......

Such Projects need good organization (Architectural Design) and Good to Perfect Documentation after implementation.

Thanks

chicka

Hi All,

If in my project it is needed to store all information in database, then it is good or not to make its Interwoven implementation.
But contents are created for the site very frequently.
Site is linked with multiple sites thats why it is necessary to store whole data into the database.

Thanks in Advance for help.
Please send me your suggetions.

Nidhi A...

Hey Nidhi,
your last statement is impressive.
"Site is linked with multiple sites thats why it is necessary to store whole data into the database."
This is the place where DB layer comes into picture. On a long run basis DB integration will give good results w.r.t easy maintenance as well as enhancement.
Also as mentioned, it depends on how complicated business requirement you have. There are many projects implemented from my end, which uses TS to push the data to DB using DD alone. In frontend, JSPs are used from APP layer to render the page.
Please let me know if u need further clarification.

moonkhanna

Hi All,

If in my project it is needed to store all information in database, then it is good or not to make its Interwoven implementation.
But contents are created for the site very frequently.
Site is linked with multiple sites thats why it is necessary to store whole data into the database.

Thanks in Advance for help.
Please send me your suggetions.

Nidhi A...

Teamsite gives you a Business User's interface to the Web Site content. Wether or not your company requires this is a Business Decision. Benefits of Teamsite when DB is intermediate could be classified as follows -

1. Business User's interface to Web Content
2. Frequent updation made easier
3. Enables Scheduled Updations easier
4. Forces you to Define and Structure your Web Content
5. Typo errors by Developers are avoided
6. Creates a process workflow for Content Updation as per your Business Scenario
7. Broken web sites can be healed

In a CMS Developer's language, how else would you do all the above and in fact even insert data into your Database?

Note - Point 1 looks simple but is highly complicated.

Nidhi_Agrawal

Hi,

If I want to use teamsite for entering the data and also for rendering the data then i have to keep data at two places (in database and in DCR).

I can't avoid database at all as i have to put my whole data in to database.
And read everytime database for rendering the data is not looking nice idea.

So i have to keep same data in two places.

Thanks,
Nidhi A..

Mr_Cruise

There are many problems with a Content Delivery Architecture (CDA) that is database centric. The main one being that if you want to add a new field multiple layers will have to be amended. The other big issue is that when you have a combination of database and file data, the whole deployment process becomes very complex. I'm not saying all this to put you off but unless you know what you are doing you will soon get stuck.

You are better off simplifying the CDA and use something like XML and XSLT. This CDA can offer you content aggregation, expiry and personalisation. I would recommend using something like cocoon, which is also free!

Best of luck

Lee

ISCBorisB

You are better off simplifying the CDA and use something like XML and XSLT

Nidhi indicated from the start that "it is needed to store all information in database".

You have no slightest idea about his Project but you already know what delivery model is *better* for him, that's interesting.
*Better* by what metric? By your logic, DB-centric models may as well not exist, it is always "better [...] use something
like XML and XSLT". Really? I would love to see your implementation of 4NF model using *something like XSLT*.

ISCBorisB

Hi,

If I want to use teamsite for entering the data and also for rendering the data then i have to keep data at two places (in database and in DCR).

I can't avoid database at all as i have to put my whole data in to database.
And read everytime database for rendering the data is not looking nice idea.

So i have to keep same data in two places.

Thanks,
Nidhi A..

Although it can be done, TeamSite IMO is not a stellar choice for the DB-centric CMS implementation.
You may want to take a look at (for example) Rhythmix CMS by Percussion, they store content in RDB, schemas are user-controlled.