Support for incorrect word splitting (adding multilingual spelling & grammar checkers into DatoCMS text editors) [Edited title]

We often struggle with incorrect word splitting in our CMS texts — for example, when compound words are accidentally written as two separate words (for eksample: Skit our instead of ski tour). This type of error can easily occur during fast-paced news production and can negatively affect readability and professionalism.

It would be very helpful if Dato CMS could automatically detect or flag these errors in the editor for review. Ideally, this could be integrated into the text editor or validation layer, supporting Norwegian language rules for compound word formation. This would improve text quality and save time during fast-paced publishing. :folded_hands:

Hi @gunhild,

Welcome to the Dato forum! And sorry about my previous posts, if you happened to see them… I wrote some messages at first and then deleted them, because I wanted to first double-check and verify with the team first.

Usually, grammar checking is a function that’s built in to your web browser, operating system, or a word processing app (like MS Word or Google Docs). There are sometimes ways to add something like that into a CMS, but I’m not sure if we are able to do that with our particular editors. I’ll check with the team and see what they think!

In the meantime, if you need this sooner, might you be able to get to get similar functionality through one of the following?

(I don’t speak Norwegian, so those are just examples… please excuse me if it doesn’t make sense!)

These days, there are also many AI tools that can help proofread your writing, but I am not sure which ones are best for Norwegian.

I know that none of these options are as good as having something integrated into the CMS editor directly. Have you used another CMS that did have such built-in grammar & spelling checkers? Or know of a service that’s especially good for Norwegian?

It’s an interesting idea, just not sure if we would have the resources to implement something like that in the CMS itself. I’ll let you know what the team says. Thanks for the feedback!

(gunhild emailed us to further discuss this issue, so we’re following up there instead.)