Take extra care with project names

lornajane commented 2 years ago

Many of the products on the Aiven platform are projects with proper trademarks and we need to name and handle those in line with each project's requirements.

In particular, the Apache projects should be referred to as "Apache [projectname]®" in the first occurence on each page to make sure that readers are clear that this is an upstream project. Later, we can use a shorter form such as just "Flink" or "Kafka".

[ ] Automate checks to make sure that all project names are mentioned correctly, initially and then later, on every page
[ ] Update any existing misuses of these project names, and check for display and layout issues where we make changes

lornajane commented 2 years ago

Vale can do something along these lines, looking at https://docs.errata.ai/vale/styles#conditional

TibsAtWork commented 2 years ago

Some significant amount of updating was done in https://github.com/aiven/devportal/pull/521

dewan-ahmed commented 2 years ago

There's a new update to Aiven for Redis and the usage of ™

An FYI to check the relevant internal channel.

TibsAtWork commented 2 years ago

Updating our vale configuration in various ways is happening at issue https://github.com/aiven/devportal/issues/672 and the PR consequent https://github.com/aiven/devportal/pull/510

aiven / devportal

Take extra care with project names #484