Organizational pages allow organizational units to communicate to different audiences what they stand for and what they are working on. It is a kind of business card.

An organizational page is no substitute for one's own website and should therefore not be set up that way. After all, we no longer communicate to our customers from organizational units. Organization pages have little content of their own; they mainly refer to content that is disclosed elsewhere in the website.

For example, organizational units have the following target groups/customer routes:

• Potential employees who want to know what is happening within a component to determine if they want to apply; 
• Current employees and students looking for specific contact information or an overview of employees;
• Internal and external researchers and collaborative partners of research institutes who are curious if there is research they can connect to.

All organizational units that are in RBS automatically have an organizational page with contact information in Drupal. Whether you need to enrich the page further depends on whether it is relevant to visitors. This includes the following:

• Some organizational units have so much content that they cannot get by with an organization page and therefore (as an exception) have a landing page with subpages elsewhere in the Web site. There are also organizational units with a website on a different domain than www.ru.nl. In these situations you should not enrich the organization page, since that content is then already elsewhere; only the fields 'Summary', 'Content' and 'Website' may be filled in such a case.
• Also, all (sub)departments of an organizational unit automatically get their own organizational page in Drupal. Enrich only the page that is most relevant to the customer. That is usually the page of the main department.

As an editor, you have quite a bit of freedom to set up organizational pages, by means of paragraphs (content blocks) with self-selected information that is relevant to visitors who want to know something about the organizational unit. You can choose from the following content blocks::

• An overview of / a separate content item with (a) service(s);
• An overview of / a separate content item with (a) project(s);
• An overview of / a separate content item with (a) vacancy(s);
• An overview of / a separate content item with (an) event(s);
• An overview of / a separate content item with (a) news item(s);
• A piece of text (for example about the mission or key figures);
• A picture;
• A video;
• A webform; (still under development)
• A file (for example, an annual report).

To ensure that the pages remain customer-friendly, you must adhere to the following rules:

• Add a maximum of 4 content blocks (= 4 lines of blocks on a desktop view), to prevent contact and employee details from being placed too low on the page. Use a maximum of 2x the same type of content block.
  • For example: maximum 2 blocks with services, 1 block with events, 1 block with 2 columns (of which 1 text block and 1 image).
• Show the content blocks that are relevant to the most visitors at the top and end with content that is relevant to the fewest visitors.
• Banners may not be used on organizational pages, with the exception of microbanners. So do not add an image in the form of a banner either.
• The content block 'web form' may not be used to request services, because the organizational page is not part of a service-providing customer journey. Only use this, for example, to register for a newsletter about organizational unit-related news.

If you decide to enrich the page, you must also keep the page up-to-date. If that is not possible, do not add time-bound content, such as a 'featured' content block about a conference that is taking place soon, to prevent visitors from being confronted with outdated content.

The above guidelines also apply to research groups. In addition, we try to organize all organizational pages for research groups in as similar a way as possible, so that there is consistency for the visitor in terms of the type of information and its presentation. Below you will find advice for the layout of your research group page. However, because there are significant differences between research groups, we cannot make them alike completely.

The order in which you place the content blocks is up to you, but we recommend that you stick to the following layout / components:

1. The 'featured' block. Here you can draw extra attention to specific news items, projects, events or other pages. To do this, choose the content block 'Two columns' with 'Separate content item' twice and put the title 'Featured' above it. Preferably place this block at the top (immediately below the opening paragraphs of the 'Content' field).
2. Substantive content: you can post two types of content on the organization page:
   • Further explanation of its own lines of research, for example to attract collaborative partners. A short text (maximum one paragraph and an image/video) can be used for this. A link can also be added to recent publications of the group (for example on Radboud Repository). (Note: if it concerns only one (broad) project, then a project page should be used instead of an organization page.)
   • Links to other initiatives in which your research organizational unit is involved, such as:
     • Facilities managed/offered by your research organizational unit;
     • Annually recurring internships that are available to students through your research organizational unit;
     • A grant that is available to employees through your research organization unit;
     • Similar initiatives.
3. A news block, a calendar block, or a combined news and calendar block.

To get you started, below are examples of how to design organization pages for different types of organizational units.