Policy Reference
Category | Application Design and Development |
Approval Date | |
Approved By | Randy Dickey, Chief Technology Officer |
Scope | All personnel adminstering City website content |
Confidential | No |
Procedure Summary
Before posting new content to City of Lee's Summit web pages; content administrators are encouraged to verify the check list items. This is only a summary check list to use on a regular basis. Content Editors must be familiar with the City's "Web Template and Style Standards.
Policy Reference
- List (and link via internal Wiki link tool) to the policy(s) drving this procedure. Normally, a procedure will only be related to one policy. if not, consider consolidating the Policies OR splitting the procedures.
Scope
- This checklist applies to all City website content editors.
- __ Check spelling, punctuation, capitalization.
- __ Ensure standard 'content templates' and 'style' tags were used to generate the page.
- __ Make the Title short but meaningful. Don't use abbreviations in the title. The title is a key element in search engine success.
- __ Check your results by viewing the content within a browser after posting. Ideally, verify the look of the content in both Internet Explorer 6.0 or above and Mozilla Firefox 3.0 and above. Contact the ITS Help Desk if you need these browsers installed/updated.
- __ Verify that all links work.
- __ Remember copyright laws on any non-original content.
- __ Ensure photos have been compressed to enhance page load time.
- __ If updating an existing page, print/save a reference copy of the original text prior to editing it.
- __ Set "Publish" and "Expiration Dates" appropriately. If the content is permanent (no expiration date) notify the ITS Web Administrator of the page location to add to the Site Map.
- __ Follow the no surprises rule. Ensure the posting has been approved and notify the approver(s) when the page is active so they can verify its final accuracy.
- What information does the person(s) carrying out this procedure need to know? Ensure specific training needs are listed.
Knowledge, Tools or Training Required |
ITS Help Desk |
ITS Sys Admin |
Apps Admin |
ITS Ops Mgr |
Mgr IT Proj |
CTO | User |
User Mgr/ Director |
|||||||||||||||||||||||||||
Use of ITS backup system | X | ||||||||||||||||||||||||||||||||||
Change control training | X | X | |||||||||||||||||||||||||||||||||
Knowledge of application of server security | X | ||||||||||||||||||||||||||||||||||
HTML and use of FCK Editor | |||||||||||||||||||||||||||||||||||
Triggers
- List the events that initiate this procedure or drive when it should be followed.
Procedure
- Define the procedure here. Use nesting (via indent) within the numbered list to group steps/tasks as appropriate.
Additional Information/Notes
- For anything else you want to communicate that doesn't fit above.
Compliance
- Normally covered in the Policy, but in some cases - specific regulations might be listed here to the extent the regulation defines a specific "how" you must do something.