kit_cms 2.3.6

data/app/views/admin/dashboard/page.html.erb

@@ -0,0 +1,6 @@
+<% content_for :main do %>
+<div class="help_page" id="db-page">
+  <%= render(:inline=>@help.body)  %>
+</div>
+<% end %>
+

data/app/views/admin/dashboard/pages/_blocks.html.erb

@@ -0,0 +1,108 @@
+<h1>Blocks</h1>
+
+<p>Blocks are pre-defined page elements which can be used in various places in various ways.  They can have parameters to allow them to display something different in each circumstance. As you'll read below, they can appear in layouts, in templates and in editable regions of a page.  They can be shared between pages or unique to a page.  They can contain any content, including various modules which provide advanced content such as a map, a form or a picture gallery.</p>
+
+<h2>Defining a Block</h2>
+
+<p>Blocks are created by choosing "Blocks" from the "Design" menu.  A block can be available only to a specific page template, or it can be available to all page templates.  This doesn't dictate that a block necessarily be used, it is just a mechanism to avoid showing a user the option of adding a block to a page which is using a template in which that block would have no purpose.  For example, a "Article References" block might be available only on a page created with the "Article" template.</p>
+
+<p>A block description should be added to allow an editor/user to know what the block does when they are choosing from a list of available blocks whilst they're editing a page.</p>
+
+<p>The main part of a block is its "body".  The body contains the content which will be displayed when the block is used.  This can contain any HTML you wish (the HTML is not sanitised).  If complex functionality is required withint the block it should be formatted as an ERB template.  For example, you could use a loop:
+
+<pre>
+&lt;% [ "North", "East", "South", "West" ].each do |region| %>
+  &lt;h2>&lt;%= region %>&lt;/h2>
+&lt;% end %>
+</pre>
+
+<h2>Block Parameters</h2>
+
+<p>One of the most powerful features available in a block is that of a Block Parameter.  These allow you to have part of the block be prompted for so that the user provides a value.  To define a parameter, use this syntax:
+
+<pre>
+  [[field_id:field_type:title]]
+</pre>
+
+where "field_id" is a unique identifier for the parameter, "field_type" is one of the following:
+
+<ul>
+  <li><code>line</code>: A single line of text</li>
+  <li><code>text</code>: Several lines of text, i.e. one or more paragraphs</li>
+  <li><code>friendly</code>: Several lines of text, with friendly formatting (for adding links, bold, italic, etc.)</li>
+<li><code>image</code>: A single line field with an image browser</li>
+  <li><code>link</code>: A single line field with a link browser</li>
+<li><code>gallery</code>: A select showing the names of the defined galleries</li>
+<li><code>menu</code>: A select showing the names of the defined menus</li>
+<li><code>snippet</code>: A select showing the names of the defined snippets</li>
+<li><code>form</code>: A select showing the names of the defined forms</li>
+</ul> 
+
+and the title is the prompt shown to the editor for this field.  It can consist of anything other than a closing square bracket "]".
+</p>
+
+<p>Parameters are used in the same place they are defined.  That is, when the page is shown, the value of the parameter will replace the parameter definition.  For example, consider this block body definition:
+
+<pre>
+  Hello [[name:line:Contact Name]]!!!
+</pre>
+
+When this snippet is placed on a page, the user will be prompted to enter a "Contact Name".  If they were to enter "Sally Jones" then when the block is rendered on a page it would look like this:
+<pre>
+  Hello Sally Jones!!!
+</pre>
+</p>
+
+<p>For a slightly more advanced example, consider how to add an image in a Block.  The parameter part is actually the "src" tag of the HTML &lt;img> tag, so the block body definition would look like this:
+
+<pre>
+  &lt;img src="[[image:line:Image Source]]" />
+</pre>
+
+or better still, use the parameter type "image" so that the user is offered an image browser to help them fill in the value of the parameter, like this:
+
+<pre>
+  &lt;img src="[[image:image:Image Source]]" />
+</pre>
+
+Assuming the user entered "/images/picture.jpg" as the image source, the end result of either of this would be:
+
+<pre>
+  &lt;img src="/images/picture.jpg" />
+</pre>
+</p>
+
+<h2>Using Blocks</h2>
+
+<p>There are three ways blocks can be used.  These are:
+<ol>
+  <li>The user can add them to an editable region on a page - the parameters the user sets will be stored as part fo the page, so it will be different on each page.  The user can deploy multiple blocks in one editable region and surround the block with other content.</li>
+  <li>An Editable Block which appears in the Page's Template (<i>not</i> in a layout) - how to use this is described below. This is akin to creating an editable region and forcing the user to put a particular block in it, and nothing else.  You must specify default values for any parameters for the block.  The block is stored with the page and so can have different parameters on every page which uses it. Unlike Block Instances described below, the parameters are set when the user edits the page, in the page editor itself.</li>
+  <li>A Block Instance which appears in a Template or a Layout - these blocks must be created, along with their parameters, before they are used on a page. They are shared by every page that uses the layout or template in which they appear.  The parameters are set in the Dashboard.  The parameters can be changed at any time and will immediately change on every page that uses them.  The syntax for using them is shown below.
+</ol>
+</p>
+
+<h3>Editable Block</h3>
+<p>Note, as described above, these can only be used in a Page Template, not in a Layout.</p>
+<pre>
+  = kit_editable_block(block_instance_id, block_id, { defaults })
+</pre>
+For example:
+<pre>
+  = kit_editable_block('special_block_27', 7, {:url=>"http://www.dsc.net", :color=>"red"})
+</pre>
+<p>The block_instance_id must be unique within the page the block is to appear (i.e. if you have two of these editable blocks in one template they must each have different instance IDs. The block_id is the identifier for the actual block definition.  Defaults is a hash with one entry per default value.</p>
+
+<h3>Block Instance</h3>
+<p>Note, as described above, these can appear in either a Page Template or a Layout.</p>
+<pre>
+  = kit_block(instance_id)
+</pre>
+<p>instance_id is the name of the block instance, which is set at the time the block instance is created.  To create a block instance, first choose from the list of <a href="/admin/blocks">blocks</a>, then view the detail of the block concerned and choose Create Instance.  Give it a name and set its parameters.  You can change the parameters at any time and they will instantly be updated on every page on which this Block Instance appears.</p>
+
+
+
+
+
+
+

data/app/views/admin/dashboard/pages/_creating-content.html.erb

@@ -0,0 +1,29 @@
+<h1>Creating content</h1>
+	<h2>Step by step instructions</h2>
+	<p>There are two ways to being creating content, you may identify the category you want to create your content in first or you may jump directly to creating an article.</p>
+	<h3>Step 1</h3>
+	<p>Browse to the category you wish your article or web page.</p>
+	<p><img src="/images/tc/db/browse-category.png" alt=""/></p>
+	<h3>Step 2</h3>
+	<p>Identify the category from your existing site architecture (or create a new category) and click to create article.</p>
+	<p><img src="/images/tc/db/categories.png" alt=""/></p>
+	<h3>Step 3 - The Article info page</h3>
+	<p><img src="/images/tc/db/article-info.png" alt=""></p>
+	<ul>
+		<li>Title - Enter the title you wish to appear on the page. Note this will automatically be made into your H1 tag and style.</li>
+		<li>Name - Enter the file name you wish to appear within the site architecture. This determines the url of the web page. Note this defaults to a file name version of the title but can be changed manually.</li>
+		<li>Page template - select the layout required for the page.</li>
+		<li>Tags - Optionally enter descriptive words separated by a comma to aid searching and categorising</li>
+		<li>Status - Set the <a href="/db/publishing-status">publishing status</a> for the page. Note this can be updated later.</li>
+		<li>Meta description - Enter a brief description of the page to be created. This is for search engine optimisation purposes and is entirely optional.</li>
+		<li>Meta keywords - If desired enter some keywords that illustrate the content of the page. Again this is for search engine optimisation purposes if required.</li> 
+		</ul>
+		<p>Click Create Article.</p>
+		
+		<h3>Step 4 - Editing in place</h3>
+		<p>You have created your page and now may edit it at will. The edit in place function allows you to directly interact with the page. Simply click on the area you wish to edit and begin typing. Double clicking will bring up a <a href="/db/editor-helper">editor helper</a> which you may use to add images or other media, adjust the styling or view the html source code.</p>
+		<p>Changes will autosave every couple of minutes and revisions to the pages are kept and may be accessed on the <a href="/db/editing-content">via the editor menu.</a></p>
+		<p></p>
+	<br/>
+	<p><a href="/db/help">return to help index</a></p>
+		<br/>

data/app/views/admin/dashboard/pages/_dashboard.html.erb

@@ -0,0 +1,21 @@
+	<h1>The Dashboard</h1>
+	<p>The dashboard is the Kit homepage and the central hub of content and community management.</p>
+	<img src="/images/tc/db/dashboard.png" alt="">
+	<h2>Recent items</h2>
+	<p>Recent pages displays the most recently created content. Each page is displayed as a link and which allows editing in place if followed. 'Show more' allows you to see a comprehensive history of the pages created and to filter that list by their status or by searching for their tags or filename. For more information about page status please refer to the <a href="/db/publishing-status">publishing status</a> help document.</p>
+	<p>Recent forum posts displays the most recent forum posts at a glance allowing moderators quick access to active threads and to management of individual posts.</p>
+	<h2>To Do</h2>
+	<p>Shared to do list. Any individual granted access to the system may add an item to the list and mark it completed. Typing directly into the box and clicking add will add your item to the list.
+		<p><img src="/images/tc/db/to-do.png" alt=""/></p>
+	<p>To mark an item as complete, simply click on the item and it will be struck through. This action is saved and the item will disappear from the list upon navigation away from the page. The action can be undone while you remain on the page.</p> 
+	<h2>Menu items</h2>
+	<ul>
+		<li>Site - Main pages of the live site, including the home page and the forum</li>
+		<li>Content - Primary access to your Content Management System. See <a href="/db/creating-content">creating content</a> and <a href="/db/editing-content">editing content</a> for further details.</li>
+		<li>Resources - Image and other file uploads browsing facility. Allows bulk operations of tagging and individual searching of filenames and tags. Blocks for site search and social network integration may also be accessed here. Note: editing these requires understanding of html and should only be attempted by a skilled practitioner.</li>
+		<li>Users - Central point for user management</li>
+		<li>System - Internal forums private to the admin and editing team and access to personal account details.</li>
+		</ul>
+<br/>
+<p><a href="/db/help">return to index</a></p>
+	<br/>

data/app/views/admin/dashboard/pages/_definitions.html.erb

@@ -0,0 +1,43 @@
+<h1>Page Component Definitions</h1>
+
+<ul>
+  <li>A <b>Page</b> consists of a...</li>
+  <li><b>Layout</b> (which references <b>a Stylesheet</b>)</li>
+  <li>which has a...</li>
+  <li><b>Template</b></li>
+  <li>which is made up of...</li>
+  <li><b>Content</b> (text, formatted with HTML) and/or...</li>
+  <li><b>Fields</b> (in to which a user can enter content and/or <b>Blocks</b>) and/or... </li>
+  <li><b>Editable Blocks</b> (which have parameters which the user can set when they edit the page on which this editable block appears) and/or...</li>
+  <li><b>Block Instances</b> (which have parameters which can be edited in the Dashboard, which are then shared across pages)</li>
+  <li><b>Modules</b> 
+</ul>
+
+
+<ul>
+  <li>A <b>Field</b> is an editable region on a page and can be a...</li>
+  <li><b>text</b> field or a</li>
+  <li><b>line</b> field.</li>
+</ul>
+
+<ul>
+  <li>A <b>Block</b> is a reuseable part of a page which can contain...</li>
+  <li><b>Content</b> (text, formatted with HTML) and/or</li>
+  <li><b>Modules</b> (pre-built functionality) and/or</li>
+  <li><b>Parameters</b> (options which the user will fill in, with defaults)</li>
+</ul>
+
+<ul>
+  <li>A <b>Block Instance</b> contains a...</li>
+  <li><b>Block</b> complete with...</li>
+  <li><b>Parameter Values</b> (set at the time of creation)</li>
+</ul>
+
+<ul>
+  <li>A <b>Module</b> is a snippet of code which provides functionality such as...</li>
+  <li><b>Map</b> or...</li>
+  <li><b>Form</b> or...</li>
+  <li><b>Gallery</b> or...</li>
+  <li><b>Reuseable Snippet</b> etc</li>
+</ul>
+

data/app/views/admin/dashboard/pages/_editing-content.html.erb

@@ -0,0 +1,20 @@
+<h1>Editing content</h1>
+<img src="/images/tc/db/quicktip-edit.png"  align="right"/>
+	<h2>The 'In place Editor'</h2>
+	<p>Kit enables dynamic interactive in place editing.</p>
+	<p>Once logged in simply browse to the page you wish to edit and enter edit mode. There are a number of ways you can do this. If you have arrived at the page from the Kit dashboard then you will be in edit mode automatically. If you have arrived by browsing the live site then you may choose to edit the page by altering the url. Adding ?edit=1 onto the end of any of your webpages will bring you into the edit mode.</p>
+	<p>Whenever you are using the in place editor you will see the Kit menu bar across the top of the page and the pink flash to highlight actions. While you are editing the flash will display "editing" and let you know when a save has been completed.</p>
+	<p>Double clicking in any editable region will bring up the editor helper which contains all the standard word processing options, a full list of which can be found in the <a href="/db/editor-helper">editor helper</a> article</p>
+	<p>Previous versions of pages are stored on the Kit system so you may review these and publish a previous version if you need to.</p>
+	<p>To access and view previous versions, follow the 'info' link on the edit menu in the top right of the page.</p>
+	<h2>The Edit menu</h2>
+	<p><img src="/images/tc/db/edit-menu.png" /></p>
+	<p><b>User View</b> - This allows you to see the page as a user would, without the Kit menu or placeholder text.</p>
+	<p><b>Edit info</b> - The edit info page will allow you to alter the status of a page, to adjust or add the meta elements and any of the editable regions in raw html</p>
+	<p><b>Info</b> - The info page shows you all the information about that page, it is also where you amy write notes to other editors for them to review and where you may see the history of the page and publish an earlier version if you wish.</p>
+	<p><b>Index</b> - The index link will take you directly to your site architecture page where you may access the pages in a tree-like structure.</p>
+	<p><b>Edit:areas</b> - Beneath these main options are the edit area links, by clicking on any of these you can go to each editable region on the page.</p>
+		<p></p>
+	<br/>
+	<p><a href="/db/help">return to help index</a></p>
+		<br/>

data/app/views/admin/dashboard/pages/_editor-helper.html.erb

@@ -0,0 +1,25 @@
+<h1>Editor Helper</h1>
+<p></p>
+
+<p><img src="/images/tc/db/editor-helper.png" /></p>
+<p>The editor helper can be used to style and format content and to upload and edit links, images and media. The buttons included are standard to most wysiwyg editors and word processing software. Some more unusual ones are detailed below. The function of all of the buttons can be found by hovering over the icon.</p>
+<img align="left" src="/images/tc/db/editor-helper1.png" />
+<h2><ul>
+	<li>find and replace</li><br/>
+	<li>toggle invisible elements</li><br/>
+	<li>show visual control characters</li><br/>
+	<li>clean up code</li><br/>
+	<li>remove formatting</li><br/>
+	<li>toggle fullscreen</li><br/>
+	<li>edit source code</li><br/>
+	<li>insert a link</li><br/>
+	<li>insert an image</li><br/>
+	<li>embed media</li><br/>
+	<li>insert special character</li><br/>
+	<li>insert predefined template</li><br/>
+	<li>insert anchor</li><br/>	
+	</ul>
+	</h2>
+<br/><br/>
+<p><a href="/db/help">return to index</a></p>
+	<br/>

data/app/views/admin/dashboard/pages/_faq.html.erb

@@ -0,0 +1 @@
+<h1>FAQ</h1>

data/app/views/admin/dashboard/pages/_forum-moderation.html.erb

@@ -0,0 +1,19 @@
+<h1>Forum moderation</h1>
+<p>	All logged in users may report a post as inappropriate by clicking the report post link. This sends a notification to the community management team.</p>
+
+<p>Moderators have additional privileges to regular users and may edit content within the forums. For moderators, the IP address of the user is always shown in order to allow quick identification of trolling.</p>
+	
+<h2>Topic comments</h2>
+<p>At the top and bottom of each topic and thread within a topic there is an editable region. Here text may be entered by moderators, commonly this area is used for describing the topic or giving guidelines to appropriate content or legal disclaimers.</p> 	
+<h2>Deleting a thread</h2>
+<p>Threads can be deleted by any moderator by clicking the link, it is important to note that threads may also be 'undeleted'. When a thread is deleted it is no longer visible to regular users.</p>
+<h2>Locking a thread</h2>
+<p>There are scenarios when moderators may wish a thread to remain on site but for no more comments to be added to it. In this case a moderator can 'lock' a thread. Users will still be able to view the thread but not to make any additional posts.</p>
+<h2>Post moderation</h2>
+<p>Posts may be deleted or edited. When a deletion or edit happens the action is logged and the moderator can optionally add their own private comment viewable only to other moderators.</p>
+<p><img src="/images/tc/db/edit-post.png" /></p>
+<p><img src="/images/tc/db/mod-comments.png" /></p>
+<p>A post on a thread may also be linked to directly. By clicking 'link' the exact position of the post within the thread is copied to a moderator's clipboard and they may use that to send to other moderators.</p> 
+	<br/>
+	<p><a href="/db/help">return to index</a></p>
+		<br/>

data/app/views/admin/dashboard/pages/_getting-started.html.erb

@@ -0,0 +1,10 @@
+	<h1>Getting Started</h1>
+	<h2>Logging into your account</h2>
+	<p>Enter your email and password. If you forget your password, use the password recovery link at the bottom of the log in page.</p>
+	<img src="/images/tc/db/logging-in.png" alt="">
+	<h2>Changing your password</h2>
+	<p>Follow the 'My Account' link and enter a new password in the boxes provided. Note, you will need to enter your existing password to confirm the change.</p>
+	<img src="/images/tc/db/change-password.png" alt="">
+	<br/>
+	<p><a href="/db/help">return to index</a></p>
+		<br/>

data/app/views/admin/dashboard/pages/_guidelines.html.erb

@@ -0,0 +1,2 @@
+<p><strong>Etiquette in Technology</strong>&nbsp;is the conduct that is socially acceptable in an online or digital situation.</p>
+              <p>Common rules for e-mail&nbsp;and USENET such as avoiding&nbsp;<a title="Flaming (Internet)" href="http://en.wikipedia.org/wiki/Flaming_(Internet)">flamewars</a>&nbsp;and&nbsp;<a title="Spam (electronic)" href="http://en.wikipedia.org/wiki/Spam_(electronic)">spam</a>&nbsp;are constant across most mediums and communities. Another rule is to avoid typing in&nbsp;<a title="All caps" href="http://en.wikipedia.org/wiki/All_caps">all caps</a>&nbsp;or grossly enlarging script for emphasis, which is considered to be the equivalent of shouting or yelling.&nbsp;</p>

data/app/views/admin/dashboard/pages/_help.html.erb

@@ -0,0 +1,38 @@
+<h1>Kit CMS and Community Management</h1>
+<p>This area provides help and resources for using Kit to manage your website.
+</p>
+
+<h2>The Basics</h2>
+<ul>
+		<li><a href="/db/getting-started">Getting Started</a></li>
+		<li><a href="/db/dashboard">My Dashboard</a></li>
+		<li><a href="/db/structure">Website structure</a></li>
+		<li><a href="/db/newsletters">Newsletters</a></li>
+</ul>
+<h2>Content Management System</h2>
+	<ul>
+		<li><a href="/db/creating-content">Creating Content</a></li>
+		<li><a href="/db/editing-content">Editing Content</a></li>
+		<li><a href="/db/seo-content">Optimising content</a></li>
+		<li><a href="/db/publishing-status">Publishing status</a></li>
+
+                <% if can?(:access, :rails_admin) %>
+                <li><a href="/db/templates">Templates, Layouts and Stylesheets</a></li>
+                <li><a href="/db/blocks">Blocks</a></li>
+                <li><a href="/db/help/definitions">Definitions for Parts of a Page</a></li>
+                <% end %>
+
+	</ul>
+<h2>Community Management</h2>
+	<ul>
+		<li><a href="/db/user-management">User management</a></li>
+		<li><a href="/db/forum-moderation">Forum moderation</a></li>
+	</ul>
+	
+<h2>Quick links</h2>
+	<ul>
+	<li><a href="/db/insert-image">Inserting an image</a></li>
+	<li><a href="/db/insert-link">Inserting a link</a></li>
+	<li><a href="/db/editor-helper">Editor helper</a></li>
+	<li><a href="/db/image-sizes">Image sizes</a></li>
+	</ul>

data/app/views/admin/dashboard/pages/_image-sizes.erb

@@ -0,0 +1,16 @@
+<h1>Image sizes</h1>
+
+<h2>Home pages</h2>
+<p>The top section of these pages is usually styled with a large picture on the left with some text to the right. Beneath this in the main body of the page, there is usually a small thumbnail picture and some text to the right with a title above.<p>
+
+<h2>Article pages</h2>
+<p>These are similar to the home pages in the top section but the main body tends to be more text focused with pictures to illustrate the article.</p>
+
+<p><b>Top section pictures - 350x250 px works well.</b></p>
+<p>Exceeding 350px may break the layout. If a wider picture is desired, for example stretching across width of top section then delete content of "image teaser", this will allow "quote & summary" to become left aligned. Then insert wider picture into "quote" section.</p>
+<p><b>Thumbnails - 150x100px works well.</b></p>
+<p><b>Main article pictures - 250px.</b> This makes a reasonably medium sized picture in your main body text.</p>
+
+<h2>Leaderboard</h2>
+<p>The space for the leaderboard is: 560 x 70 px. However, a standard banner size is 468 x 60 so you may find advertisers prefer to give you creatives in that size. The standard banner will fit well into the leaderboard space.</p>
+<p><i>NB, advertising creatives (graphics) are best delivered in .png, .gif or .jpg.</i></p>

data/app/views/admin/dashboard/pages/_image_sizes.erb

@@ -0,0 +1,17 @@
+<h1>Image sizes</h1>
+
+<h2>Home pages</h2>
+<p>The top section of these pages is usually styled with a large picture on the left with some text to the right. Beneath this in the main body of the page, there is usually a small thumbnail picture and some text to the right with a title above.<p>
+
+<h2>Article pages</h2>
+<p>These are similar to the home pages in the top section but the main body tends to be more text focused with pictures to illustrate the article.</p>
+
+<p>Top section pictures - 350x250 px works well.</p>
+<p>Exceeding 350px may break the layout. If a wider picture is desired, for example stretching across width of top section then delete content of "image teaser", this will allow "quote & summary" to become left aligned. Then insert wider picture into "quote" section.</p>
+<br/>
+<p>Thumbnails - 150x100px works well.</p>
+<p>Main article pictures - 250px wide makes a reasonable medium sized picture in your main body text./p>
+
+<h2>Leaderboard</h2>
+<p>The space for the leaderboard is: 560 x 70 px. However, a standard banner size is 468x60 so you may find advertisers prefer to give you creatives in that size. The standard banner will fit well into the leaderboard space.</p>
+<p><i>NB, advertising creatives (graphics) are best delivered in .png, .gif or .jpg.</i></p>

data/app/views/admin/dashboard/pages/_insert-image.html.erb

@@ -0,0 +1,16 @@
+<h1>Inserting an image</h1>
+<p>Images can be inserted into editable regions using the editor helper.</p>
+<p>Clicking the insert image icon brings up the insert image pop up, here there are three ways to choose an image.</p>
+<p><img src="/images/tc/db/insert-image.png" /></p>
+<h2>Uploading an image</h2>
+<p>The default tab is for image uploading. Clicking the 'Choose File' button will take you to your local file system where you may browse to the image you need. Once you have chosen your file you can optionally give it a name and tag it so you can easily find it again later. Additionally you can change the filename if needed. Click upload and you'll be taken to preview your image.</p>
+<h2>Browse</h2>
+<p>Alternatively, you may browse to find previously uploaded images. You can also search for a name or tag to find the image.</p>
+<h2>Recent</h2>
+<p>Recently added images are displayed in the 'recent' tab and can be selected directly from there.</p>
+<h2>Previewing your image</h2>
+<p>Once your image is uploaded and selected you can set the size, add any padding needed and set the alignment wrap.</p>
+<p>The size required will depend on the context, however a good rule of thumb is that the smallest is a thumbnail picture. The image will preview when you select a size to allow to make an informed choice. You can always return to adjust the size if needed.</p>
+<br/>
+<p><a href="/db/help">return to index</a></p>
+	<br/>

data/app/views/admin/dashboard/pages/_insert-link.html.erb

@@ -0,0 +1,17 @@
+<h1>Inserting a link</h1>
+<p>Links can be inserted into editable regions using the editor helper.</p>
+<p>Clicking the insert link icon brings up the insert image pop up, here there are three ways to enter a url to create an on page link.</p>
+<p><img src="/images/tc/db/insert-link.png" /></p>
+<h2>Entering a link manually</h2>
+<p>The default tab is for manual entry and to enter additional details about your link. To link to external websites enter the web address in the URL box.</p>
+
+<h2>Linking to an existing internal page</h2>
+<p>Existing pages can be linked to by browsing to the correct category and article. The search feature can also be used to identify a page via a name or tag. Selecting a page will bring you back to the Link details.</p>
+<h2>Linking to a file</h2>
+<p>Resources such as pdfs may also be linked to within a page. The 'link to file' tab will allow searches of existing resources and new resources to be uploaded.</p>
+<h2>Customising a link</h2>
+<p>Once a link has been selected it must be given anchor text. This is the text that a user will click on. Optionally a title may also be entered which will be visible to users when they hover over the link.</p>
+
+<br/>
+<p><a href="/db/help">return to index</a></p>
+	<br/>

data/app/views/admin/dashboard/pages/_newsletters.html.erb

@@ -0,0 +1,46 @@
+<h1>Newsletters</h1>
+	<h2>Creating a newsletter</h2>
+	<p>Newsletters are created by the editorial team within their email clients or webmail accounts. As with any email the content can be composed in either rich text, including html or plain text. The CMS may be used to create the html but it ought to be noted that the html will then need to be edited to remove any dynamic content (for example Twitter feeds).</p> 
+	<p>Once the team is happy with the email look and content it must be emailed to the specified newsletter address. This can be any TC owned email address and the 'from' address can be different if wished.</p>
+	<p>The completed newsletter will be distributed via email therefore the usual recommendations are applicable.</p> 
+	<ul>
+		<li>It is inadvisable to use large images as some users' email clients may reject larger emails.</li> 
+		<li>Subject lines should be chosen carefully to avoid looking like spam.</li> 
+		<li>Dynamic content should be avoided.</li>
+	</ul>
+	<p>Once the newsletter email is sent to the distribution address it will feed into the system.</p>
+	<h3 style="color:red">IMPORTANT</h3>
+	<p>You must put the word <b>newsletter</b> in the subject line followed by a colon and a space, then enter the subject line you want to appear.</p>
+	<p>An example of a newsletter sent to users with the subject line "News and Events"</p>
+	<p><img src="/images/tc/db/subject-line.png" /><p>
+	
+	<h2>Managing newsletters</h2>
+	<p>The Newsletter dashboard shows a list of newsletters received into the system<p>
+		<p><img src="/images/tc/db/newsletter-dashboard.png" /></p>
+		<p>This provides an overview of the newsletters and their status. Clicking on an individual newsletter provides a more detailed view.</p>
+		<p><img src="/images/tc/db/newsletter-details.png" /></p>
+		<p>There are several options available on this view. You may send the newsletter to yourself only, to a list of test email address or to the subscribers.</p>
+		<p><img src="/images/tc/db/newsletter-send.png" /></p>
+	<p>The lists of testers and subscribers can be viewed with the 'show' links. 
+	<p><img src="/images/tc/db/newsletter-show.png" /></p>
+	<p>Whether a user is subscribed or not can be adjusted within the user management function.</p>
+	
+	<h2>Checking for newsletters</h2>
+	<p>To check whether the system has received any new newsletters click the check button. </p>
+	<p><img src="/images/tc/db/check-newsletter.png" alt=""/></p>
+	<p>If any new newsletters are available they will appear underneath. Note, newsletters will only appear here when 'new'. To see full list of newsletters available in the system click Back to newsletters.</p>
+	<p><img src="/images/tc/db/newsletters-found.png"> 
+	<h3>Warnings</h3>
+	<p>A warning will show if an untested newsletter is about to be sent direct to subscribers.</p>
+	<p>A warning will show if a newsletter has already been sent and is about to be sent again.</p>
+	<p>A confirmation prompt will show before newsletters are sent, either in test mode or subscriber mode.</p>
+	<h3>Legal requirements</h3>
+	<p>It is a legal responsibility to provide an opt-out option for users. This can be in the form of a link to the user's own account page to direct the user to manage their own subscriptions or a contact address to send requests to.<p>
+		<p>"You cannot transmit, nor instigate the transmission of any marketing by electronic mail (whether solicited or unsolicited) to any subscriber (whether corporate or individual) where
+		a. the identity of the sender has been disguised or concealed; or
+		b. a valid address to which the recipient can send an opt-out request has not been provided."</p>
+		<a href="http://www.legislation.gov.uk/uksi/2003/2426/made">The Privacy and Electronic Communications (EC Directive) Regulations</a>
+
+	<br/>
+	<p><a href="/db/help">return to help index</a></p>
+		<br/>