WebGUI's Story Manager is a combination of three assets:

• Story: an individual story.

• Story Archive: a collection of many stories. Story Archive contains Story assets. Stories are listed chronologically by date and order of submittal (default).

• Story Topic: dynamically pulls in Story assets from Story Archive based on keyword association.

Story Archives house Story assets, similar to how a Wiki houses Wiki Articles. You can create a Story Archive, and add as many stories to it as you wish. By assigning each story a keyword, you can then create corresponding Story Topics. Assign a Story Topic an identical keyword as a Story, and the Story Topic will pull that Story.

For example, you could have a Story Archive that contains dozens of stories with the keywords of sports, politics, local interest and so on. Then you create a Story Topic asset, and in that asset give it a keyword of “sports”. The Story Topic asset will pull in only those stories from Story Archive that also have a keyword of “sports”. You'll see this demonstrated in this chapter.

Story Archive

Use Story Archive to build an archive of stories. Story Archive can be viewed on its own, or you can use it along with Story Topic to organize stories by keyword association.

1. Select Story Archive from the New Content menu. The “Add/Edit Story Archive” screen will open.


2. Give the Story Archive asset a title in the “Title” field.


3. The Menu Title can be left blank and WebGUI will use the title from the “Title” field as the Menu Title, or you can create your own Menu Title by entering one here.

4. In the “Description” field you can enter content related to this asset. Use the rich editor to format content entered here.

5. Set display options in the “Display” tab.

A. The first five fields are the standard Display tab fields.

B. “Stories per page” allows you to set the number of recent stories to display on the page at one time.

C. The “Story Archive” template is the template used to display this asset.

D. The “Story Template” is the template used to display an individual story in this asset.

E. “Photo width” allows you to set the maximum width, in pixels, of photos uploaded with a story. Photos uploaded with a story will be resized to this specification. If you are using a Carousel asset to display images as well, you will need to size them similarly in order for them to render properly.

F. “Edit Story Template” is the template used to display the Edit Story form, which is used when creating new stories or editing existing stories.

G. “Keyword List Template” is used to render the list of stories with matching keywords.

H. “Archive Stories After” allows you to set a length of time to pass before stories are archived. There are many units of time to select from.

I. The “Rich Editor” field allows you to select the rich editor configuration used for creating and editing Story assets.

6. Set asset permissions in the “Security” tab.


A. The first three fields are the standard Security tab fields.

B. The “Group to Post” field allows you to select the group of users allowed to post Stories.

C. The “Story Approval Workflow” is the workflow to be triggered when a Story asset is created or edited.

7. The “Metadata” tab allows you to set metadata properties for this asset, such as keywords or fields created through WebGUI's content profiling system.

8. The “RSS” tab allows you set up specific RSS properties for the Story Archive.


A. The “Items Per Feed” sets the number of stories included in the feed.

B. The “Feed Copyright” field allows you to enter optional copyright information that may pertain to content published by your organization.

C. The “Feed Title” field is the name of this feed. If this is left blank the asset will simply use the title given to the asset in the Property tab's “Title” field.

D. “Feed Description” is an area to enter an optional description of this feed. If left blank, any content entered in the asset's “Description” field will be used.

E. “Feed Image” is an area to upload an image to associate with this feed, such as a logo.

F. “Feed Image Link” is where you can enter a URL to where users will be hyperlinked if they click on the image uploaded in the “Feed Image” field. If not specified, the asset's URL will be used.

G. The “Feed Image Description” field is an optional area in which you may enter a description of the image uploaded in the “Feed Image” field. If left blank the asset's title will be used.
The “HTML Header Feed Links” field is where you can select which feed types to include in the HTML headers, which many browsers offer as options to users.

9. Click save to create the Story Archive asset.

The Story Archive contains a search field and a link to add stories.

Add a Story

Stories are added to Story Archive and organized by order of creation on the day they were created. Each story is a Story Asset, so it will have an asset toolbar, its own URL, and become an asset that can be managed through the Asset Manager.

1. Click on the “Add a Story” link in the Story Archive to open the “Add a Story” screen.

2. The “Title” field is where you enter a title for this Story asset. When managing stories through the asset manager, this is the title that you will see.

3. The “Headline” is the headline of this story as it will appear when viewing the story. This is the headline/title that users will see.

4. The “Subtitle” field is where you can enter an optional subtitle to go under the Headline.

5. The “By Line” field is where you enter the name(s) of the author(s) of this story.

6. “Location” is the location of this story's events.

7. “Keywords” is where you enter metadata keywords to associate with this story. Multiple keywords can be entered, and should be separated by a comma. (ex: lorem, ipsum, lorem ipsum) Keywords are used to populate Story Topic assets. If you give stories a keyword(s), and then create a Story Topic asset with an identical keyword, the Story Topic asset will pull headlines in from the matching story assets for display in that asset. See the Story Topic section for an example.

