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

Does xhtml supported in Teamsite...

sara_team

Hi,

We are converting the DCR outputs to xml. We are lookng forward to the output to be converted as xhtml. Is it possible in Teamsite 6.1, if yes, wat are the files need to be updated.

Thanks,
Sara...

Find more posts tagged with

Comments

Adam Stoller

Hi,

We are converting the DCR outputs to xml. We are lookng forward to the output to be converted as xhtml. Is it possible in Teamsite 6.1, if yes, wat are the files need to be updated.

Thanks,
Sara...

It seems you have not taken any FormsPublisher classes, nor spent much time reading the manuals. I suggest you do at least one, if not both, of these if you intend to spend much time working with the product as a developer.

TheYann

Following what fish said, you might just have to take classes, because quite frankly the documentation is ****!

Note to interwoven: whoever is doing your doc, fire him/her ... unless it is a strategy to order very expensive courses and pay a lot of money to interwoven consultants ...

Tbag

In Interwoven's defense, while their documentation does frequently come up lacking and in some cases is just plain wrong, they do do a pretty **** good job *compared to other organizations their size with their offerings*.

We all know that technical documentation writing is perhaps the least glamorous of tech jobs (though you can make a case for manning a help desk, I suppose). Considering the turn-over and flux involved in the technology as well as the writing staff, it's a miracle they produce anything at all.

THAT SAID, I think it'd be a pretty dope idea if Interwoven established one of two things:

1) Wikidocs :: put all their documentation in a wiki-like format (could be hard with the # of pictures). Allow trusted community members to update it.

2) Pay-to-Proofread :: for every "substantive" error in Interwoven documentation found, corrected, and submitted by the devnet community, Interwoven gives 'em $10 or something (could be Amazon gift certificates or whatever).