When it comes to content creation in Haiilo, you have several options. Two of the most common apps used for creating, managing, and displaying content and knowledge are the wiki app and the content app. Both apps can be filled with a variety of widgets, use different layouts, and offer great flexibility in composing the desired content.

Aim of the apps

Both apps share a lot of DNA and cater to a common goal: Making information and knowledge easily accessible. At the same time, the cases of using one or the other apps differ from each other.

Content app

The content app can be seen as a blank piece of paper. Admins of a page or community are free to design the app with numerous widgets and compose these within various layout options. Content can be lined up as needed for the desired use case, and the app can reach an extensive length. At the same time, it remains a single "sheet of paper." For this reason, the content app is particularly suitable for introductions and self-contained use cases:

• Overview of information that is stored on a page or community
• Introduction to a department or location
• Introduction of team members

Keep in mind that the content app can only be edited by an admin of the page or community in which it is installed. For this reason, the content app is one of the more static elements of Haiilo and caters to use cases best, where the carried information has a long lifetime value.

Wiki app

If the content app is the piece of paper in Haiilo, the wiki app is the book. A wiki app consists of a sum of wiki articles that can be structured hierarchically. Each of the wiki articles offers the same layout options and widget composition as the content app. With the help of a so-called "Home article", you can provide an overview at a glance for your users about all included topics and information. As a result, the wiki app can provide easy access to extensive amounts of information that need structure in one place and in a compressed way:

• Company guidelines with different chapters or topics
• Extensive related content that needs to be structured thematically
• FAQ's or Troubleshooting Guidelines

Unlike the content app, the wiki app can be configured to meet the needs of the use case. This way, you can decide if only admins of the page or community or everyone with access can edit the wiki app. As a result, the app can be used way more dynamically than the content app.

Examples

To make both apps and their use cases more tangible, let's provide you with some typical examples.

Content app

The content app is the perfect place to introduce your team, department, or location. With the help of different layouts and widget combinations, all relevant information is assembled clean and accessible at first glance.

Wiki app

You can gather everything your employees need to know in just one wiki app, providing them with all relevant and location-specific HR content in one place. To give a better overview and facilitate access to the different topics covered, we created a "Home article" as the entry point of the wiki app.

Further tips & tricks

• Looking for some more content app examples? Join or go to our client community to discover the content app being used on various pages.
• Nice bonus: Well-structured wikis help to encourage users to regularly visit your platform, as it acts as the central hub to find all information. To prevent your employees from using outdated information from downloadable documents, make sure the latest information is stored within the Wiki App.
• You're just getting started with your intranet? We know it takes a lot of work to create wikis at the beginning so we recommend starting with the most-used instructions, handbooks and policies, for example:
  • HR wikis with holiday requests, policies, expense claims and further training opportunities
  • Knowledge databases with letter templates, glossaries and instruction manuals
  • Service or help wikis, in which templates, FAQs or tips & tricks are brought together