@Alex-Fiala yes you should be able to use IP addresses. However, you still need to have the protocol in there (http://). Copy the address at which you access your NodeBB server and paste it into the config.json
@kacemlight I know it's a very old topic. Just replying because i faced a similar issue. SEO tools pointed out that the heading structure was incorrect i.e the nav bar headings had H3 and content had H2 and H1.
I solved it by creating a barebones plugin and overwrote the tpl file that had the inconsistent heading structure (in my scenario). The path of the file is plugin/static/templates/partials/menu.tpl
Real preview without rebooting or waiting for over 5 seconds/theme.
Yeah, this is a real problem that I don't think can be solved by wishing it to happen. Not all things are possible with programming, unfortunately; there are real world constraints we have to live with.
AFAIK the current themes require processing since they need to be compiled to CSS that the browser understands, and that requires time. What is sacrificed in time is gained in modularity and composability, which I think is quite a fair tradeoff, unless you plan on changing the CSS constantly (several times a day). This is a scenario I've seen too, but the way to solve it is extremely complex.
But by all means, if you can pull it off, more power to you!
It looks to me like the German translation was intented to be informal. That is what most communities would use anyway and what should be the default. So I would consider the formal language in the recent translation a bug.
I also think the translation could be improved. Most parts are very well translated other parts are not so perfect and a few are just wrong.
I'm also not sure, if there is really a need for a formal German translation. It's just a UI. We wouldn't talk to Siri, Google or Alexa in a formal way.
Of course there is nothing wrong to have a formal translation as an option, but would there be a maintainer? Who wants to do the extra work and keep the two translations in sync.