An intranet people actually open

Personal for the individual. Structured for the organisation.

The front page is not the same for everyone. Content surfaces by department, by position in the organisation, and by the channels a person chooses to follow. Order, accent colour and density are each employee's own.

An intranet builds culture, or it is just a file server

Most intranets do not fail technically. They fail because nobody has a reason to open them. AabenIntra is built around the opposite premise: make colleagues' work visible.

Recognition with substance

A kudos has a recipient, a badge and a reason. Not a like, but a sentence about what the colleague actually did. That is the difference between recognition someone remembers and a notification they dismiss.

An activity stream that shows contribution

Every publication, comment and recognition is logged at write time. New starters can see who contributes where instead of guessing.

Channels people choose

Employees follow the topics relevant to them, so the news stream becomes something they opted into rather than something broadcast at them.

Communities of practice

Community is its own group type, not a renamed team. Built for networks across departments, with open, closed or secret visibility.

Knowledge sharing in small pieces

Tips are shared by category: how-to, best practice, troubleshooting. A lower barrier than a document, and easier to find again.

Find an expert

Search by skill rather than by name. Useful precisely when you do not know who to ask.

The organisation is not a field. It is a structure.

Most intranets treat department as a tag. Here the organisation is a hierarchy and visibility inherits downward. If Digitalisering writes to the whole municipality, everyone sees it. If they write to their own unit, they do not.

That same lineage drives the dashboard, the news stream and the activity log. One concept, three places, in a single query. It is why targeting does not cost performance.

The activity log is written at write time behind a unique key, so hooks and rebuilds cannot produce duplicates. Personalisation stays cacheable because preferences are expressed as cache contexts rather than by switching caching off.

Platform

Drupal 11.3

Custom modules

11

Contrib dependencies

13

Provisioning

Drupal Recipes

Languages

Danish and English

Licence

Open source

A thin dependency surface is not a limitation, it is what makes a fixed monthly maintenance price realistic.

Mandatory reading with receipts

Policies can be marked mandatory. The employee acknowledges, the receipt is stored, and HR can export a report as CSV. This is the sort of thing that otherwise lives in a spreadsheet beside the intranet.

A fixed price, so the budget is known

7,500 DKK a month, baseline.

Onboarding and training are agreed separately at the start. That is also when the operational layer is stood up for your installation.

Hosting, updates, backups and monitoring

Hosting on European infrastructure, security updates for Drupal core and modules, daily backups with a tested restore, and monitoring with alerting.

Support with response times

A named contact. Critical issues within four business hours, everything else within two business days.

An included change budget

A fixed number of hours each month for new sections, content structure and small features. A retainer should feel like progress, not insurance.

Onboarding and training

Setup, content migration and training for your editors.

They do not exist as a finished service on the demo instance today, and that is precisely part of what the onboarding covers.

What runs today, and what does not

This is a proof of concept with a public demo. Everything below is built and can be seen. What is not built is stated too.

• Built
  Dashboard, news, channels, directory, org chart, expert finder, kudos, activity stream, comments and reactions, groups, mandatory reading with CSV export, Danish and English.
• Not built
  Search beyond Drupal core. No notifications, calendar or surveys.
• Not evidenced
  Accessibility. The markup follows good practice, but no audit has been run. EN 301 549 is a legal requirement for public bodies, so an axe-based CI gate and an accessibility statement belong in a pilot. We already do exactly that on AabenForms.
• One installation
  Multi-tenancy is designed as one container per customer. One runs today, and per-customer branding is not built yet.
• Demo data
  The public demo is seeded with invented content from a fictional Aabenby Kommune. That is deliberate, so you can see it as it looks in use.