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; } } }

Interwoven or JSPWiki?

HeMan10

Hi,
Here is an interesting question that the Enterprise Architect at my clients has come up with. What exactly Interwoven provides me that JSPWiki doesn't? Let me explain a little bit of the set up that we have here. Theres only one TeamSite user who takes care of all the creation and maintenance of data. So theres no workflow involved. Templating and open deploy are being used. His plan is to use JSPWiki instead of Interwoven suite and just maintain the data in a database and use it on the site. That way he could avoid a lot of steps in between like submitting it to the staging, cutting an edition and then deploying, as the set up here is very simple.

Can anyone give me some pros that Interwoven has in the simple set up that this client has? Any feedback is appreciated.

Thanks
-H

Find more posts tagged with

Comments

gzevin

Hi,
Here is an interesting question that the Enterprise Architect at my clients has come up with. What exactly Interwoven provides me that JSPWiki doesn't? Let me explain a little bit of the set up that we have here. Theres only one TeamSite user who takes care of all the creation and maintenance of data. So theres no workflow involved. Templating and open deploy are being used. His plan is to use JSPWiki instead of Interwoven suite and just maintain the data in a database and use it on the site. That way he could avoid a lot of steps in between like submitting it to the staging, cutting an edition and then deploying, as the set up here is very simple.

Can anyone give me some pros that Interwoven has in the simple set up that this client has? Any feedback is appreciated.

Thanks
-H

ONE USER? for the whole enterprise-level system?

common, tell us you are kiddin' Smiley Happy

drew1

Can anyone give me some pros that Interwoven has in the simple set up that this client has? Any feedback is appreciated.

Even in the simple scenario you've described, TeamSite has plenty of useful features.

* Site versioning. TeamSite will keep track of what the client's website looks like at any point in time, and allows the entire site to be rolled back to a prior snapshot.

* Ability to preview the web content before deploying to production.

* Workflows can be setup to automate single-user tasks like link checking, or spell checking, not just multi-user review scenarios.

Hope this helps,
Andrew

HeMan10

Thanks for the replies. Even though we have a lot of business users, only one guy, content manager, takes care of all the content creation, deploying it to QA and production. For versioning the Architect says that he can back up the database and roll it back to a particular day. So he doesn't think that doesn't add much value. The capability to preview the web content also doesn't impress him as he is changing the web content straight away in wiki set up and he can see it there and then itself. We are not using workflows anyway in this set up.

Any more advantages of Interwoven please?

Thanks
-H

dkuntze

Any more advantages of Interwoven please?

The are tons of advantages to using a enterprise CMS. Many of the features may be overkill if you only have one primary developer. Although, when I was doing one-man development "back in the old days", I would have been mighty pleased if I had a tool like TeamSite.

Here are some benefits I'd see over a standard wiki:

100% control over templating -- output any language you wish: php, asp, jsp, etc...

Workflow -- even though you aren't using it, there is value to at least integrating your deployments into it.

Versioning -- most wiki's version content, but TeamSite versions everything. Templates, data... everything in the repository. If you have some sort of compliance dept. this is a very big deal.

Shared content / reuse -- if set correctly, you can share content from site to site.

localization/internationalization -- you can set up sites to output multiple version of pages/content. This includes mobile versions.

There are, of course, more benefits that I can't think of... I'm sure some of the others he could add their two cents.

drew1

Thanks for the replies. Even though we have a lot of business users, only one guy, content manager, takes care of all the content creation, deploying it to QA and production.

It may be one guy today, but next year maybe there'll multiple users, or maybe you'll have a different content manager. Businesses grow, requirements change, staff changes. I argue that TeamSite will be a more flexible and scalable solution than JSPWiki.

For versioning the Architect says that he can back up the database and roll it back to a particular day. So he doesn't think that doesn't add much value.

I'm glad your Architect is backing up his database, but TeamSite's solution is easier to manage. Every published edition looks just like the entire site -- a rollback consists of deploying the previous edition to the production site.

The capability to preview the web content also doesn't impress him as he is changing the web content straight away in wiki set up and he can see it there and then itself.

Why bother with any content management at all, if he's making the changes directly on the live site? The point of TeamSite, or any configuration management system, is that you can preview changes within the context of the *entire* site. If links break, you can catch that before it goes on your production site. If indexes need updating, you can be proactive and fix it.

Any more advantages of Interwoven please?

* As dkuntze points out, compliance is becoming a bigger and bigger issue for organizations.

* The ability to use standard html & standard html authoring tools instead of wiki markup.

hope this helps,
Andrew