feat: Features

[fonodi]

Task Link

Task #2043

Description

Introduced new Features and Features tag collection type, to add new information about the cards on /features page. Also added a migration, that fills out the Features and Features tags with the data on the page.

TL;DR

New Collection types and migrations

New environmental variables

If your PR introduces new environment variables, please list them here along with a description of their use and apply the requires-env-vars label.

Checklist - author

• Assignee is set (the active developer of this PR).
• Reviewers are set (team members who will review the code).
• PR is linked I have linked the PR to an issue in Jira.
• Description I have described the changes proposed in the PR clearly and concisely (more important than what is why).
• Screenshots/Videos I have added screenshots/videos or they were not needed.
• Environmental variables are listed or they were not needed.
• Unit/Integration tests are added for all utilities and business important logic
• Labels I have added labels to the PR.
  • Use requires-env-vars when PR requires environmental variables
  • Use ready-for-review when PR is ready to be looked at
  • Use ready-to-merge when PR has a passing review
  • Use needs-revisions when PR has comments that block merge
  • Use do-not-review when PR is daft only and you don't want to get a review
• [OPTIONAL] Conversation/documentation is started in places where the code is not self-explanatory

Before merging

• PR is approved
• All conversations are resolved
• Pipelines are not failing

Checklist - reviewer

• I understand all proposed changes.
• Necessary after deploy steps are handled by someone (adding new env var, syncing config, running migration...)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website-ui	Ready	Preview, Comment	May 11, 2026 0:01am