WebLion's Guide for Content Managers

Begin working on your site's content as soon as it is in Plone.

The WebLion team will migrate your site's content from the current system you're using into Plone. This will happen several weeks before your site actually goes live in Plone.

You and your content providers will need this time to make necessary content changes and additions before the site goes public.

You will use part of this time to decide, and set up, who has permission to add and edit in different sections of your site.

This is also the time to set up the organization your site's content (also known as your site's information architecture) and your site's navigation.

You will have a lot to do and learn during this time. Use it wisely!

Immediately have content owners begin reviewing their content.

Make sure the owners of your site's information are happy with their content before your site goes public.

If these same content owners should be responsible for editing their content, make sure permissions are in place and arrange for their training so that they can begin editing as soon as possible.

Check all content before your site goes public.

Now is the time to fix links, titles, images, and other lingering issues and content gotchas.

Depending on what system you were using before Plone, there may be old and problematic code hidden in your content. Have a member of your team who is HTML-savvy go through your content and clean out this code. Hint: This is a great use of part-time student help.

Keep your sites' content in synch prior to launch.

Up to the time when your site goes live in Plone, you will need to attend to content in two locations: your site in its current system and your new Plone site.

Make things easy on yourself by doing the following:

• Closely monitor all content activity on your current system. Make sure these additions and changes are put in place on your new Plone site as they occur. Saving up a stack of site changes to do just prior to launch will divert you from conducting final pre-launch checks on your new site and will add to your stress.
• Wherever possible, limit the addition of new content on your current site. Work with your stakeholders to set up newly requested site sections in Plone. They, and you, will be more satisfied with the outcome.
• Avoid postponing the date when your new site is due to go public. The longer this is delayed, the more work you will have maintaining content on two sites.
• Institute a content freeze on your current site at least one week prior to your new Plone site going public.

Remember: Content is your top priority.

It's human nature to have a keen interest in the graphical design of your new Web site. The look and feel of your site is important.

But your site's content is more important. Content is what your users most want and need. While you are working with WebLion to finalize your site's visual theme, keep your site's content on track:

• Devote adequate staff time to reviewing and making necessary changes to your content once it is in Plone. It  is easy to underestimate the time needed for this.
• Avoid postponing your site's public launch date in order to continue making visual theme changes, or "tweaks." Postponing your site's launch date can lead to a serious content management workload crunch.
• Involve WebLion in visual design planning and development from the very beginning. We can help you to avoid snags in the process as well as design "features" that will negatively impact your ability to effectively manage your site's content -- not to mention your end-users' experience.