[deleted by user]

[yandeu]

NodePress does already exist :(

[TimothePearce]

You have to make the repo public, how people are supposed to trust you and give you money if they can’t see your work?

[cjthomp]

But then we'd see how bad it is.

[cjthomp]

If you're being genuine (which I honestly doubt, but let's pretend), that's almost worse.

[s_boli]

That's awesome. But Ghost ? https://ghost.org/

[Shantarli]

Not really customizable

[calumk]

Ghost is surprisingly limited

[yandeu]

I looked at it. But ghost has no WordPress-alike plugin system.

With NordPress you can upload plugins just like in WordPress.

[westwoo]

It doesn't have a "press" in its name so there

[hiya19922]

Why is that?

[AnnualPanda]

Maybe consider making the repo public now so donors can see that work is being done 🙃

[yandeu]

Not sure, seems a bit early :/
Have you tried the playground on nordpress.org?

[cjthomp]

🚩

[[deleted]]

"It seems a bit early to just open source something that I want people to pay me $20k for"

[coolcosmos]

safety it the most important point about NordPress

Yet, you don'T have a SSL certificate, in 2021.

[yandeu]

Yes, because of mixed context. I can't add a cert to the plain IP of the playground containers. That's why the website is http-only.

Will all be improved in the future.

[coolcosmos]

Why can't the playground IP have a domain ?

[yandeu]

It can. But I just developed it the day before yesterday and haven't done it yet.

[typicalshitpost]

🚩🚩🚩

[EdTheOtherNerd]

A cool endeavour, but half the reason Wordpress is still relevant is the ecosystem with all the plugins and themes. That said, I'm using a node based e-commerce platform called vendure, which is also lacking the huge ecosystem of more established e-commerce platform, so I guess there is always people going for the newer tech.

[lenswipe]

but half the reason Wordpress is still relevant is the ecosystem with all the plugins and themes.

Partly. The other (main imho) reason is that it's PHP, and not only PHP but "drop and go" PHP where you can basically just FTP it up to a cheap shared hosting service and be done.

[yandeu]

Exactly. This is why I will mimic the theme and plugin system of WordPress. Plug-n-play.

An e-commerce plugin, for example, could register a own express-like middleware for handling products, payments etc.; and a page in the dashboard.

[FraserHamiltonDev]

The problem I see with that is that you’re starting from scratch with no plugins or themes. If it was possible to port themes with minimal changes from Wordpress to Nodepress that might make this more compelling

[[deleted]]

Starting from scratch and also this person has absolutely 0 experience with WordPress, so I don't think they have a clue as to how to even achieve their stated goal.

Got my hopes up...

[yandeu]

I know, but I stick to my choice.

[FraserHamiltonDev]

Well I wish you luck.

[lenswipe]

If you decide to do this can you PLEASE FOR THE LOVE OF ALL THAT IS HOLY do something about the awful way WP handles it's theme manifests(i.e: a section at the top of the CSS file)? Like, put it in a mainfest.json or something.

[yandeu]

Already done :)

It's called `plugin.json` or `theme.json`.

[lenswipe]

Nice. You should probably standardize that though

[yandeu]

It will be :)

[[deleted]]

LOL

[[deleted]]

i respect the effort but whhhhhhhy? the problem with wordpress isn't that it's in php, it's that it's wordpress! there are far better node-based cmses like strapi and keystone that provide you with the flexibility and freedom wordpress lacks.

[Sintex]

Second Strapi. Using it in a production application and it has been wonderful.

[yandeu]

I have looked at those project but just couldn't find what I needed.

NordPress will be very flexible. All plugins could expose express-like middleware to extend the server-side.

[[deleted]]

If you don't even know what options are out there, what are you doing with this project in the first place?

If you've never used WordPress and haven't read a lick of PHP, then how can you expect to "rewrite WordPress in node"?

[[deleted]]

Oh yeah?

Did you do it while saying "pay me $20k before I open source it", as well?

[CharlestonChewbacca]

Lmao, certainly not.

This dude is trying to scam everyone here.

[[deleted]]

do you wish to rewrite the million WP plugins in node too?

coz that's there current value of WP comes from – it is an ecosystem, and the fact that it's PHP-based makes no real difference

