> On Aug 11, 2022, at 5:30 AM, Laura Smith <n5d9xq3ti233xiyif2vp@xxxxxxxxxxxxx> wrote: > > > > > > > Sent with Proton Mail secure email. > > ------- Original Message ------- > On Thursday, August 11th, 2022 at 13:11, Ray O'Donnell <ray@xxxxxxxxxxxx> wrote: > > >> On 11/08/2022 11:00, Laura Smith wrote: >> >>> Hi Tony >>> >>> The reason I'm looking to do it from scratch is that its a case of >>> "once bitten, twice shy". >>> >>> This CMS will be replacing a Joomla based CMS. >>> >>> I can't quite say I'm enamoured by the option of trading one "baggage >>> included" opinionated CMS for another. Also in this day and age, >>> removing the excess baggage means an improved security footprint. >> >> >> I would second what Tony Shelver said - it sounds as if what you're >> trying to do has already been done, and for the most part done well. I'd >> recommend Drupal, which works well with PostgreSQL, and which is very >> extensible and customisable. >> >> I'd agree with you that removing baggage can mean improved security - >> on the other hand, having a huge, security-conscious community behind an >> open-source project gets you there too. >> >> Ray. >> > > Tony's suggestion also needed Node.js, and frankly I'm not even going to open that can of worms. > > At this point I'm not interested in "very extensible and customisable". Joomla fills those words too, and my present installation is full of all sorts of third-party extensions ... the thought of all the security vulnerabilities scares the bejeezus out of me ! > > Hence I want to get rid of bells, whistles and baggage. Forget the fancy GUI, forget the "community" of random plugins. > > I just want a solid Postgres, which exposes to the outside world via a limited number of Pl/pgsql functions. The frontend can then pull the data and render it into a template. > > I know I probably sound nuts. But as I said, I've spent too long in the hell of Joomla. I don't want to replace it with another thing that tries to be all things to all people ... I just want to follow the KISS principle now. > > I once worked a company which produce reference text for radiologist. The content was generated from an in-house app which wrote a form of mark up xml and store in postgres (version 8,9 no json). That was hard copy though (but beautiful). I would like to better understand your concept of “page”. I’m not following how you’re managing layout and how variable that is in your world. I would suggest getting as many of the things like page name (foo) and description(bar) as possible out of the json. How many tags (eg pageHeader, pageMainLeft) do you have? Do queries ask for pages with pageMainLeft having some string value within their content? Will you index the content separately? Pictures as content?
