Laserfiche Online Training from General Code

yieldingrabbleInternet and Web Development

Dec 7, 2013 (3 years and 4 months ago)

79 views







Website Management

for
GeneralCode.com





















Revised
2011
-
05
-
25

by Eric Scoles (e
ric.
scoles
@brandcool.com)

Senior Internet Marketing Developer

Brand | Cool Marketing




Table of Contents

Website Management for GeneralCode.com

................................
................................
....

1

Introduction

................................
................................
................................
................................
................................
........

5

Managing GeneralCode.com

................................
................................
................................
................................
.........

6

Overview of Your Website

................................
................................
................................
................................
.................

6

Review of Your Site's Organization

................................
................................
................................
................................
......

6

Logging In

................................
................................
................................
................................
................................
........................

7

What You Can Do Before and After Login

................................
................................
................................
..........................

7

Types of Content

................................
................................
................................
................................
................................
...........

8

Content Editing Workflow

................................
................................
................................
................................
........................

8

Roles, Capabilities and Responsibilities

................................
................................
................................
.............................

9

Getting Access to Webform Submissions

................................
................................
................................
.........................

11

Changing Content

................................
................................
................................
................................
................................

12

Finding Pages

................................
................................
................................
................................
................................
...............

12

Editing Pages

................................
................................
................................
................................
................................
................

12

Creating New Pages

................................
................................
................................
................................
................................
...

23

Creating and Formatting Webforms

................................
................................
................................
................................
..

25

Converting Pages from One Type to Another

................................
................................
................................
................

31

Removing Pages

................................
................................
................................
................................
................................
..........

32

Changing Site Appearance

................................
................................
................................
................................
..............

33

What You Can, Shouldn’t, and Can’t Change through the CMS

................................
................................
...............

33

Managing Blocks

................................
................................
................................
................................
................................
.........

35

Changing the Navigation

................................
................................
................................
................................
.........................

38

Adding a URL Redirect

................................
................................
................................
................................
......................

40

From the URL Redirect page

................................
................................
................................
................................
.................

40

From the

node edit form

................................
................................
................................
................................
.........................

40

Editing and Creating Users

................................
................................
................................
................................
.............

40

Edit A User

................................
................................
................................
................................
................................
.....................

40

Create A New User

................................
................................
................................
................................
................................
.....

41

Reference

................................
................................
................................
................................
................................
..........

42

Working
With the WYSIWYG Editor

................................
................................
................................
..........................

42

Character Formatting versus Block Formatting

................................
................................
................................
...........

42

Paragraphs versus line
-
breaks; making a new paragraph
................................
................................
.......................

42

Making a new line
-
break

................................
................................
................................
................................
.........................

43

Bold, Italic

................................
................................
................................
................................
................................
......................

43

Lists
................................
................................
................................
................................
................................
................................
...

43

Font and text color

................................
................................
................................
................................
................................
.....

43

Other Text Formatting

................................
................................
................................
................................
.............................

43

Applying styles

................................
................................
................................
................................
................................
............

44

Uploading Via an FTP Client

................................
................................
................................
................................
..........

44

FTP Configuration

................................
................................
................................
................................
................................
......

45

Information required to configure an FTP client will be provided separately. Uploading Images and
Files

................................
................................
................................
................................
................................
................................
...

45


Turner Engineering
-

Website Management Training | July 29, 2008 | page
4

Website Backup and Restore

................................
................................
................................
................................
.........

45

Website Status and Available Updates

................................
................................
................................
......................

45

Updating the Website Software

................................
................................
................................
................................
....

46

Using FTP + Web

................................
................................
................................
................................
................................
.........

46

Using Drush

................................
................................
................................
................................
................................
...................

47

Appendix A: Screenshots of Important Edit / Create Node Settings Panes

................................
..........

49

Menu Settings

................................
................................
................................
................................
................................
........

49

URL Path Settings

................................
................................
................................
................................
...............................

50

Normal:

................................
................................
................................
................................
................................
...........................

50

With automatic path alias:
................................
................................
................................
................................
......................

50

Revision Information

................................
................................
................................
................................
.........................

51

Publishing Options

................................
................................
................................
................................
..............................

52

Appendix B: Online Resources

................................
................................
................................
................................
.

53




General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
5

Intr
oduction

This document provides supporting material for managing the
General Code

website, with special attention to
how to edit and create documents, and is meant as a companion to one or more real
-
time training

sessions.

The sessions will follow this general outline:

1.

Part 1: Creating and managing content.



Creating pages



Assigning pages to the navigation



Editing pages



Converting pages from one Content Type to another



Miscellaneous management tasks

2.

Part 2: Advan
ced topics



Creating webforms



Managing and creating blocks

3.

Part 3: Presenting content



Editing Views


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
6

Managing GeneralCode.com

Overview of Your Website

This section will provide an overview of your website, and will cover:



The website as it appears to ordina
ry visitors.



Differences between the visitor's view and a site administrator's.



Key content management concepts, including: Content types, blocks, user roles, and content
management workflow.


Review of Your Site's Organization

Overview of how your site is

organized and the principle features of the site.



Home page



Parts of a page:

o

Header

o

Body

o

Sidebar(s)

o

Footer



Navigation

o

Primary, which may be displayed as a drop
-
down menu near the top of the page and a static
menu in the footer

o

Secondary, generally used
to provide additional navigation in the site’s footer

o

Utility

o

other



Kinds of page

o

Nodes



Page:

the main type of content on your site. Used for most pages.



Events:

Items to be shown on the Events page. Includes a date for the event.



News Release:

Items to
be shown on the News Releases page.



Positions:

Job postings for your company
, which will be displayed on the Open
Positions page
.



Bare Page:

Used to create pages with no navigation, sidebar or footer (for example,
for an advertising landing page, or a po
pup page for a flash movie).


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
7



Page with Complex Layout:

Used on pages requiring layout that can’t be
accommodated by the normal page template (“Composite Layout”). Currently, only
the Home page is of this type.



Simple Node:

Used to create items that can b
e included in other pages (such as
Composite Layout pages), usually as a block.



Webform:

Used to create form pages, such as the Request Quote or Contact pages.



Image:

Used to add images for use in QuickTab displays, and elsewhere.



Other types not used on

this site: Story and suitcase. The Story type is a default
system type; it should be left unused. The Suitcase type is a means to import and
export fields from one site to another, and can be deleted when development is
finished.

o

Views: Pages that displ
ay lists of nodes



News Releases



Open Positions



Events

o

System Pages



Site map, which is created by the Sitemap module based on the content of the
Primary and Secondary navigation.



