|
Problem
|
Missing images, broken links |
|
Cause |
Interwoven doesn’t track dependencies between assets |
|
You’ve spent days coordinating the release of a series of articles on new
video game. Dozens of pages and images are involved. Your content is part of a
larger deployment involving the work of many other content producers, and your
articles require images that depend on the work of others. You push all your
content out to the staging instance for deployment. Unfortunately, one of the
other producers had to delay release of the content he was working on,
forgetting that your pages needed some of the images he was responsible for.
Your content gets deployed, but with broken image links.
|
|
Solution |
Pervasent’s CMS explicitly tracks content dependencies, including images and
links, ensuring assets are in place before content is published. |
|
▲ |
|
Problem
|
You can't add links to your
new content from other website pages |
|
Cause |
Links in Interwoven are part of page content |
|
Your IT staff has created a
new TeamSite template so you can add press releases to your company's Web site.
Everything goes well, and you've produced two new press release pages that have
been approved. Now you want to add links to these new pages from the
"Product" pages and the press release summary page. Unfortunately, you're
not authorized to modify those pages, so you'll have to wait for other people to
get around to adding the links for you.
|
|
Solution |
With
Pervasent’s CMS, links are stored as their own content type, separate from
other page content. Users can add links to their content from a web page,
without having modification access to any other content on that page. |
|
▲ |
|
Problem |
You can't create or modify TeamSite workflow templates |
|
Cause |
TeamSite workflow templates are written in Perl |
|
You use the default TeamSite workflow tool to track the production
of articles for your site. You’ve hired an editor, and want to add a new
approval step to the default workflow. However, in order to make this simple
change, you have to change TeamSite’s default workflow script, which was
written in Perl. Not being a programmer, you have to call in your TeamSite
consultant to make the change.
|
|
Solution |
Using our
Workflow Template Builder, no programming skills are required to create workflow
templates. From a graphical user interface, users can select from a
palette of tasks and dependencies.
Pervasent’s
CMS also offers project management tools to track resources, such as staff
currently working on particular content. |
|
▲ |
|
Problem |
You're "locked out" from changing content |
|
Cause |
Pages must be checked out
before they can be modified |
|
Your product manager checks out the site’s product overview page to add a
new product description, but leaves the office before she finishes. You want
to add some text to a product description on the same page describing a
promotion starting tomorrow, but your product manager still has the page
checked out. You must find an Interwoven administrator to break the
lock on the page, or delay updating the page until your product manager
returns.
|
|
Solution |
Content is stored in Pervasent’s CMS as discrete objects; e.g. a "blurb," a
quote or a headline; so conflicts over
modifying content are all but eliminated. You never have to check out an
asset in order to modify it, while "optimistic locking" protects against any
potential database conflicts |
|
▲ |
|
Problem |
You have to do search and replaces on your very
large website |
|
Cause |
With TeamSite, content has to
be replicated to be reused |
|
Your company's product suite has received a glowing review in a trade
journal. You extract a killer quote from the review and send it to all
your product managers to post on their product's web pages. You ask your
marketing people to post it elsewhere on the site. A week later while
looking on your site, you realize you attributed the quote to "Internet Weekly"
instead of "Online Weekly." Now, someone will need to do a "search and
replace" on your 1000 page site.
|
|
Solution |
Because content is stored "logically" in Pervasent’s CMS, it never has to be
replicated to be reused. Change text, a headline, a link or an image in one
location, and it's changed everywhere on the site. |
|
▲ |
|
Problem |
You need an enterprise-level CMS solution, but budgets are tight |
|
Cause |
A typical Interwoven
implementation costs $250,000 |
|
Your company's web initiatives are playing an increasingly important role in
your company's success, in which you as the web content manager take particular
pride. That hasn't stopped you from losing staff that you haven't been
able to replace, while your budget is under a microscope. You know the
right CMS will allow you to do more with less, but six figure solutions are out
of the question.
|
|
Solution |
Often for
less than a TeamSite upgrade, Pervasent's CMS can provide an enterprise-level
solution tailored to your particular content. Typical implementations take
one month and cost under $50K including licensing and consulting services.
|
|
▲
|
