Our new text editor is now available on all communities!

Not sure about the text-editor, but when it comes to overall in the community - we just change it in custom css:

/* Font styles */

p {
  font-size: 16px;
}

h1 {
  font-size: 39px;
}

h2 {
  font-size: 32px;
}

h3 {
  font-size: 25px;
}

p, h4, h3, h2, h1 {
  letter-spacing: -0.025em;
}

For specifically inside a topic, we use these commands:

/*font-sizes*/
.cke_panel_container h2, .post__content.post__content--new-editor h2 {
  font-size: 31.25px;
}

.cke_panel_container h3, .post__content.post__content--new-editor h3 {
  font-size: 20px;
}

.topic__title {
  font-size: 25px;
}

I tried changing the text-editor, but didn’t manage to make it work i’m afraid 😕

Hi, 

apologies for the delay in response, I relayed this question to our support team last week, but I now noticed that we failed to share an update here. 😐

This is a bit too technical for my knowledge, but I will attempt to relay what I can see in internal discussions:

So the editor itself is currently not able to use custom fonts just yet. We do have a story ticket to have this improved, but I cannot communicate timelines at this moment I am afraid. 

It was pointed out that you should define a fallback font under Theme > Font. The fonts will be applied in the order they are put in the input field. If a font is not available the browser will try to apply the next one. So in the example image Roboto is the fallback font, and if that is not available it"s Helvetica.

This fallback font ideally should be one which is being used in all browsers. I am not sure why, but I assume that this has to do with limitations in loading in custom fonts in the editor.

Hope this helps!

Because there are different fonts so it means that this can be done. But probably this is something only inSided can do. I´ll create a ticket, let´s see.

Thanks.