ORACLE CHANGES & ANNOUNCEMENTS GUIDELINES
Embedded Files
1 | HOW TO MAKE EDITS
1 | HOW TO MAKE EDITS
FORMATING
FORMATING
When creating a new training page, use the "Unit Page Template:"
This page gives a rough demonstration of what the content should look like including:
Fonts
Standard Heading/Sub Heading defaults
layout for content containing text and images.
Make sure not to edit the Unit Page Template itself
In most cases where you do not need to make a new training, simply copy the format of the existing training using the same fonts and sizes.
TITLES AND TABLE OF CONTENTS FEATURE
TITLES AND TABLE OF CONTENTS FEATURE
If making a brand new page, make sure to always give it a relevant Title and below that, where you see "Explanatory Text," indicate which department this is intended for use in.
The unit template has a table of contents by default. The advantage of using the built in table of contents is that it will automatically link to all chapter headings and sub headings to make user navigation easier:
Allows users to simply click on chapter headings/sub headings to navigate to that exact place on the web page.
HEADINGS AND SUB HEADINGS
HEADINGS AND SUB HEADINGS
The template includes a table of contents which updates based on how you choose to update headings/sub headings respectively:
Chapter headings:
ALL CAPS
BOLD
MULI SIZE 12
Subheadings:
ALL CAPS
BOLD
MULI SIZE 9.5
Chapter headings are used to introduce an entirely new subject. Subheadings are to be used as mile stones for each part of the curriculum within that chapter.
BODY TEXT
BODY TEXT
Body text will be Muli size 9.5:
It is not a hard and fast rule, but text will usually be used to support images and diagrams and not the other way around.
Make sure to use spell/grammar checking.
DIAGRAMS
DIAGRAMS
Diagrams should illustrate your point as clearly as possible. This may include highlighting parts of diagrams with outlines or red boxes to draw the readers attention.
The example to the right is an example of image highlights being used to illustrate the curriculum being outlined.
2 | LOGGING CHANGES
2 | LOGGING CHANGES
HOW TO LOG CHANGES
HOW TO LOG CHANGES
Every change made needs to be logged. follow these guidelines:
List updates under "Training Updates by course ID:
Needs to list the training by title to ensure ease in hyperlinking with weekly announcements
Make a comprehensive list of changes:
CTRL + ENTER to make new lines in a single cell
Sign off on changes:
Initial and date each update you are responsible for.
For brand new material, list the new training by course ID in the lower "New training by course ID" section:
Leave a brief description and sign off with your initials and the date of changes.
These logs are added to the general announcements at the beginning of each business week by the Sector 2 Training Developer.
For urgent announcements, see URGENT ANNOUNCEMENTS
EXAMPLE
EXAMPLE
URGENT ANNOUNCEMENTS
URGENT ANNOUNCEMENTS
When an urgent announcement needs to be made for the department that you are over, utilize your department's specific announcement dashboard and follow the same general formatting as all other announcements to make an urgent announcement for your team.
3 | INTERDEPARTMENTAL COMMUNICATIONS
3 | INTERDEPARTMENTAL COMMUNICATIONS
WHEN THEY ARE NEEDED
WHEN THEY ARE NEEDED
Interdepartmental outreach will refer to changes that need to be communicated to departments outside of sector 2. Not every change to policy or training will require interdepartmental outreach, in fact, most probably wont.
We only want to make broad announcements to other Sectors/Departments when a change we are making will intersect with another department's process such as changes to deliverables used by Permitting/Utility/HOA/DV or changes to processes such as ancillary work, engineering requests, etc. If the change you have made only affects Sector 2 departments, then no interdepartmental communications will be necessary.
EMAIL TEMPLATE
EMAIL TEMPLATE
When making a broad announcement to other departments, make sure to use the following template:
Subject Line: Update Announcement - DEPARTMENT
________________________________________________________________
Hello all,
We are making the following change in DEPARTMENT to our workflow:
Implementation Date: X
Change Details: X
Reason for Change: X
Updated SOP Link: X
Team's Google Site: X
Page updated
Report abuse