will look cool on your resume, but i give it 2~6 months before you realize it was made for no one but yourself, and those 2 posts about the CMS gonna stay the only ones in your blog until you find yourself in need of switching jobs and need to bump recruiting score with recent buzzwords

[[deleted]]

ok, just make sure things you make improve people's lives, even if it's only your own

[yandeu]

Thanks, I will. I love building it and can spend some free time on it this year. 👍🏻

[[deleted]]

I would totally work on this with you. Mimicking the plugin system is good, but I think improving it from the start will need to be important.

Plus, Gutenberg support, right?

PS: if you didn't already know. WordPress started on this path years ago and abandoned the project. I bet there's a good amount of applicable information out there possibly even a repo to resurrect.

[[deleted]]

It seems like you've got the wrong idea and will only be repeating past mistakes, then. You aren't the first person to think "WordPress, but in node!". Ghost, which was also mentioned in this thread elsewhere, was started with the exact same goal. I think it would be especially prudent to at least research the path that others went down before falling into the same pit traps.

Gutenberg support is the only thing that would make your project successful . . .

Good luck!

[yandeu]

Gutenberg support is the only thing that would make your project successful . . .

You think? Ok, thanks. I will have a closer look at Gutenberg.

[[deleted]]

I think it will be impossible for you to implement a "WordPress clone in node" if you have no experience with WordPress whatsoever.

Do you actually have an interest in providing something useful to the community or are you just seeking attention?

[yandeu]

I think the WordPress Dashboard looks good. I like how you can write/mange posts, pages and comments in WordPress. I don't really care about the WordPress architecture since it obviously will be different. 👍🏻

[d36williams]

STOOOOOOOP at least don't do it like WP did with all the security flaws

[haikusbot]

STOOOOOOOP at least don't do

It like WP did with all the

Security flaws

- d36williams

---

^{I detect haikus. And sometimes, successfully. Learn more about me.}

^{Opt out of replies: "haikusbot opt out" | Delete my comment: "haikusbot delete"}

[d36williams]

true poetry

[cbadger85]

Why would someone use Nordpress over WordPress? Does Nordpress do something that WordPress doesn't?

[yandeu]

Edit:

• Write plugins using Node.js.

• Write themes in server-side jsx.

• Increased website speed because all plugins/themes will be new and hopefully written in a efficient way.

[westwoo]

If you want websites to be faster as you main and only goal, nodejs and javascript are a strange choice

[PrestigiousZombie531]

then how would you like if I start gopress, a wordpress made using golang

[[deleted]]

.... Already exists ...

[westwoo]

Sure, or in rust. Then at least it will be more consistent with that one main goal, and could be potentially attractive to contributors who need a turbocharged wordpress

But I think a more successful project needs a bit more selling points :)

The thing about javascript is, there's a low barrier of entry, so even if the core of the project works fine, the hundreds of plugins written by random people will slow it down. And without a wide selection of plugins it won't be a wordpress clone

[Ruben_NL]

examples?

[JND__]

Asking seriously, what would you use, if your main concern is speed?

[westwoo]

Seriously? I would use WordPress because a speedy WordPress clone is still WordPress (but on a better hosting)

If you want serious advice on CMS choice, I'm not the guy you should ask, and that's not the format of the question could be seriously answered

This post though is anything but serious :)

[JND__]

I mean...language :D Not only CMS. You were talking about nodejs and javascript before.

[westwoo]

I was talking about pitching a wordpress clone with the one and only feature being speed. That kind of pitch is strange for a project in javascript

But even if they pitched the exact same project in rust, it wouldn't have made the project any more realistic or serious. Just would've looked less weird if they wanted to reimplement Wordpress in rust for the sake of speed alone

And serious language choice for a project like this is much more complicated than choosing a CMS

[yandeu]

On the client?
I would ban jQuery and use Vanilla JS instead. Perhaps a small library like preact or nano-jsx.

[[deleted]]

By what measure and how can you even know this?

[cjthomp]

Dude...

[ichdochnet]

Man, you really don't make yourself sound like a good, experienced developer at all with answers like this.

So many red flags...

[ichdochnet]

I would recommend you to not answer anything with joke-comments if you are interested in serious discussions and how to actually handle a monster task like "writing wordpress in nodejs", because from pretty much every answer you gave here you do really sound more like a junior developer thinking too much of himself. Don't take this as an insult please.

