Introduction

HTML content serves as the cornerstone of Omega 365's Content Management System. We use the functionalty for updating information on Infoscreens across all Omega office locations, maintaining and developing our official website (www.omega365.com), as well as creating a range of essential resources such as employee guidelines, blogs, user guides, and training materials. By leveraging the capabilities of the Omega 365 Content Management System, we streamline our content creation and management processes, ensuring efficient and effective communication both internally and externally

About HTML Content Items

HTML content refers to content written using the HTML format. Omega 365 utilizes web browsers as the platform for displaying various types of content. With HTML, we can create rich content that combines text, images, videos, and formatting options. For more detailed information about HTML Content Items, please refer to the user guide: https://docs.omega365.com/docs?Area-ID=10004&ID=MSI22933. Also, since Omega operates in multiple countries, it was crucial to ensure that the content management system supports multiple languages

In this video you can also learn how to use HTML content items:

Public web sites

Omega 365 is a company with several subsidiaries, and some of them have there own web site. A web site consists of  set of pages, or "Articles" as it is called in Omega 365. Omega 365 Design (omega365.design.no), a company within the Omega 365 group specializing in among other, web design, is responsible for designing these websites.

There are two primary types of articles or pages on our public websites:

1. Static Content: Many web pages consist of static articles that include text, images, and occasionally videos. These articles are simple HTML content items that can be written without requiring any programming or database skills.
2. Static Content Combined with Database Content: By leveraging the wealth of information available within our Omega 365 solution, we can connect and retrieve relevant data. However, utilizing this capability does require some programming skills

To create a new page, we follow this procedure:

1. Create a new Article (page). When creating a new article, one selects what template to use.
2. Write the static content using HTML Content Item
   
   The HSE web page contains just static text, and is written using the HTML Content Items editor. 
   
   The content item is connected to the web page, by using the "slug" field. The "slug" refers to the part of a URL that identifyes a page (e.g. omega365.com/hse - here "hse" is the slug). 
   Also, note that the content can easily be made available at also at other places, e.g. at screens - where only the summary text and the image is shown, or in an employee guideline)
   
3. Will the web page re-use some existing content? If so, choose among the  partial-content articles, which are made to be re-used in different articles.
   
   The overview of where the Omega offices are located are re-used in many of our web pages at different web site.
   
   To include partial content, the page administrator adds a reference to the partial content, by a single line of code:
   
   @await Html.PartialAsync("LocationsListPartial")
   
   
4. Will the web page use information available in the database?
   If so, some "razor" (server side c# code) is written to retrieve this information, and combined with HTML renderedin this example we retrieve the available positions directly from the module used by Omega 365 Consulting for managing jobs and resources
   
   

Blogs

To update our clients about new features in our products, and how these can be utilized, we use blogs. We also have blogs targeting our own employees, to share information about what's going on in Omega.

Our blogs are available on blogs.omega365.com - most are public available, but some require login.

the blogs.omega365.com web site contains several blogs, some mainly for internal use, and some that we think is interesting for others.

The blog contents is based on HTML Content items. Again, these content items can be re-used multiple places, including screens, web sites.

To create a new blog entry, we follow these steps:

1. Create a new HTML content item
2. Publish the content to the relevant org units, or choose "public" if it is to be made available on one of the publicly available blogs.
3. Select one or more "tags":
   

Procedures, policies and other guidelines

All the procedures used in our company are written using the HTML Contents. Here we have good control of revisions and approval. And we can collaborate around the content.

Having procedures and implementing these are naturally a central part of ISO certification. You can read more about how we worked to get ISO-certified and we focus on continuees improvement in this document: https://docs.omega365.com/docs?Area-ID=10004&ID=MSI22958

When we need to create a new procedure, or update an existing, we follow these steps:

1. Create a new HTML content / or navigate to an existing 
2. Create / update the content (when we publish it, the previous one is found in "Preivous Revision".
3. Set who is to be approved by
4. When approved, publish.
5. For new content, open the Content Manuals, and find the manual the content will be a part of

Screens

In Omega we have several infoscreens in offices around the world. This serves as a great way of staying updated, and it contains everything from birthday greetings, visits to office, live count of number of employees and so.

The live overview of the number of employees in Omega's company appears on all the info screens around the Omega offices in the world

In addition we write static content, here we again use "HTML Content", and make it avaiable to the desired screen by using "Tags".

Which tags I can publish to is controlled by access.

The screens can combine static content with dynamic data retrieved from the database, and be presented to various screens in Omega.

Training material, presentations and user documentation

At Omega we produce both user guides and training courses aimed for both the internal and external users. Whether it's the Omega 365 Document Management for Super Users course, an introductory course on Risk Management, or a specialized training program designed specifically for our own employees, such as "How to Get Started," we strive to provide valuable learning experiences for all.

And again, HTML Content is the source. For user documentation, we organize it in manuals, for example "Omega 365 Document Management", where all Content Items related to this are added.

When it comes to courses and other presentations, the concept is that use "Sessions". A session is a walk-through of a manual. So when use the session viewer, the manual is presented as slides, with easy navigation between the content items (slides in this case).

A session contains HTML Content Items, which can be formatted text and videos.

Sessions can also be used when having a presentation for existing or potential new client, or internally. Of course, it is not easy to compete with Microsoft Powerpoint, so in many cases we still use PowerPoint, but with all the easily available content items, using Sessions is more often a better option.