Administrative pages


Logging In

To login during the development process, bro
wse to:



http://
50.19.103.197/
user

Log in with the appropriate user name and password.

After the site has launched, you will login at http://generalcode.com/user.

What You Can Do Before and After Login

Before login, you will not be able to manage any of t
he "content
-
managed" features of the website. Most
pages will show "Primary" navigation (and “Secondary” navigation if your site includes it).

After login, you will notice several differences:



New navigation available as a pull
-
down menu at the top of th
e page. This is the
Administration
Menu
.



A row of buttons at the top of the middle column on many pages that will allow you to manage that
page.



Edit
,
Configure

or
Delete

buttons may appear on some pages that include the content of other nodes.



Edit [
]

and Configure [
] icons, or

[Edit
]
,
[Export
]

and
[
Clone
]


links will be displayed when you
hover over some areas of a page.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
8


Types of Content

Your site has three different kinds of page that are visible to the public:

1.

Node
s, as web pages
:

The basic bui
lding blocks of the site. These are the most straightforward web
pages. They show just one piece of content (a "node"), but can also include extra fields that affect
how the page is displayed. Your site may include several custom
content types

that include

additional
fields, or have special characteristics. (For example, your site includes
Pages
,
Webforms

and
Simple
Nodes
, as well as several other types
, all of which are listed here:
http://
50.19.103.197/
admin/content/types
). Examples:
Codification Services

and eCodes

[a Page],
and
Contact Us

[a Webform].

a.

Note: Pages like the home page of your site are actually a hybrid of node pages, Views, and
system
-
generated pages in that they are a node page that can include blocks, other nodes,
and views. On your site
, pages like this are created using the Composite Layout Page content
type.

2.

Views
:

These are pages that display lists of other pages. (They're called "Views" because they provide
a
view

into the system’s database.) Views are ways of selecting nodes that ha
ve something in
common
--

for example, that they're all about a particular subject, or are all the same content type.
Basically, they are much like search result pages, without having to enter the search terms. Views can
also have different
displays

that c
an be shown in other places (for example, as a block of text in one
of the sidebars). For example, the same View might have the following displays:

a.

As a page: http://
50.19.103.197/
news
-
releases might show the published news releases.

b.

As a block in the si
debar: http://
50.19.103.197/n
ews might include a View block in the
sidebar that displays recent News Releases.

3.

System
-
generated pages
:

This category includes search results, error pages (404, 403, etc.), the site
map, and system
-
management pages.

In addi
tion, your site may have other types of content that are never displayed on their own


rather, they are
always displayed as part of another page. For your site, those include:

1.

Blocks
: are chunks of content that are displayed in specific parts of a page.
Blocks may be created by
a site administrator, or generated by a website module. On your site, blocks are displayed primarily in
the right sidebar and in the page header.

Content Editing Workflow

This is the basic workflow for editing the content of exist
ing pages:

1.

Login

to the website



http://
50.19.103.197/
/user

2.

Browse

to the page you want to change.

3.

Edit

the page
.

4.

Optionally
Review

the page
--

send a note to another person, or let it sit for a time and then review it
yourself.

5.

Revise

the page if neces
sary.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
9

For most blocks, the workflow to edit content is similar:

1.

Browse to a page displaying the block you want to change.

2.

Click the appropriate button, icon or link to change the block:

a.

Use the
Configure

button or Configure [
] icon to edit the block co
nfiguration, or edit the
content of a normal text block.

b.

Use the
Edit

button or Edit [
] icon to edit the content of a block that’s based on a Simple
Node.

c.

To change the content of blocks displaying a View (for example, “Upcoming Events”), click on
the
[E
dit
]
,
[Export
]

or
[
Clone
]

link that is displayed when you hover over the block.

3.

Make the desired changes, and click the
Save

button.


Roles, Capabilities and Responsibilities

To enforce workflow and enhance security, the website relies on user
roles
. Eac
h user is assigned to one or
more a roles; each role is assigned certain permissions. Permissions are
positive

(that is, they
allow

actions
rather than preventing them) and
cumulative

(you can assign multiple roles to one user to add to their
capabilities)
.

By default, the content management system is set up with three basic roles: Administrator, Authenticated
User, and Anonymous User. For
General Code
, the website has been configured with additional user roles,
as
shown below.

The permissions assigned to your user role determine what you can do, and what items you can see on a page.
The Anonymous User has a role just like any other user.

In order of declining privilege, here are the roles and their capabilities
.
Note that this table represents
individual users as they correspond to roles only at the time of this training


role assignments may be
changed to suit workflow needs.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
10

Who

User Role

Capabilities

Root Administrator
("
gcode.one
") (sometimes a.k.a.
'user 1')



N/A


(NOTE:
Though
User 1
doesn’t
need a role to get privileges


it
already has all privileges
available on the system


it
is set
to
the
‘administrator’ role to
ensure consistency of
presentation for
some blocks.)



The only user who can
perform system
updates.



Has access to all
administrative features.



Can create or edit
without anti
-
spam
verification.

(User 1 will always have all
rights, and so should be used
sparingly for ordinary tasks. User
1’s lo
gin information should not
be distributed to more than 2 or
3 people.)