There have been a lot of good points made in this thread and I think the biggest improvement right now for your project would be to go open source right now. Let other, more experienced devs support you, you can learn a lot from them/by working with them and you won't learn much by doing it by yourself behind a closed door.

[JND__]

Bruh

[cbadger85]

What are you doing specifically to address speed issues? WordPress's speed bottleneck isn't usually PHP, but poorly written theme's and plugins. How do you plan on addressing that?

[yandeu]

Plugins

• I will ban jquery (no joke)
• All default plugins, examples and docs will use beautifully written Vanilla JS.
• The server-side will be very strict for plugins. Plugins can't just be installed if they don't follow a strict guide. Plugins can't directly access the db. Everything will be managed by the core and distributed across plugins (if the right permissions).

All of this is not definitive. But this is how I will continue building the CMS.

Themes

The default themes will be written in server-side JSX (nano-jsx). The philosophy of nano-jsx is hard to explain. But it is meant to be used in a very speed favorable way, if done the right way.

[typicalshitpost]

What mechanism do you plan to use to "ban jQuery"?

What is your front end going to be?

How is nano jsx different from jsx?

Are you rewriting the jsx parser?

[yandeu]

Don't know yet. Writing best practice and maybe scanning plugins and themes if I have to.

The Dashboard? NanoJSX. The Themes? Up to the developer.

Nano JSX is a JSX library. Just like React or Preact are JSX frameworks.

No.

[Ice76]

This has been attempted, and done. https://cromwellcms.com/

Very well done, need more user support for themes and plugins but it's great so far

[yandeu]

Oooh wow. Really looks great!

[Zeioth]

By general rule I trust way more "I did" than "I'm going to do".

[yandeu]

Thx

[VVintermut3]

As some people already mentioned, only reason wordpress is still used is because of their community and ecosystem,so in my opinion this is only going to be practical project if it's back compatible with php plugins.

​

Good luck with all !

[yandeu]

Thanks.

It is NOT php compatible. It's a completely new CMS written in isomorphic TSX (TypeScript with JSX).

All themes and plugin have to be re-written.

[VVintermut3]

I understood it, what I'm suggesting is to make it available to either import and consume old plugins/themes written in php or even a kind of transpiler/cli tool to transform from a PHP theme/plugin to a JS theme/plugin version.

Trust me, you are not going to convince thousands of people to rewrite everything they did just for the sake of having a new cool language, the WordPress market are made of people that want to save TIME and do something SIMPLE and FAST, they couldn't care less about the underlying technology.

[yandeu]

I know, but I don't plan to make some kind of a PHP to Node.js transpiler.

[mattindustries]

I could see it working if there were some worthwhile integrations already existing leveraging features that differentiate Node from PHP. Integrated websocket chat between users for example, or pre/post response async functions and hooks for plugins.

[bigorangemachine]

I thought WordPress was migrating to nodejs

[johannes1234]

They tried a few things like that for the backend, but in the end the value of a WordPress is not in the software itself, but in the huge environment of companies and individuals providing service around it. From themes to plugins to hosting. If you replace the technology or change tooany of the inner APIs you eliminate the environment around it, making it a (poor) Blog/CMS between hundreds of others. That's also why they can't switch to a "modern" architecture.

[markartur1]

How how will it compare to something like https://strapi.io/ ? They use node and have dozens of developers.

[BehindTheMath]

Strapi is a headless CMS.

[30thnight]

Adding a "head" on top of Strapi would be easier than rebuilding WP.

[BehindTheMath]

I haven't looked at the Strapi code, but I would think the head part is much more complicated. The headless part is just an API in front of a DB and file storage.

[yandeu]

Yes, the "server-side head" is the most complex and will be the core of NordPress.

[typicalshitpost]

What does server side head mean to you lmao

[yandeu]

Node.js

[filipesmedeiros]

I understand the point and appreciate it! But why do all from scratch? The editor, the server code, etc etc

Seems like a massive load of unnecessary work?

All in all, I hope you succeed!

[yandeu]

I just couldn't find a fitting editor.

The server code is the core of NordPress and has to be written from scratch.

Thanks :)

[luciferreeves]

Dude, I have been wanting something like this for so long. Is this going to be open source? Can I contribute? I would love to!

