CMS, a favorite subject

TL;DR -- We started with MicroSoft and were happy, but they pushed people off of OfficeLive in order to get Office 360 in place. So, we did the right thing and limped along with a hacked out static mode in order for not let publishing get in the way of acquiring knowledge (the old fashion way, not machine learning - heavens forbid). The next motive for change came with the decision that Google would require some semblance of mobile friendliness to play in their part of the universe. Okay. After that, we did a website for a group that got us looking at alternatives. Then, things were fairly low-level looking to require lots of plug-ins (with regular costs accumulations). So, we just hacked more functions using javascript. When we started our portal, we had another chance at change. So, we had intermittent opportunities to consider CMS over our time. Now, we're at it again. The difference? The mobile environment has matured enough to be really interesting. Technology choices and issues abound; truth engineering is even more imperative; and notions, such as what was old is new again, apply. We'll stay at this until we get a resolution which will found the future work. Too, stay tuned; there is no limit to the ways that someone can contribute technically. We might just be the perfect lab for spawning lots of ways and means for considering how to attain some type of sustainable future. 

---

This post is technical in content, with enough of the 'meta' (proper usage) issues covered to cover the extent of the current dilemmas. For now, we will have a list which is unordered and which will be extended throughout this iteration. We have touched upon the subject a few times, even recently mentioning that it's time to open the Pandora's box, again. As well as having the technical focus which will include the posts from our Technology Blog (hosted via WordPress on our site (TGSoc.org) that is presented via webhostinghub), we will look at motivation and talk the huge issue of managing across the levels related to development and deployment. The top level? We call it content, so CMS, to us, means Content Management System. One might stress the top down aspect of this. That is, the Thomas Gardner Society, Inc. has a focus of the Cape Ann start of the American experience where we look across 400 years in terms of history, family dynamics, genealogy, and cultural issues, such as science. The overarching view is called 'truth engineering' which will show that AIn't is the reality unless some serious changes to the assumptions occur, thereby telling us that we need to lift to public awareness just how the marvels come to be that are associated with computing. 

Some might use 'configuration' which emphasizes the technical aspect due to the decisions required at that set of levels which are many. At the basic level will be the hardware, but it is supported by science and engineering. Software? In the list below, look at the Periodic Table of WordPress plugins. That refers to one set of frameworks (which can be generalized) pertaining to one offering on the market, albeit a popular one. 

Aside, one national group of interest uses WordPress at level of one of the States involved, whereas the overarching scope is handled by Drupal. Of note? We looked at Drupal back in 2012 (see notes with regard to this) as well as WordPress and a few others. Our choice was to fall back to a custom approach which turns out to be useful with respect to steps to the future. As one lecturer noted, what's old is new again.  

For now, consider the uses of 'C' interchangeable since we are using TGSoc.org to demonstrate issues, as well, from the bottom up (Wikipedia - Content Management (notice web content management and knowledge management); Configuration Management (notice the use for software). 

Motivation (see Summary discussion): Provide modes for managing a nonprofit in a cost effective manner while supporting the operational needs that go along with such a focus. At the same time, provide a full suite of media approaches to presenting information that has been curated, manually. Albeit, types of machine learning may be applied but with any use being noted explicitly. Meaning, of course, no implicit uses that can confuse. ...

• CMS posts in our content blog 
• CMS posts in our technical blog 
•  
•  
• Content management posts in our content blog
• Content management posts in our technical blog 
•  
•  
• Static web page - our approach which basically hacked HTML and which was chosen to allow progress with presenting information while we came up to speed on the related domains (events, names, dates, ...), covered over 400 years of history, published on a regular basis, and extended our focus/scope as we proceeded. Efficacy was attained by using several editors (HTML, simple text, and publishing). 
• Dynamic web page - initial thrust of mobile support plus curated indexing accomplished, mainly via CSS and Javascript using only simple text editing with Chrome testing support. 
•  
•  
• Model-view-controller - traditional approach for supporting the user via the web browser 
• Decoupled Architecture and WordPress - some history, pros and cons. There may be a better video put into place, however the basics are covered sufficiently. Suggestion, scan through this quickly without the sound on. 
• TodoMVC - examples, demonstrating some of the confusing notions that will be tamed
• Periodic Table of WordPress plugins - again, demonstrating the variety (most coming with an initial and a scheduled cost
•  
• Decisions - Pros and Cons of Decoupled Headless Websites;  The Pros and Cons of a Headless CMS; ...
• Deep Dive into Headless CMS Back-End Options - comparative look at what's available (Feb 2021)\=
•   
•  
•  Initial WordPress - picked from Top 15+ tutorials 
•  Business manager - for WordPress 
•  
•  

To us, content and configuration denote two heads or two hats for one head. The reality is that there are content issues that do not need to consider configuration issues. The inverse is true, too. Now, the overlap? It's more than semantics, though we will use CMS for both views because those playing the different roles may be on the same team (or the same person, such as yours truly). 

A better metaphor might be the floor where we have an above and a below where there is an almost impenetrable barrier. Sometimes, one uses silos which are monoliths that isolate. Many times, isolation is good (philosophical notion); actually, partitioning by classes is an example of many. 

You know, we haven't paid attention until this year, but RootsTech 2022 is coming up. This graphic shows the many approaches that have been developed. There has been some effort at establishing a commonality. To us, this means more content management than the other, except where standards might be under discussion. Don't know, yet, but will be paying attention. 

Remarks: Modified 02/25/2022

02/25/2022 --