Administrator ("
gcode.admin
")



admin




Access to all
administrative features.



Can create or edit
without anti
-
spam
verification.

You

should try to perform most
administrative tasks using an ID
in this or the site_editor role.

TBD

("
tbd
")


TBD

("
tbd
")



site_editor




Can create or edit
without anti
-
spam
verification.



Access to many
administrative features.



Cannot create new
users or assign users to
roles

















All active website users

authenticated user

[standard role]



No privileges beyond
those of the normal
anonymous user.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
11

Who

User Role

Capabilities

anonymous
-
simulator

untracked



Used to block reporting
to Google Analytics
prior to site launch and
on the Development
website
, and l
ater for
system testing
.



No privileges in addition
to those of a normal
authenticated
user.

All website visitors

anonymous user



Able to see all
"published" content.



Able to submit public
-
facing forms, search the
website.

*Note: The "Authenticated Us
er" role is configured to have no privileges beyond those of a normal
anonymous user.

Getting Access to Webform Submissions

When visitors submit contact forms (or other Webforms) on your site, two things happen:

1.

A copy of the message is stored in the con
tent management database.

2.

A copy of the message is emailed directly to the addresses specified in the form's configuration.
(Typically this means that a copy of the message will go to at least one person in the company and to
the user who submitted it.)

W
hile in theory, you should be getting every message that users send, sometimes you will need to look them
up. Here's how:

1.

Login to the website.

2.

Browse to a Webform page, such as the Contact Us page.

3.

Click
Results
.

If you can’t remember where the webform
page is:

1.

Using the Administration menu, browse to Content Management >> Webforms.

2.

Find the webform you’re looking for on the list of webforms.

3.

Click the Results link for that form.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
12

Changing Content

Finding Pages

Through Navigation

Most pages on your we
bsite are either included in the navigation, or are accessible through pages on the site.
Some types of page are not visible in the site’s navigation, but can be accessed through pages that are in the
navigation. (Events, News Releases, and Positions would

all fit this description.) You will be able to edit such
pages using links or buttons adjacent to the item on the pages listing Events, News Releases, etc.

Through the List Content Page

Some types of content (such as Simple Node or Bare Page pages) are di
fficult to find because they aren’t
included in the site navigation. You can find such pages using the List Content page.

1.

Use the Administration Menu to browse to Content Management >> Content.

2.

Use the filters to filter the list by status, content type or

category. You can combine filters, but note
that Category is only relevant for Position pages.

Once you have filtered the list down to the status or category you want, you can select multiple nodes to
update using the Update Options selector.

You can als
o use the Scheduled tab on the List Content page to see any nodes that have been scheduled for
future publication.

Advanced Content Management Page

Your site also includes an Advanced Content Management page (Content Management >> Advanced Content
Managem
ent), which allows you to perform additional actions on selected nodes. For many purposes, it’s
functionally equivalent to the List Content page, though it lacks the ability to display scheduled content and
may be slower.

Editing Pages

This section will c
over editing pages, including:



Editing an existing page on the website.



Editing an item that's displayed on the home page (or another Composite Layout page).



Changing the text that appears at the top and bottom of a "View Page."

Edit an Existing Page

To e
dit an existing page:

1.

Login to the site and find the page that you want to edit.

2.

Click on the
Edit

button (at the top of the middle column) to load the Edit form.

3.

Make changes as required to the fields on the edit form. (Also see
Working With the WYSIWYG
Editor
, below.)

a.

If the title of the page will include markup (that is, italics or boldface), or must include an ®
or ©, you should enter it in the Displayed Title field. Otherwise, you can feel free to leave

General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
13

that field blank. (Note: Regular fields can inc
lude ® and ©, but may not format them in an
aesthetically acceptable way. We recommend applying superscript to ensure that the mark
doesn’t overpower the text it’s marking.)

b.

Add text to the body field, either by typing it in directly or copying it from ano
ther source.
(See ‘Tips for Using the WYSIWYG Editor’, below.)

4.

Click the
Submit

button to save changes to the node.

Note:



Some blocks in the sidebars
--

including the navigation
--

may not display as you expect while you are
editing a page. That's becaus
e the system determines where to display some blocks based on the
URL, and the URL for the Edit form is different from the URL for the page. (See
Controlling Display of
Blocks
.)



In Preview mode, the Side Content shown in the right sidebar will not accurate
ly reflect changes you
have just made to the Side Content field on the form. You will have to Submit the form to see any
changes you make to Side Content. Remember that any changes you make will be held in
moderation, so there isn't a risk of exposing the
pages on the web prematurely.

Notes about the WYSIWYG Editor

Your website incorporates a WYSIWYG [“What You See Is What You Get”] editor called CKEditor that will allow
you to see what the text of a page looks like before saving. The editor uses many of t
he same editing
conventions as Microsoft Word (for example,
Ctrl

x

to cut text,
Ctrl

v

to paste text, etc.). The editor will
enable you to format text using basic markup like bold and italics, set hyperlinks, add and format images,
select from predefined s
tyles, etc.

To ensure that pages continue to be consistent with the site’s overall design, you will not have the opportunity
to change the size, color or font of your text. However, you can apply pre
-
defined styles from a drop
-
down list.
Most styles on th
e list are presented as a preview of their appearance in the document.

Because it’s sometimes necessary to make changes that can’t easily be accomplished in WYSIWYG mode, you
can also edit the HTML source code of the text.

Tips for Using the WYSIWYG Edito
r

Copy & Paste

The WYSIWYG editor can preserve the basic formatting of text that you paste in from Microsoft Word.
However, with some versions of Word or Microsoft Windows, you must use the ‘Paste from Word’ button
[
] to ensure that the editor is able to
strip out extra styles and formatting that will alter the appearance of
the text. If the text looks unusual (for example, is in the wrong font, or is a little larger than expected, etc.),
you should un
-
do the paste operation and use the Paste from Word dia
log instead.

Do not paste directly into the editor from web browsers, Microsoft Outlook, or WordPad. They also include
excess style and formatting information, but in a form that the editor isn’t able to recognize. Instead, use the
‘Paste as Plain Text’ [
] button. Use ‘Paste as Plain Text’ any time the paste operation produces unexpected
results.

Symbols and Special Characters

Special characters or symbols can be inserted using the Special Characters [
] button on the editor toolbar.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
14

Some special characte
rs (especially
® and ©) aren’t formatted in a very attractive way by default. We
recommend superscripting [
] those symbols.

In most cases, you will also be able to paste special characters into the editor from Microsoft Word (they’re
converted into “HTML

entities”); however, if you see evidence of a “broken” character where you think there
should be a symbol, it’s probably that the browser is trying to display a Windows or Macintosh character as
though it were ANSI. Replace the character with one from the

Special Characters dialog.

If you need to use a special character in a non
-
WYSIWYG field (like Title), and you don’t know how to get that
character on your keyboard, you can copy it in the WYSIWYG field, and paste it into the non
-
WYSIWYG field.


Working
with Tables

Unfortunately, web
-
based WYSIWYG editors do not do a remarkably good job at working with tables. This
section will outline some tips for producing acceptable tables or working with existing tables.

Inserting a new table

To insert a new table,
click on the Table [
] icon on the editor toolbar.

The table dialog allows you to set the number of rows and columns. You should figure out before inserting a
new table how many rows and columns you need.

You can also paste a table from Microsoft Word. I
f you do, you should take care to set (or clear) all table
properties to appropriate values after pasting the table (see below).


Editing an existing table

To edit the characteristics of an existing table, you should right
-
click within the table.

Table ed
iting follows many of the same conventions as Microsoft Word, though is not as powerful. You can
merge cells, and insert or delete rows or cells.

To add a new row to the end of a table, as with Word, you would put your cursor in the last cell and press th
e
tab key.

Appropriate settings for table properties

To adjust the display of an entire table, right
-
click within the table and select Table Properties.

To ensure that tables display consistently, we recommend the following settings.

Table properties (d
efault tab):

Property

Value

Comments

Rows

fill in the number you need

Don’t forget to account for a
header row.

Columns

fill in the number you need


Width

Leave empty.

Normally it’s best to leave this
empty to allow the table to find its
own width in
the column.

Width scale

Usually percent, if specified

Unless tables are presented

General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
15

together on the same page, this is
best left blank, so the browser can
set it based on the amount of copy
in each column. If you want to
enforce a specific proportion, use
%. However, if you want to force
several tables to have matching
column widths, you must use
pixels.

Headers

None

Headers will take on different
formatting from the rest of the
table. For tables on this site,
simply format the text in the
header rows as
bold to indicate a
header.

Cell Padding, Cell Spacing, Border
Width

Leave empty

These should always be set to left
empty. These properties are set in
the site’s stylesheet, and setting
them here will cause them to be
over
-
ridden.

Alignment

Not set

Sett
ing alignment on the table can
cause issues with word wrap in the
narrow columns of a website.

Caption

Leave blank

Not used in the copy on your site.

Summary

Leave blank

Not used in the copy on your site.


Advanced tab:


Property

Value

Comments

ID, S
tylesheet Classes

leave blank

Not useful unless a table will have
special formatting defined in the
site’s stylesheet.

却S汥

汥慶e⁢污lk

佮汹⁵Vefu氠睩瑨nowleT来f⁃卓
捯c楮朮

䱡n杵慧攠䑩牥捴楯n

汥慶e⁵n
-
VeW

UVeT⁴o⁳ 琠T楲i捴楯nf⁲e慤in朠
汩湥⸠䑥f
慵汴l楳 f琠瑯⁲楧桴⸠


Editing Content on a Page with composite layout

Some pages on your website use composite layout to position content in ways that aren’t easy to do within a
normal page design. You can identify pages that have composite layout enab
led by the fact that the editing
buttons include buttons labeled
Blocks
,
Fields
,
Nodes

and
Zones
.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
16

To edit content on a composite layout page, such as the home page, click on the
Edit

button or link (if it is a
node) or the edit icon (if it is a block) adj
acent to the content you wish to edit. Click
Save

when you are
finished, and you will be returned to the page you started from.

Adding An Image To A Page

The simplest way to add images to the website is to upload them as needed using the Image Browser:

1.

W
hile you are editing a page, click the
Image Properties

icon [
] on the editor toolbar.

2.

In the Image Properties dialog, click the
Browse

Server

button. That will cause the Image Browser
window to display.

3.

In the left pane of the Image Browser window, click

on the folder to which you want to upload images
--

for example, "photos" for photos. You may need to expand the folder tree to find the right sub
-
folder.

4.

Click the
Browse

button, and select the image you would like to upload.

5.

Click the
Upload

File

butt
on.

6.

When the file has finished uploading, it will display in the bottom pane of the window.

7.

Click on the image to select it.

8.

The Image Browser window will go away and you will be back in the Image Properties dialog. We
recommend the following settings:

a.

F
ill in Alternative Text, to ensure that visually disabled visitors and search spiders can tell
what the image represents.

b.

If you plan to link the image, set the Border value to "0", to insure that the image won't have
a border.

c.

Leave the alignment and spa
cing attributes as they are.

9.

Click
OK

when you have finished making changes to settings.

10.

You should now see the new image in the editor box.

To align the image to the right or left and wrap text around it:

11.

Click on the image to select it.

12.

Click the "Styl
es" drop
-
down in the toolbar at the top of the editor box, and select "Image L Wrap" to
align to the left or "Image R Wrap" to align to the right. (Note that you should avoid aligning to the
left when the picture will be adjacent to a bullet list.)

To uplo
ad one or more files
, simply follow steps 1
-
6, repeating steps 3
-
6 as many times as necessary, and
then close the Image Browser window and cancel the Image Properties dialog.

Note:

While your website should theoretically allow uploads of up to 5MB, it's
often impossible to upload files larger
than a few megabytes via web forms, due to the time required. For larger files (such as large PDFs or Flash
movies), you may need to use FTP. FTP configuration information and credentials will be provided under
separ
ate cover.



General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
17

Creating links

Links to Web Pages

To create a new link:

1.

Highlight the text that you want to be linked.

2.

Click the Link button on the Edit toolbar.

3.

Fill in the URL field:

a.

You can copy and paste full URLs into the URL field
--

the editor will
remove the "http://"
part automatically.

b.

Links to pages within the site should
begin with a leading slash

--

for example,
"/services/disciplines" would be what you would enter to add a link to the Disciplines page.

4.

The Protocol field will normally be set
automatically if you have entered the URL field first. If not,
select the appropriate protocol:

a.

For links to pages within the site, select "Other"

b.

For links to pages on other sites, select "http"

5.

If the link is to another site, click the "Target" tab, and

select "New Window (_blank)" from the Target
select box. (Most links on
GeneralCode.com

will be to other pages on the website. Those links should
open up in the same browser window as the current page. Lin
ks to a different site or to a PDF
document should open in a new window, to ensure that visitors don't lose track of the
GeneralCode.com

website.)

Email Links

GeneralCode.com

uses an email obfuscation filter to prevent appropriation of email addresses by spambots.

To ensure that the email filter works properly:



Do not apply any formatting to parts of the email link, such as bold or italics. If you need to
format
the email link as bold or italic, make sure that you have selected an area greater than the linked text.
(For example, it’s OK to apply a block style to the paragraph the email link is in.)



Do not supply any additional attributes (such as 'subject'
or 'cc').


Links to Files (PDF, DOC, PPT, etc.)

Linking to a file combines techniques used in creating links and adding images. You will start as though you are
creating a link to another web page, then upload or browse to the file as though you are adding

an image.

1.

Highlight the text that you want to be linked.

2.

Click the Link button on the Edit toolbar.

3.

In the Image Properties dialog, click the
Browse

Server

button. That will cause the File Browser
window to display. (This is essentially the same as the
Image Browser window, with a few words
changed.)


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
18

4.

In the left pane of the File Browser window, click on the folder you want to upload your document to
--

for example, "documents" for PDFs or other documents. You may need to expand the folder tree to
find th
e right sub
-
folder.

5.

Select or upload the document.

a.

To upload a document:

i.

Click the
Browse

button, and select the document you would like to upload.

ii.

Click the
Upload

File

button.

iii.

When the file has finished uploading, a link to it will display in the bot
tom pane of
the window, where the image would display if you were uploading an image. Click
on the link to select it.

b.

To select a document:

i.

Scroll the file list in the right pane until you find the document you want to link to,
and click to select it.

ii.

A l
ink to the file will display in the bottom pane of the window, where the image
would display if you were uploading an image. Click on the link to select it.

6.

Once you’re selected a document, the File Browser window will go away and you will be back in the
L
ink Properties dialog.

7.

When linking to files, we recommend the following settings: on the Target tab, select ‘New Window
(_blank)’; on the Advanced tab, fill in the Advisory Title field with the title of the document you are
linking to (if the document is

very large [a megabyte or more], we recommend putting the file size in
parentheses after the title).

8.

Click
OK

when you have finished making changes to settings.


Adding a Movie to a Page

Your site includes a filter that simplifies embedding videos into
web pages. The video must be hosted on a
supported video sharing site (such as YouTube, Google Video or Vimeo


see below for a list of supported
sites).

To add a movie to a page:

1.

Browse to the video
-
sharing site where the video that you want to share is h
osted. (The video filter
supports YouTube, Vimeo and a number of other commonly
-
used sites


see below.)

2.

Find the video.

3.

Copy the URL.

4.

Browse to
GeneralCode.com

and create a new page, or edit an existing o
ne.

5.

In the Body field, put your cursor at the place where you want to insert the video. (It should
preferably be in a new paragraph by itself.)

6.

Type in a simple code, and add the URL of your video, in the format “[video:
url of video
]”. The final
result mig
ht look something like this:

[video:http://www.youtube.com/watch?v=iKaVp9wLeIk
]


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
19

7.

Save

the page.

Video Embedding Options

The video embedding filter allows you to add options to the video embed code.

For example, the following would embed a video, make the

display 300 pixels wide and aligned to the right:

[video:http://www.youtube.com/watch?v=iKaVp9wLeIk align:right
width:300]

Option

Arguments

width

width in pixels

height

height in pixels

align

right

left

the default value is no alignment, which will usu
ally
cause the video to align to the left.

autoplay

1

0

‘0’ [false] is the default value.


Supported Video Sharing Sites

As of this writing, the Video Filter supports videos from the following websites:



YouTube



Google Video



Flickr Video



Flickr Slideshows



Vimeo



Picasa



Blip.tv



Capped.tv



College Humor



DailyMotion



Eyespot



Gametrailers



Gamevideos



Metacafe


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
20



Myspace



Revver



Slideshare



Tangle


Un
-
Doing (“Revert”) Changes to a Page

By default, the website will save revisions to pages, so you can roll back some erron
eous changes.

What Can Be Reverted

The Revisions feature doesn’t keep track of all changes. Here’s a quick summary of what is and is not covered
by the revisions feature.

At a high level, things that are inherently part of a node (like the body field) or

which are specifically designed
to be revertible (add
-
on fields like Displayed Title) can be reverted. Aspects of a node that are dependent on
other parts of the system usually can’t be reverted. (For example, being able to revert the URL path or menu
ent
ry would require potentially changing the URL path or menu entry of other pages.) In addition, simple
configuration options (published/not
-
published, input type of a field, comments/no
-
comments, etc.) can’t be
reverted.



Revertible

Not Revertible

Body T
ext

X


Title

X


Displayed Title

X


Side Content

X


Navigation


X

Status (published, promote to
front page, etc.)


X

Meta tags


X

Changes to image formatting
within a field (border, size, alt text,
etc.)

X


Replaced image or document files


X

Attac
hments


X


Viewing Previous Revisions

To view revisions for an existing page:

1.

While logged
-
in as an Admin, Site Editor or Site Maintainer, browse to a node
-
based page.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
21

2.

Click on the
Revisions

button.

3.

You will see revisions listed by date and time, with t
he most recent listed first. The page that is
currently being displayed to visitors is labeled “current.”

4.

Click on a revision. You should see a box identifying the page as a revision.

Comparing Revisions

To see the differences between two revisions:

1.

Whil
e on the Revisions screen for a page, select two revisions using the radio buttons in the middle
columns.

2.

Click the
Show

Diff

button.

3.

The content of both pages will be shown, one in each of two columns, with the differences
highlighted in red. (The text is

shown as HTML code.)

Reverting to Earlier Revisions

To revert to an earlier revision of a page:

1.

Browse to the page you want to revert.

2.

Click the
Revisions

button.

3.

Click the “revert” link corresponding to the version you wish to restore.

The version you

just replaced will be saved as a new revision, so you can return to it if necessary.


Editing a Webform

Webforms are in part like any other node. However, they have a form attached that allows them to store
visitor
-
submitted information in the site’s dat
abase and send email notifications when visitors submit the
form.

To edit
the content of
a Webform

node
:

1.

While logged in, browse to a webform page (such as Contact Us).

2.

Click Edit.

To edit the Webform components of a form, you would click the
Webform

butt
on. That will give you access to
the webform configuration screens.

To change the email addresses to which forms are sent:

1.

Click the
Webform

button.

2.

Click
E
-
mails
.

3.

All emails that the form sends will be listed. Click the Edit link corresponding to the emai
l you want to
change.

4.

If the form does not conditionally route email based on the value of a form field (see below), you can
edit the ‘Custom’ field to include one or more email addresses. (Multiple email addresses must be
separated by commas.)


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
22

To change
form settings:

Form settings include:

Confirmation message displayed when visitors submit the form

Fields for PHP code that facilitates additional processing or validation

To change the form settings:

1.

Click the
Webform

button.

2.

Click
Form

settings
.

3.

Chang
e settings as desired.

4.

Click Save.

Note: If you make changes to the Additional Validation or Additional Processing fields, you should copy the
original code to a text file for safe keeping.

To change the form fields:

1.

Click the
Webform

button.

2.

Click
Form

components
.

3.

Edit the form components as desired.

NOTE: You should not change the length or type of a field after it has started to receive data, or you may lose
data previously submitted.

Changing the Header or Footer Text on a View

Views have many comple
x options. This section will explain only how to change the View Header and View
Footer text of a View page or block.

The simplest way to edit a View is to find a place that a view is displayed (such as on a View page or in a View
block), and edit it from

there.

1.

While logged
-
in to the site, browse to a View page, such as the News Releases page, or find a View
block, such as the News Releases block.

2.

With your mouse, hover over the body of the page or block until you see an Edit link displayed above
the ma
in page heading (normally at the top of the middle column). Click the Edit link.

3.

The Views edit screen is very complex, but by reading the options carefully, you should be able to find
the right ones. The top part of the screen is a four
-
column table cont
aining a menu of all the
configuration options for the view. In the second column, look for a link labeled “Header,” and click
on it.

4.

The Header edit field will be displayed below the configuration table. (Unfortunately, this field does
not support the WYS
IWYG editor, so any HTML text in this field must be edited by hand.) Edit the
Header field to show the desired copy, and click
Update

when you are through.

Note:

a.

You may need to click an
Override

button to the upper right of the Header edit field before
y
ou can click the Update button.

b.

If you don’t click
Update
, your changes will not be saved.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
23

5.

You can edit the
Footer

and
Empty Text

fields in the same way.

6.

Click
Save

when you are finished with your edits. You will be returned to the page you started fro
m.


Creating New Pages

While different content types can be presented differently (for example, Events include the dates for the
event), the basic procedure for creating a new page of any content type is the same. Most content types can
be added to the si
te navigation when they are created or edited.

Creating A New Page

To create a new page:

1.

Login to the site.

2.

Select
Content Management

>>
Create Content

>>
Page

(or any other available content type) from
the Administration Menu.

3.

Fill out the form field by

field. You may need to expand some sections to see the field, but all required
fields will be visible. Consult your Quick Guides for more assistance with particular content types or
fields. Here are notes about a few important fields:

a.

Title

is required,
and determines what is displayed above the Body content. By default, it is
also displayed in the browser’s title bar and as the text of a bookmark.

b.

Displayed Title

will replace the title above the Body content, if it’s supplied. Use this to add
formatting

or special characters to a title.

c.

Menu Settings

is where you add pages to the navigation system.
[IMPORTANT]

i.

For
Title
, fill in the text you wish to be displayed on the menu. (You must provide a
title, or the menu settings won’t be saved.)

ii.

If the Title
is clear and descriptive, don't bother filling in the
description
. (Anything
you fill in here will be displayed as a tool
-
tip when you hover over the menu item,
and will be read out loud to visually impaired users with audio screen
-
reading
software.)

iii.

Paren
t Item

determines what menu the menu item appears on. For example, to
create a new menu entry on the "About Us" menu, you should select "About Us" as
the parent item.

iv.

Weight

determines the vertical placement of the item on the menu. It’s best to
adjust the

position of the item later, using the Menu screen. However, if you know
the item will be at the top or the bottom of the list, you can set it to a very low (top)
value (
-
50) or very high (bottom) value (+50).

d.

URL Path

should always be human
-
readable; to
ensure that blocks display propertly, the
path must be consistent with the other pages of that type. For example, all pages in the
"Products & Services" section must have a URL path beginning with "products
-
services/". All
text should be lower
-
case, and wo
rds should be separated by hyphens to improve
readability by both humans and search spiders.

[IMPORTANT]

[Note: Some content types have their URL path set automatically. For those
types, the URL Path field will be disabled.]

e.

Abstract

should be filled in o
n any page that has an Abstract field. (Content types that don’t
have an Abstract field provide an abstract automatically.)

f.

If there will be content in the right column of the page, add it to the
Side Content

field.

Note:

For the present time, most pages
will not have side content.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
24

g.

If you have information to put into the
Meta Tag

fields, click the Meta tags tab to expose
that pane. You’ll usually only need to do this if you want to prevent a page from being
spidered by search engines, or if you want to ad
d Search Optimization content for that
particular page. (Note that if the Description field is left blank, the system will use the
Abstract.)

h.

L
og message
s

can be useful if you are making revisions.

i.

Publishing Options

allows you to show a page to anonymous
users by setting i
t as Published,

include a page in the site’s newsfeed by setting it to Promote to Front Page, or cause it to
float to the top of some View displays by setting it to Sticky.

4.

Click the
Submit

button to save changes to the node.

5.

Check to m
ake sure that the node is showing up where you expect it to. If not, you may need to edit
the
Menu,
Category or Publishing Options.


Creating a New Event Page

You can create a new Event by browsing to
Content management >> Create content >> Event

using th
e
administration menu.

Event pages differ from regular pages in three main ways:



They require you to provide a start date (and optional end date) for the event.



The URL path is automatically generated based on a pre
-
set pattern.



They lack a Side Content f
ield.



Events are displayed automatically on the Events page and in the Events block on the home page and
elsewhere.


Creating a New News Release Page

You can create a new News Release by browsing to
Content management >> Create content >> News Release

usin
g the administration menu.

News Release pages differ from regular pages in two main ways:



The URL path is automatically generated based on a pre
-
set pattern.



They lack a Side Content field.



News Releases are displayed automatically on the News Releases pag
e and in the News Releases
block on the home page and elsewhere.


Creating a New Position Page

You can create a new News Release by browsing to
Content management >> Create content >>
Position
using
the administration menu.

Position pages differ from norma
l pages in the following ways:



Includes required fields for
General Code

Location and Job Category.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
25



Includes a checkbox labeled “Open”, selected by default, which determines whether the page is
displayed on the

Open Positions page.



The URL path is automatically generated based on a pre
-
set pattern.



They lack a Side Content field.



They are displayed automatically on the Open Positions page for as long as the node is published and
the “Open” checkbox is selected.



They are automatically assigned a hidden menu entry underneath Careers >> Open Positions.


To remove a Position from the Open Positions page:

Edit the position to de
-
select the “Open” checkbox. (At this point, potential candidates will still be able to s
ee
the page if they have a direct link to it, though it will no longer appear on the Open Positions page.)


To unpublish a Position:

Edit the position to deselect the “Published” checkbox (under Publishing options). (Once the Position is
unpublished, no o
ne will be able to see it unless they are logged in.)

(See also “Remove Pages”, below.)


Creating a New Simple Node Page

Simple Nodes are used to create units of content that are displayed within other pages. They aren’t meant to
be displayed as pages in t
heir own right, so you don’t normally include them in the navigation.

You can create a new Simple Node by browsing to
Content management >> Create content >>
Simple Node
using the administration menu.

On your site, Simple Node pages are used to create the

content for blocks and QuickTabs. Simple Node pages
differ from normal pages in the following ways:

1.

They are not directly indexed by the search system. (However, if they are included in other pages,
they are indexed as a part of that page.)

2.

They are not
meant to be viewed as standalone pages by anonymous site visitors, and are excluded
from spidering by search spiders.

3.

The URL path is automatically generated based on a pre
-
set pattern. (Since the pages aren’t meant to
be viewed as pages, the URL is not ‘
human readable’, but rather includes the page’s ‘node ID’ as a
component.)

To find a Simple Node page after you’ve created it, go to the content listing screen and filter for the type
Simple Node.

Creating and Formatting Webforms

Webforms are forms that a
llow site visitors to submit information, which can be saved in the website
database, emailed to someone at your company, or both.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
26

The Webform content type is intended to present webforms, and will have a webform attached. It may
include extra fields that

make it suited for displaying webforms and webform
-
instructions.

Creating a Webform

Since webform pages are more complex than normal pages, you will create them in several steps:

1.

Create the webform page

2.

Add form elements

3.

Configure form settings and add
confirmation page text

4.

Optionally add email messages

5.

Adjust form formatting as necessary

Create the Webform

You can create a new Webform node by browsing to
Content management >> Create content >>
Webform
using the administration menu.


Add Form Elements

The form needs form elements in order to collect information.

To add a form element:

1.

Browse to the webform page you want to edit.

2.

Click the Webform button. The Form Components screen will be displayed.

3.

Type a label for the new form element in the blank

field at the bottom of the list of form elements.

4.

Select the form element type (see list below).

5.

Check the box in the “Mandatory” column if the field will be required.

6.

Click Add.

7.

Make sure the Field Key is what you want it to be. (See note about formatt
ing and field keys, below.)

8.

Fill in the fields as appropriate:

a.

Default value will set the field to a default.

b.

Description would be displayed below the field, in smaller type, as an explanation of the
field. (Not recommended unless you have specific instr
uctions you want them to follow.)

c.

Multiple [Select Option and Grid only] determines whether the field uses radio buttons / pull
down lists, or checkboxes and multi
-
select listboxes.

d.

Options [Select Option and Grid only] lets you specify what options are g
oing to be available
for selection.

e.

Allow ‘Other’ [Select Option only] will add an ‘Other’ option to the select element. If visitors
selct ‘Other’, they’ll be given a text field to fill out.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
27

f.

Load a pre
-
built option list [Select Option only] allows you to

quickly add US States or days of
the week to the Options field. (The days of the week could be made to automatically
translate to another language.)

g.

Listbox [Select Option only] lets you stipulate that the choices will be presented as a listbox,
rather th
an as checkboxes or radio buttons. (Listboxes have poorer usability for most people,
but are more likely to comply with ADA Section 508 guidelines for the visually impaired.)

h.

Randomize options [Select Option and Grid only] will randomize the order of optio
ns in the
select element with each page load. This helps to mitigate bias arising from a choice’s
position in the list.

i.

Mandatory causes the field to be required.

j.

Unique means that no other field on the page can have this value. (Not commonly used.)

k.

File

types [file only] lets you stipulate what kinds of file visitors will be permitted to upload.
For résumés, for example, you might want to select txt, rtf, doc and docx. Specify extenions
you don’t see on the list in the Additional Extensions field.

l.

Max u
pload size [file only] lets you set an upper limit to the size of files.

m.

Start / End year [date only] are the farthest back and forward that a visitor can specify a
date.

n.

Popup Calendar allows visitors to use a JavaScript
-
based popup calendar to select th
e date.

o.

Use textfield for year allows visitors to type the year instead of selecting it via popup.
(Default is un
-
selected.)

p.

Width will be over
-
ridden by the size value specified in the stylesheet.

q.

Labels to the left and right may be useful for fields th
at will contain currency or units of
measure. Label display defaults to ‘above.’ Your site is formatted to cope with labels above
the field; inline labels may not look very good. (Avoid using no label, as it is poor usability for
disabled site visitors.)

9.

W
hen you’re finished click
Save

component
.


About Tokens

Tokens are essentially substitution codes, recognized by the system. You can use tokens to insert values into a
field. For example, you could insert the current date with the token %date. Where it’s
possible to insert a
token into a field, there will be a list of available tokens in a collapsed section directly below the field.


Types of Form Element


Field Type

Description

Use For

Special
Considerations

Textfield

A single line of text with no
markup

code of any kind.
Normally limited to 128
characters in length.

Names, addresses, postal
codes, phone numbers,
etc.



General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
28

Textarea

A large text area that
allows for multiple lines of
input.

Longer
-
form text like
feedback messages.

Default size values will
usually be adequate.

E
-
mail

A special textfield that
accepts e
-
mail addresses.

Email addresses.


Select options

Allows creation of
checkboxes, radio buttons,
or select menus.

Lists of states or
countries; lists of items.

Select “Multiple” to
make a sin
gle
-
option
select display as a
checkbox.

Avoid radio buttons if
your form must be
ADA Section 508
compatible.

Lists of checkboxes
will not be Section 508
compliant; however,
you can create a
structure that is
compliant by nesting
individual select fields
,
as checkboxes, within
a Fieldset (see below).

File

Allow users to upload files
of configurable types.


The formatting of File
elements won’t be
consistent from one
browser to another;
we’ve tried to format
it to look OK in all the
main families (IE,
Mo
zilla and Webkit).

Date

Presents month, day, and
year fields.

Dates.

For specific dates, it’s
better to use a Select
field.

Time

Presents the user with
hour and minute fields.
Optional am/pm fields.



Markup

Displays text as HTML in
the form; does not

render
a field.


Make sure this is
entered as HTML, with
proper paragraph
containers, or it may
not display at the
correct size.

Fieldset

Fieldsets allow you to
organize multiple fields
into groups.


By default, rendered
with a thin border
around the fi
eldset
and the fieldset
Legend in bold.

Fieldset legends
cannot be made to

General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
29

line
-
wrap

in Internet
Explorer, so you
should keep them
short.

Grid

Allows creation of grid
questions, denoted by
radio buttons.


May not be compliant
with ADA Section 508
requir
ements.

Hidden

A field which is not visible
to the user, but is recorded
with the submission.


Use this to store
information that the
visitor isn’t meant to
know about. (Do
not

use it to store email
addresses


they’ll be
visible to spambots.)

Can be use
d to hold
the value of system
tokens generated
when the page was
originally loaded.

Page break

Organize forms into
multiple pages.


Use for surveys.


Assigning a Field Key to Form Elements

While most form elements will display without a problem, some w
ill not display properly unless they are given
the correct
field key
.

The field key determines the style classes and IDs that are applied to the form element. See ‘Formatting the
Webform’, below, for more detail.

The following lists fields which are know
n to require a special name in order to display as
-
designed.

Type of data

Value of ‘field key’

City, as part of a street address

city

State, as part of a street address

state

Postal code or zip code (depending on audience), as
part of a street address

zip

postal_code


Configure Form Settings and Add Confirmation Page Text

The form settings screen lets you control several aspects of how the form behaves:



Message that’s displayed on the web page when the form has been submitted.



Whether you will redirec
t visitors to a different page entirely when they’ve submitted the form
(generally you will leave this set to ‘confirmation page’).



Submission limit, which helps to mitigate the risk of people using the form to spam you or others. Fill
this in with the ma
ximum number of times per hour or day that you think someone will have a

General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
30

legitimate reason to contact you. (But leave this value un
-
set until after you’ve launched your site, or
it will get in the way of your testing.)



Status of the form is open by default
; setting it to closed will prevent people from submitting the
form.



Submission access lets you control who can submit the form. Checking both Anonymous and
Authenticated users will allow anyone to submit the form.



Advanced Settings allow you to:

o

Make t
he form available as a block (useful for forms you want to display at different places
throughout the site),

o

Show the form in a teaser (not terribly useful for most sites)

o

Show “save draft” button and Save draft between pages (only useful for complex form
s such
as surveys)

o

Show notification about previous submissions (only relevant for logged
-
in users)

o

Submit button text (change the text on the
Submit

button for the webform)

Add Email Notifications

The webform can also send email when a form is submitted.
You can add an arbitrary number of emails that
are triggered and sent when someone submits a form. We recommend sending a confirmation message to the
site visitor, and a message with the visitor’s information to a designated person at your organization.

T
o add an email to a webform:

1.

Click on the
E
-
mails

button.

2.

Specify an address to send the message to, or select a webform component that will supply the email
address.

3.

Click
Add
.

4.

Fill in Subject, from address, and from name (or select options from the p
ull
-
down lists). We
recommend clear, informative subject lines, rather than subjects that are designed to grab attention,
because clear and informative subjects are more likely to pass spam filters and more likely to be
opened. Similarly, the ‘from’ addres
s should be an address that can actually receive email, and to
from which someone can actually get a response.

5.

Fill in the Email Template field. Your site will be configured to send emails from webforms as HTML,
so this message should be in HTML to preven
t it from collapsing in the recipient’s email client.

6.

Click
Save

email

settings

when you are finished.


Confirmation Email

For a confirmation email, we recommend a simple thank you. If you respond to people who send emails via
your contact forms, it’s a g
ood idea to give the sender an estimate of when they can expect to hear from you.
If the form is being used to submit complex information, such as a request for a quote, you may want to echo
the information back to them so they have the opportunity to corr
ect any errors.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
31

Notification Email

This should be sent to a role
-
based address (e.g. ‘contact@example.com’) that’s checked routinely by
someone. The default message will probably be OK, as long as you take care to apply HTML formatting. You
should establis
h clear internal protocols for how messages are handled.

Formatting the Webform

Your stylesheet includes default formatting for webform fields. (See “Assigning a Field Key to Form Elements”,
above.) Any formatting beyond the defaults must be carried out b
y editing the site stylesheet.

Each form element is wrapped within two layers of DIV containers, and corresponds to an associated LABEL
container. Elements are tagged according to their field type and field key. As a consequence, it is possible to
format
forms and form elements with a high degree of precision, if it is required.

Converting Pages from One Type to Another

There are two ways to convert pages from one content type to another: Individually, and in a batch.

For most conversions, you will be a
ble to click from one step to the next without making any new choices.
However, since not all nodes store the same kind of information, you may lose some information in converting
from one type to another. For example, if you convert a node from an Event t
o a Page, the dates for the event
will usually be discarded, because Pages don’t have fields for storing dates.

Individually

To convert an individual node from one type to another:

1.

Browse to the page display for the node you want to convert.

2.

Click the
C
onvert

button.

3.

Select the content type you want to convert to. (Note: Depending on your permissions and the types
of node in question, you may not be able to convert a node of a given type to another type.)

4.

Click the
Next

button.

5.

If the content type you’
re converting from includes extra fields (most do), you will be asked to
confirm which fields in the new content type should be used for the old content.

6.

Click the
Convert

button.


Batch

To convert several pages from one type to another:

1.

Use the Adminis
tration menu to browse to Content Management >> Advanced Content
Management.

2.

Select each node you want to convert by clicking the checkboxes to the left of the node title.

3.

Click the Bulk Operations selector, and select Convert a Node.

4.

Click the
Execute

b
utton.


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
32

5.

Select the appropriate conversion template. If you don’t see an appropriate conversion template, you
will need to either convert the nodes individually, or define a new template (browse to Site Building
>> Node Convert Templates). Click
Next
.

6.

Click
Confirm

to confirm the conversion.


Removing Pages

When you no longer want a page to be displayed to visitors, you have two options:



Unpublish it, which will make it invisible to any user who's not logged in, but keeps the content in the
database (in cas
e you want to use it again).



Delete the page entirely.

Unpublishing

Since deletion is permanent and irretrievable, it’s usually better to unpublish.

There are two ways to unpublish a page: From the page itself, and from the content listing page. Unpublis
hing
from the content listing page allows you to unpublish more than one page at a time; it’s also sometimes faster
than browsing to a page, editing the page, and saving it.

To
unpublish

from the page itself:

1.

While logged in to the website, browse to the

page you would like to unpublish.

2.

Click
Edit
.

3.

Scroll to the bottom of the page, and expand the Publishing Options section.

4.

De
-
select the "Publish" option.

5.

Click
Submit
.

To
unpublish

from the content
listing

page:

1.

Click the List Content link in the Ad
ministration Menu.

2.

Set Status to "published".

3.

Click
Filter
.

4.

Click to select the checkbox next to the title of any nodes you would like to unpublish.

5.

Make sure that the select box underneath Update Options is set to "Unpublish", and click
Update
.

6.

Confi
rm unpublishing.


Deleting

You would want to delete a node if you want to make sure that the content is not preserved in your database
anymore, or if you are concerned about publishing it by mistake. (Some Ask Experts questions might fit this
description.
)


General Code

-

Website Management Training Documentation

|
2011
-
05
-
25

| page
33

There are two ways to delete a page: From the page itself, and from the content listing page. As with
unpublishing, the latter approach allows you to unpublish more than one page at a time.

To
delete

from the page itself:

1.

While logged in to the website,

browse to the News page, and click on the title of the top News story
to load that page.

2.

Click
Edit
.

3.

Scroll to the bottom of the page, and click the
Delete

button.

4.

Click
Delete
.

To
delete

from the content management page:

1.

Click the List Content link i
n the Administration Menu.

2.

Set Status to "published".

3.

Click
Filter
.

4.

Click to select the checkbox next to the title of any nodes you would like to delete.

5.

Make sure that the select box underneath Update Options is set to "delete", and click
Update
.

6.

Con
firm your deletions.


Changing Site Appearance

What You Can, Shouldn’t, and Can’t Change through the CMS

The CMS allows you to change many aspects of your website's appearance, but there are limits.