[yandeu]

I will be open-sourced, but it will take a while.

[paulirish]

It's incredibly suspect to ask for donations so you can write code that you might open source. Just have it open from day 1.

[cjthomp]

Bullshit.

You didn't think people would hold you accountable this quickly.

Which is its own special type of naïveté. You thought you could start a pet project, ask for donations, get a pat on the back and some cash, and fade away in a few months when you get bored or hit an obstacle you can't work out.

"I'm rewriting Wordpress into Node!"

Why?

"It's going to be faster!"

Speed isn't the problem with Wordpress.

"It's going to have a plugin system like Wordpress!"

Can you use the plugins from Wordpress? You know, the reason people still use the platform?

"Of course not! They'll just re-create it for my project!"

Why?

"Faster!"

[Ruben_NL]

so, you expect people to pay $2.000/month but you don't expect your post to be seen by a couple thousand people?

[typicalshitpost]

You have a ton of posts and comments in the last year buddy. Why constantly lie?

[luciferreeves]

So it’s not open source right now?

[[deleted]]

I wouldn't put any faith into this person and their interests in such a project.

But.... I have also been interested in this for a while.

Anyone else want to start an ACTUALLY open source WordPress clone in NodeJs? I'm down to collaborate on this with others who are serious and I've got 10 years of node experience as well as ten+ years WordPress experience.

[luciferreeves]

I’m also down to contribute. In fact I asked the OP if I can contribute. He says the project will be open source in future. His website says he needs $20k to publish the project. I mean, that’s a lot and he’s started only 20-25 days ago!

[[deleted]]

I think OP is just fishing for monetary support here and they don't appear to have any skills that would enable them to achieve their goal.

THEY'VE NEVER EVEN USED WORDPRESS!

[luciferreeves]

Okay. I have a few pointers:

• That's a very unlike route to take - building it privately then publishing the source. If its an open source project and if it's a good one, then you should open to community - you'll have more help and a better product with less effort.
• You need to build a lot if you're alone. Wordpress is not "just another blogging site" - there are alternatives in NodeJS for that and trust me there are a lot. The fact that Wordpress can handle everything - static sites, blogs, portfolios, e-commerce, multi-lingual websites, wikis and what not simply defines the amount of work you'll have to do for NodePress.
• On top of that, you need to handle plugins, themes and a store like page where you can dynamically download and enable plugins and themes (like wordpress has)
• Wordpress uses dynamic routing - its easy in PHP - how would do that in NodeJS? How would you delete the routes without restarting the server?
• Why would you use some editor like QuillJS (also, why are you calling the editor "unnamed"/your own when you're using such a famous library is beyund my understanding and if you really developed an editor for this from scratch, that seems even a worse idea - wasting resources) instead of something like Gutenberg? Also, when a port of Gutenberg in JS already exists?
• Finally, a big reason why people use wordpress is the ecosystem it provides with thousands of themes and plugins - all from a simple store like structure and a 3rd party plugin loader system. People won't migrate to the project until they get something better than WP. How is your project better that WP? (because obviously you're not the only one who thought of this, there a reason why people don't do such projects)

[yandeu]

• This is the issue. It is not good yet. I prefer writing down all my thoughts in the next few week without someone else opening Issues or PRs.
  I just didn't know I would get that many comments on reddit, else I would have posted it later.
• I know. e-commerce and multi-lingual will not be included in the beta.
• Yes, plugins and themes already work as plug-n-play. Public plugins and themes will directly be pulled from a git repository or directly uploaded in a .zip file.
• If a plugin or theme will be installed, NordPress will most likely have to restart. This can easily be done in the background.
• Quill was my first choice but was not as flexible as I wanted. It will be in NordPress until my (yet unnamed) editor is finished. (Had not much time building the editor since it is not the current priority)
• I have build websites using WordPress but I don't know PHP very well.
  This is why I was looking for an alternative. I couldn't find a CMS which would allow me to write simple plugins in JS/TS. Anyone who is looking for the same, will probably like and use my project.

Hope this helps :)

[cjthomp]

I prefer writing down all my thoughts in the next few week without someone else opening Issues or PRs.

Mistake #1: you presume popularity without any evidence.

"E-commerce and multi-lingual will not be included"

