Content and more

Content? Yes, would not all of us like to be such?

But, the web works against that blissful state, for various reasons, which will be a continuing theme for this blog (metaphors abound).

In the meantime, we have to consider the management of our information, called content, both on the web and not. Which of those is of a larger size? Some, no doubt, would argue for the former; such are the was of the e-literate.

However, in truth, non-web'd (where web encompasses a whole lot, including those "cloudish" things that are so appealing) is the larger; showing this is one of our tasks.

---

Decisions made a couple of years ago resulted in a serious of learning experiences which helped the blogger update his world view. You see, he has been web-izing since its beginning (and, before). Too, he has watched the various newcomers appear, like waves in the ocean. At any point, some of these make a splash (make someone a bunch of money).

Yet, none have really been enough to bring contentment. Until now which we'll go into below. First, though, let's recap.

• The precipitating event as the need to move a website (associated with the TGS) because of Office Live going away. Several people had built processes upon this freebie offered by Microsoft. Having that basis jarred was interesting (several posts). 
• After casting about for some alternative, the site was moved to a hosting facility. However, it was done in a mode that is late 1990s in flavor. Why? Fall back position (important lesson learned long ago while dealing with large, complicated systems). There was some attention paid to tools (this old timer has all sorts of opinions on the matter). Yet, none were attractive (Sea Monkey's Composer felt good, for the time). 
• Later, I started to look at CMS approaches. That took several iterations to get the proper feel. 
• None really clicked. For one thing, databases are overused (we'll go on about that, folks, time and again - any young one listening?). Too, a lot of effort is put into the titillation requirements that seem to be implicit. So, I continued with my static approach. 
• Then, I gave CMS another chance and did a couple of examples. One of these has been used for a What's New for a few months. 
• Of late, I have gotten back to code, thanks to Codecademy (code is a right, rather than being a privilege - yes, I want to know what crap comes down to my browser). During the past sixty days, I have played with several environments. Python still looks good (albeit server related), but I'm not making a decision about the language, yet. Using several languages may be the necessity (due to contextual imperatives).

Today, I took another look at WordPress and was impressed (see showcase examples). So, within the next few days, I will try it again within the context of TGS content and will get back with the specifics. 

Remarks:   Modified: 01/21/2019

04/25/2014 -- Oh yes, Internet shock. The Office Live fallout pales in comparison but is analogous enough for us to use as an example.

08/02/2014 -- Bit the bullet and updated the site (looks, behavior) using HTML/CSS. Of course, things are still pending, such as membership functions, business, ... We'll get there.

05/31/2016 -- Continuation of the theme.

01/21/2019 -- If you look at Content Management or CMS at this blog and the one for the Thomas Gardner Society, Inc. (CMS or Configuration), you will see lots of posts. We have a new site where we prove our work: TGSoc.org. Its role is portal but, for now, we introduce changes there, first. See the Discussion page with a link to our devlog. Based upon the direction I hear that Google is going, working this approach for our portal is right on. So, technical will be visible rather than not.