@Atayz said in Help Translate NodeBB!:
Hey, I've started working on the hebrew translation! 🙏
Nice
Hey guys,
As you probably know, this forum is our usual testbed for the latest and greatest (and sometimes not-so-great) features before they make it into a release of NodeBB.
Many of you are already running the latest master
builds, which gets you plenty of exposure to new features and all the bugs that come with it
However, we also have a develop
branch that contains breaking changes, and occasionally, larger, more adventurous features.
Today we've updated the forum to the latest commit from the develop
branch, with two new features:
The ability to use NodeBB with javascript disabled is potentially interesting for some, as a non-insignificant number of users use libraries such as NoScript and Ghostery to speed up their web browsing and ensure security. With these changes, NodeBB should work better for those users, and they'll finally be able to post.
Right now, I'm composing this topic with javascript disabled
Give it a try (or take a look at the new digest) and tell us what you think!
exciting, as someone who blocks js on all sites by default this is great in terms on usability!
keep it up
I'm not going to lie, I think it's the best feature
Ah, I neglected the most important part about all of this... that this was all done by @An_dz!
Fantastic job
Edit: added attribution in OP
What we can't do without JS now:
@njkdsncds Replies should work, but the registration won't here as we use spam-be-gone and the recaptcha requires js.
I run the develop branch and I get "Forbidden" when trying to login with JavaScript disabled. Log says:
error: /login
Error: invalid csrf token
It's working great here do you have any idea?
Nah I can't reply:
Wow, impressive work!
The no-JS version looks almost exactly identical to the 'full' page.
Would this also enable NodeBB to use progressive enhancement? I'm a bit obsessed with speed, a large part of our revenue is generated by users that visit one or two pages on our forum through a search engine. These users want to see content fast.
If you are a regular user downloading several 100kb worth of CSS and JS is not a problem. You only do that once, after that all you download is some JSON.
The inverse is true for one time visitors. They need to load a LOT of extra data for functionality that they will never use. Another drawback of this is that ads will load slower because they compete with all the 'app' javascript for network and CPU.
Therefor it would be fantastic if the HTML could load and render, then the ads are initialized and then all the NodeBB Javascript is pulled in and executed.
@roldanlt we've rolled back the changes here for now, it'll be reintroduced later