2

Do y’all build your own CMS?

Comments
  • 6
    do you vulcanise your own car tyres?
  • 0
    Do you invent your own programming language?
  • 2
    Do you make your own condoms?
  • 0
    @Frederick at least it isn't bicycle... oh wait, gymnasium... kinda has bicycle vibes.
  • 0
  • 0
    We use jhipster on couchbase. What do you guys use?
  • 2
    @hack lasers stimulating trained butterflies flapping wings to direct cosmic rays to flip the bytes of an SSD
  • 3
    Yes.
    CMS’s are pretty straightforward.
  • 0
    @netikras maybe.. just to be sure!!
  • 0
    @tosensei that’s for folks with muscle
  • 0
    @AnxiousADHDGuy i tried once, didn’t end well sadly
  • 0
    @Frederick cos I’m high?
  • 0
    @zlice … but Java isn’t a database
  • 0
    @hack We love to build from scratch
  • 0
    @gymnasium stop doing cheap drugs
  • 1
    @AnxiousADHDGuy I should have clarified, high on code… not codeine
  • 0
    @Root How would you build one today?
  • 0
    My last small project involved that. Its abandoned now.i stopped it before feature creep took over.
    it was just an example i anted to make with my own framework, which had some nice things starting with database pooling, orderly shutdown abilities, the ability to serve multiple sockets, domain aware routing, saml authentication and an menu system with the ability to hide entries if they aren't needed (login button only to unauthenticated, logout to authenticated).
  • 1
    Yerp, CRUD is CRUD, just be sure to protect the D if you spin your own.

    Anything with a DB behind it, is the same as anything else with a DB behind it. It's just how you get to that DB that seems to have changed over the years.
  • 1
    I normally don't build my own CMS. But when i need any content to be manageable, i do.
  • 0
    @gymnasium It's simple crud with a few fancy features like tagging, and some nice index/show pages.

    Everything a CMS does is an extension of this.
  • 0
    We did in 2007, and it was decoupled from the beginning: the backend was separate from the front end. But maintaining it was a PITA because the developer and sysadmin left without any documentation. The pages are dynamically generated using XML files and all the XML files reside in a single folder. The number of files have grown to 500k. Worse, the XML files are copied from the backend using rsync to several headless PHP servers. The sysadmin I replaced didn't even bother adding a timeout option so for several months, the load average would go up and the only thing they did to resolve that was to restart the server.

    Then I had the bright idea of replacing it with WordPress.
  • 1
    @Root devil woman
  • 1
    @AleCx04 and proud!
  • 0
Add Comment