8. “Story Highlights” is where you can enter a brief synopsis of this story.

9. The “Story” field is the rich editor in which the story text is entered.

10. Below the rich editor is the “Photo” field. This is where you can attach a photo to upload with this story. You may upload multiple photos.

11. Text entered in the “Photo Caption” field will display below the photo.

12. The “Photo By Line” is where you enter credit(s) for this photo.

13. “Photo Alternate Text” is where you enter alt text for this photo.

14. “Photo Alternate Title” is where you enter the alternative title for this photo.

15. If you enter a URL into the “Photo URL” field, users may click on the photo to be linked to this location.

16. Click save to create the story. You will be shown a confirmation screen indicating that the content has been received. Use the back to site link or the site navigation to view the Story Archive asset.

Stories will be listed in the order they are created, from newest to oldest, and by date.

Each story will have a delete icon and an edit icon. Also, a keyword cloud will be generated by any keywords you entered in the stories. Clicking on a keyword in the cloud will display all stories with matching keywords. Below, the keyword “local interest” was selected.

Near the bottom of the Story Archive asset are links for syndicating the content of the asset. If you click on one, you will be directed to the screen on which you can subscribe to the feed.

Stories are viewed by clicking on a story title. Site users can use the crumbtrail navigation in the upper left hand corner to return to the Story Archive. Keywords are listed at the bottom. Clicking on a keyword will display all stories with matching keywords.

Note: If you view Story Archive in the Asset Manager, each date is a separate folder, with the individual stories for that date within it.

Story Topic

Story Topic is used to pull in headlines from Story Archive based on keyword association. This allows you to have a main story repository (Story Archive) and display headlines anywhere else on the site.

1. Select Story Topic from the New Content menu. The “Add/Edit Story Topic” screen will open.

2. Give the Story Topic a title in the “Title” field.

3. The “Menu Title” is the title of this asset as it appears in the site navigation. You can enter one or leave it blank and WebGUI will use the title.

4. The “URL” is the URL of this asset. You can leave it blank and WebGUI will create one for you, or you can enter a URL of your own.

5. The “Description” field is where you can enter content related to stories displayed in this asset.

6. Set display options in the “Display” tab.

7. 1. The first five fields are the standard display options.

   2. “Stories Per Topic” sets the number of headlines displayed if the Story Topic asset is viewed directly. It also limits the number of stories sent through feeds.

   3. “Stories Per Page” is the number of stories displayed in Story Topic if the asset is placed on a Page Layout.

   4. The “Main Template” is the template used to display the Story Topic asset.

   5. “Story Template” is the template used to display the individual Story assets pulled in from Story Archive. This template can be different from the Story Template used to display stories through Story Archive if you wish.



 

8. Set permissions in the “Security” tab. These are the standard Security fields.

9. The “Metadata” tab contains all the standard metadata fields. In order to pull in headlines from Story Archive, you need to enter a keyword into the “Keywords” field. This keyword association is what populates Story Topic. In this example, “local interest” was entered, so all Stories in Story Archive with the matching keyword of “local interest” will be pulled in to this Story Topic asset.

10. The “RSS” tab allows you set up specific RSS properties for the Story Topic.

1. 1. The “Items Per Feed” sets the number of stories included in the feed.

   2. The “Feed Copyright” field allows you to enter optional copyright information that may pertain to content published by your organization.

   3. The “Feed Title” field is the name of this feed. If this is left blank the asset will simply use the title given to the asset in the Property tab's “Title” field.

   4. “Feed Description” is an area to enter an optional description of this feed. If left blank, any content entered in the asset's “Description” field will be used.

   5. “Feed Image” is an area to upload an image to associate with this feed, such as a logo.

   6. “Feed Image Link” is where you can enter a URL to where users will be hyperlinked if they click on the image uploaded in the “Feed Image” field. If not specified, the asset's URL will be used.

   7. The “Feed Image Description” field is an optional area in which you may enter a description of the image uploaded in the “Feed Image” field. If left blank the asset's title will be used.

   8. The “HTML Header Feed Links” field is where you can select which feed types to include in the HTML headers, which many browsers offer as options to users.

11. Click save to create the Story Topic asset.

Story Topic will pull in headlines from Story Archive that have matching keywords. In this way, a Story Topic asset can be placed anywhere on a site, and stories can still be managed through Story Archive. Each story will have a delete and Edit button, and the headline can be clicked on to view the full story. Like Story Archive, the feeds for this asset are located in the lower left corner and can be clicked on to access the screen on which to subscribe to a feed.