How do you "document" SitePublisher for your User community?

We are struggling with documenting the process to build pages, add components, update DCRs... etc

What do you all do to prevent phone calls and allow the mere mortal users to use SitePublisher correctly?

Find more posts tagged with

Comments

nipper

We are struggling with documenting the process to build pages, add components, update DCRs... etc

What do you all do to prevent phone calls and allow the mere mortal users to use SitePublisher correctly?

Do you ?

We make templates and then let the users at it.

I have pregenerated pages with stub DCRs, can be done in certain circumstances.

We typically do not encourage users to add/change components, though as they get familiar with the system, that may happen.

Rick Poulin

We have a team dedicated to doing in-person content author training, and they're working on building an e-learning program. Users don't read word docs.

We also have a service desk. Because some mere mortals can't ever remember how to make a table in Word, let alone doing it in TinyMCE.

@nipper: I know the platform kinda lends itself to saying components are just a different kind of content, but we always have and always will treat them as code. I.e. non-developers don't get to touch them, and they don't ever change in between code releases.

moulikk

We create page templates and teach users how to use them. They know how to add components but for the most part its only basic components like textareas and banners. Dynamic components (e.g. my-account) are typically page specific and those pages are created prior to launch, so the users typically don't ever have a need to add them, simply play with the textboxes within.

This works for the few SP driven sites we have now but as we bring in more business lines, we are trying to find a good way to document the site-specific css styles so the users and support team can efficiently work it out.

I'll be curious what others are doing.