Missing heading styles in "installation/advanced/content-styles.html"

[surfinzap]

Origin URL

https://ckeditor.com/docs/ckeditor5/latest/installation/advanced/content-styles.html

Project version

40.2.0

Is the information outdated? How?

No response

Is there something missing in the guide? What is it?

I'd welcome heading styles in the list of content styles as an example to override. I'm assuming that something like this should probably work?

.ck-content h1 {
  font-size: var(--custom-h1-font-size);
}

.ck-content hN {
...
}

Is there anything else you would like to add?

No response

User agent

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0

[Reinmar]

The editor comes with many styles, but mostly related to the "extras". Stuff that otherwise wouldn't look reasonable – e.g. block quotes, code blocks, images, tables, media embeds, etc. The basic typography is left for the integrator as a great majority of integrators will want to have custom styles here.

If we included basic typography into editor styles to make the content look good by default, integrators would have to override those styles, which is always a bit trickier than just writing new.

In other words, this is on purpose. 

However, things may change since we're considering (see #15502) splitting the CSS from the JS soon. The CSS would still be massive, if it contained both the content and the editor styles. Also, the content styles are composed of two parts – those that could be overridden and styles of things like widget borders, the resize handles, etc. The latter should not be touched unless someone really knows what to do.

But anyways, it could be a good moment to consider shipping (apart from the current, combined CSS) a split set of CSS files (editor UI, content UI, and content styles).

cc @filipsobol @Witoso

[Witoso]

Meanwhile, take a look at the headings configuration in which headings can be styled via classes.

[surfinzap]

Thanks, @Reinmar, for explaining the current state and plans, and thanks, @Witoso, for pointing me out to the headings config. Much appreciated!