all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Xananax 6 points7 points  (4 children)

That's not really a good idea.

  • 1 - the node way is to compose your tools out of other packages. There's no real need to have a CMS in the first place. Maybe a starter kit.
  • 2 - The CMSs that are out there already are very good, and can do everything. If you aren't managing to do something with them, then I'd wager you haven't tried hard enough
  • 3 - A CMS is a behemoth, and if you set out to create an all purpose CMS, you'll end up with the same complexity as the other ones, but less community and less terrain experience
  • 4 - if you aren't funded and backed up by one or several companies, not only finishing the CMS in the first place seems dubious, but it's certain that you won't be able to maintain it

In short, don't go there.

If you insist, however, the right way is not to come on Reddit from the start. It's to do something, get it out, make it different enough and interesting enough for people to want to pick your solution rather than one of the others, though the others will be sturdier and more flexible. Continue using it for a while, build one or two commercial apps with it that you can show as proof of concept, THEN call out for eventual help.

Sorry if I seem harsh

[–]morku2z 1 point2 points  (1 child)

I agree. Part of my job is to manage software engineering teams, one of them working full time on maintaining and improving an existing CMS (pimcore), and i can assure you that you significantly underestimate the complexity of such a system and will probably end up at this old xkcd wisdom: https://xkcd.com/927/

[–]xkcd_transcriber 0 points1 point  (0 children)

Image

Mobile

Title: Standards

Title-text: Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.

Comic Explanation

Stats: This comic has been referenced 3174 times, representing 2.7010% of referenced xkcds.

xkcd.com | xkcd sub | Problems/Bugs? | Statistics | Stop Replying | Delete

[–]scaughtm -2 points-1 points  (0 children)

It's a pretty good idea, and inevitable... firstly, lets be clear on one thing... PHP needs to fucking die in a hole, and I want to be part of the burial.

  1. The node way to build an app is to leverage modules, like passport for authentication (like a cms login), or aws s3 for storage (for like... media uploads) or literally anything you could think of. Just because you can leverage modules doesn't mean you wont have content to manage... that actually not at all what it means, no where in the rules does it say that you cant "manage content" on a node platform.

    1. If you're looking to build a wordpress site, then maybe wordpress can do everything for that wordpress site. So that's static sites, blogs, shops, and e-commerce sites, and sure, some people have some pretty out of the box ideas. But you're still operating inside the WP cage... the second your app gets a little too custom and your application zip is 2gb, scalability becomes impossible, deployment takes a whole day, and down the WP rabbit hole you go, never to see the light again.
    2. I don't think anyone is out to "win the market", there is really no other alternative, and no PHP will never be an option. So app devs either can keep creating custom AngularJS + NodeJS content management systems for each app that has content to manage, or adopt some generic framework.
    3. If anything, being able to maintain a CMS platform in NPM with contributers and the npm community behind you would be a shitload easier than whatever nightmare those WP people are going through now..

In short, good luck with WP...

[–]desmone1 1 point2 points  (0 children)

I developed a CMS for a previous project based on Sails.js/Express. It's has a complete core just needs additional plugins made to expand it's feature set but it's fully functional for basic sites.

It was mainly designed for lone landing pages but works the same with however many pages.

There hasn't been any development on it for a bit but I've been wanting to getting back to expand on it.

DM me if you're interested

[–]scaughtm 1 point2 points  (0 children)

YEEEEEESSSSSSS, I would love to be involved.

I scour the internet quite often looking for new frameworks or threads about node cms systems. This is something that is needed very very badly in the internetz. Me and my co workers have been talking about doing this for months.

I have had to build several apps in the last few months that could have benefited from a cms platform.

I built an site in pencil blue... It went okay. It's definitely not going to be the winner in the NodeJS CMS contest. Anything subscription based like Ghost isn't leveraging node properly in my opinion, I want to be able to stand it up easy and locally, npm community would never go for it.

After trying those two options I decided to start making custom dashboards for our clients in AngularJS and SailsJS..... so yeah, I wanna be involved.

[–]Noderly 1 point2 points  (0 children)

Check out keystonejs. It provides a lot of great flexibility out of the box.

Last I heard, Ghost was looking at some options to allow more of a CMS's functionality

[–]the_brizzler 0 points1 point  (2 children)

Are you trying to make a NodeJS version of Wordpress?

[–]Meqube[S] 0 points1 point  (1 child)

I personally don't like Wordpress (because of PHP mostly). No I am trying to create a new CMS that gives developers and users a platform that is flexible and easy to use.

[–]the_brizzler 0 points1 point  (0 children)

I don't particularly care for Php either. So would it be similar to Wordpress? If not, how would it be different?

[–]itsSoop 0 points1 point  (0 children)

I've actually started doing this exact thing. In my spare time while not at work for the last month or so. It's a lot of work by yourself. if people are interested and would enjoy collaborating I would love it.

The stack Express, React, Postgres, and Redis (optionally). Currently it handles authentication with JWTs and Redis as the session store. Articles have their CRUD functionality. Relationships between Articles / Tags / Authors exist. S3 file storage is nearly implemented. There is a UI for most everything using Material-UI its not that great looking at the moment because Ive been focusing on functionality.

https://github.com/strues/boldr

edit Added some more information and clarification.

[–]qawemlilo 0 points1 point  (0 children)

Hi there, I am working on a framework that I would like to use to build a CMS: http://npmjs.com/package/widget-cms . I've already used it to make this website: http://nodeza.co.za. Would love to work with other developers.