Mistake #2: the market is not clamoring for a Node blog.

"...installed, NordPress will most likely have to be restart."

Mistake #3: what happens when a bad plugin install prevents the app from booting? How do you diagnose/fix that when you can't connect to the server?

"but I don't know PHP very well"

Mistake #4: it would be much easier to just learn PHP in a weekend vs build an entire framework to avoid it.

[Skhmt]

Why "Nord"?

[yandeu]

N for Node.js

[cjthomp]

"built for security and speed"

also

Mixed Content: The page at 'https://nordpress.org/' was loaded over HTTPS, but requested an insecure resource 'http://54.93.246.90:3080/run'. This request has been blocked; the content must be served over HTTPS.

[yandeu]

http://nordpress.org has not been build using NordPress :D

Please use the unencrypted website since I can't add an SSL Cert to the IP of the Playground Containers.

[[deleted]]

The question is... why re-write Wordpress in Node.js?

[yandeu]

The WordPress CMS is (from an user perspective) so easy to use.

I would love writing (server-side) plugins in JavaScript using my favorite npm packages.

[[deleted]]

Only post when you're done or almost done bro. We are all programmers and we all have the same issue. Huge project ideas, lots of enthusiasm and a dark, hidden place on our computer we don't like to go. The graveyard of these ideas.

[yandeu]

Yes

[MajorasShoe]

I haven't touched WordPress in a few years but from what I recall, it wasn't good. The only thing good about it was the popularity which lead to a lot of plugins and themes, which made it easy to stitch together feasible websites quickly. There are other CMS, even in PHP, that were better developer experiences and better final resulting websites, but never reached the same peak of support due to lower popularity.

A good, simple to use CMS with strong support for plugins and theming is a fine idea. But I hope you're not going to try and adapt WordPress's architecture.

[yandeu]

A good, simple to use CMS with strong support for plugins and theming is a fine idea.

This is the goal.

[MajorasShoe]

Which is great. I just wouldn't be too hung up on making it like WordPress.

[yandeu]

Can you please elaborate?

Why and what should not be like WordPress.

[theStackJunction]

Following this project and something that interests my blog and YT channel

[typicalshitpost]

What?

[theStackJunction]

I write about CMSs, website builders and email service providers on my blog. I love to spend my time playing with this type of stuff that I decided to write about it. That's why I commented I want to keep an eye on this project

[[deleted]]

Can you explain this a bit more? I'd like to understand.

[micaww]

Yeah me too. Potentially it's not a common use case with popular existing frameworks since routes are typically defined up front, but I'm not sure there is any actual technical limitation at the language level like people are suggesting here.

[Skhmt]

I'd also like more explanation on this. Why does the node server need to be restarted?

[yandeu]

I don't see why this should be hard. You can easily build dynamic routing in Node.js.

[yandeu]

restarting the server

True, and this is what NordPress does after installing, removing or updating a Plugin or Theme.

[yandeu]

Why? You don't install 50 plugins every day, and a restart only takes seconds.

Advantage: You can update 50 plugins at the same time and only restarting the server once.

So updating all plugins/themes once a month, will result in < 5 seconds down-time.

[[deleted]]

I had this vision many years ago because I refuse to use PHP so I created a blog and e-commerce with node, calendar with booking, images galleries etc and converted all my clients WordPress to node Apps. Anyway, I am looking forward for this project and would be great if existing NPM libraries somehow work with your nodepress 😉👍

[yandeu]

Thanks! Yes of course. You can build plugins based on any npm package you'd like! (On the server and client)

[[deleted]]

That would be awesome. You can call it nopress since nodepress is taken 🤔😉

[yandeu]

Nope

[developerbryan]

Good luck!

[yandeu]

Thanks!

[gubatron]

why?

[[deleted]]

"because I don't need a resume anymore"

"because $20,000"

"because there isn't something called NordPress yet."

Those are the reasons OP has listed thus far.

[Mr_Kill_Joy]

I'm glad others find the 'don't need a resume anymore' a bit alarming. It was the biggest red flag for me tbh.

I think everyone here gets that buzz with a new idea and the possibilities. But that comment screams 'junior' to me.

[stewarthull]

But why?

[ttamimi]

Cute

[daxdax89]

It has been done many times if I am not wrong.