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

Link Management - TeamXML??

Johnny

Hi Guys,

Ive been looking into how we could manage large structured online documents.
In particular im looking into link management (maintaining the relationship between pages when a page or section is moved from one place to another).

After reading up on TeamXML, im starting to think it has been designed for this purpose.

Has anyone had any similar requirements?.. I would have suspected so, as link management seems to be on top of the agenda for most that i talk to and it seems to be a common feature of CMS's. Is TeamXML the iwov solution to this?

What light can people shed on their solutions to structured online documents ( managing links - aka doc ids, repurposing sections/topics etc), and to the real world use of TeamXML?

Your help will be really appreciated.

John Cuiuli

Find more posts tagged with

Comments

Johnny

anybody?

John Cuiuli

Migrateduser

I sent this post on to some folks but no one has responded yet. I would speak to your sales person about TeamXML before giving it serious consideration for an implementation.

Regards,

lissa

Migrateduser

> I would speak to your sales person about TeamXML before giving it serious consideration for an implementation.

Does that mean it's going the way of TeamCode or whatever that thing was?

pflory

John,

TeamXML provides a sort of link management for XML documents, yes.

For client-side authoring of documents, TeamXML requires some sort of XML editor that has been integrated with it, such as ArborText Epic or XMetal.

One of the key benefits of this product is the ability to reuse XML components, or snippets in multiple documents. Components can be searched for, inserted, edited, etc.

Typically, components will be structured along lines drawn by your DTDs or XML Schemas. For example, if you have XML docs conforming to something like DocBook, you might structure your TeamXML components around Chapters, Sections, Graphics, and Paragraphs. How you break down your docs into components may appear to be a voodoo art at first.

One of the key obstacles to a TeamXML-based approach is getting your user base to understand how to work with highly structured documents, via an XML editor. Unlike MS Word, formatting and document structure are locked down tight. The editors may seem a bit alien to most people.

Let me know if you need more information.

Thanks,
Paul

Paul Flory

Johnny

Thanks for your feedback guys.

The functionality certainly seems to fit our requirements.
Though our end users wouldnt want to be concerned about xml - i wonder if templating can fill that whole (I did see some posts that they are not integrated).

We are doing as lissa suggested and will be speaking more about our requirements with interwoven.

We definately need a tool to work with highly structured documents, though a techincal interface such as an xml editor would be an obstacle.

At this stage it doesnt seem these sort of CMS features are part of the core use of teamsite.

Thanks again!

John Cuiuli