Recently in sites Category

[update 2010-09-02T20:07Z I added the category and tidied up the table a little bit.  I am also noticing the many ways that Windows Live Writer fails to handle editing of more-intricate [X]HTML content.  After all of this time in the history of HTML editors, I am not clear what is so difficult about this, apart from misplaced NIH ego-foo.]

I have 20 domain names all to be hosted at nfoCentrale.  The sites category provides subcategories on their individual development and status.

There are also two retired domain names.  I’ve commented on the demise of InfoNuovo already.  Until I sat down to create this list and check on all of the current leases, I had forgotten about the never-used  It keeps company in the list of retirees, below.



DMA: The Document Management Alliance Specification DMA

AIIM’s Document Management Interoperability Exchange DMware

eoWare: Applicative Language Development eoWare

Millennia Antica Pottery millennia-antica

The Miser Project miser

nfoCentrale: The Anchor Site


nfoWare: Digital Information Processing Technology nfoWare





nfoWorks: Tools for Document Interoperability nfoWorks

NuovoDoc: Design for Document System Interoperability NuovoDoc

ODMA: Open Document Management API Interoperability Exchange ODMA

Orcmid’s Lair orcmid



TROST: Open-System Trustworthiness trost

[reserved] worthiness


InfoNuovo InfoNuovo

In preparing for the Centrale Retirees I learned that when there are duplicate sub-category names, as with Centrale/{retired} and sites/{retired}, posting via Windows Live Writer will publish to both {retired} sub categories no matter which branch I select it from.  To repair that, I avoided duplication by having Centrale/{retired} and sites/{retirees}.

I renamed the sites sub-category but retained the status/sites/retired-1 location.  By republishing the site, the duplication disappeared, which is useful to know.  This was all done with the Movable Type administrative interface via my browser, so that I had the necessary fine control to eliminate the duplication.

Although the site/{retirees} category has the same function as that explained for Centrale/{retired}, there probably won’t be so much retirement going on.  Still, if some site becomes completely stabilized and no further posting is expected, it will be useful to freeze its status.  Whether I move it to emeritus status here in the {retiree} category or not remains to be seen.

The subcategories under centrale and sites have been expanded extensively.

The expansion serves two purposes:

    1. The subcategories that I will be needing for a while will have their folders created on the site for backup and maintenance.  They provide places to link to.  They provide places for status about all components of nfoCentrale, including previous components that are now retired.
    2. I can capture historical information about the development of what is now nfoCentrale, by category.

To prevent the categories from being too cluttered in the long run, information about retired nfoCentrale components will eventually be removed from active categories but will remain reachable from the {retired} subcategories under centrale and sites.

The nfoCentrale site is not a web site in the usual way.  It is the anchor site on which all of the other sites I operate are situated.  It is in that way that I speak of those sites as being nfoCentrale sites.

The other sites are maintained as folders within the actual nfoCentrale site.  The anchored sites have their own domain names and they behave as independent sites.  But they are managed as in a single account of an Apache Web Server.  That account has the top level be reached via the nfoCentrale link:

Until now it has been unimportant that the other sites,,, etc., are implemented as folders in a single web hosting server account that is all of nfoCentrale even though they have their own domain names for their portions of the site. 

If you nose around nfoCentrale, you'll see that the anchor level of the site has been neglected, consisting of many poorly-connected pages that have been borrowed from other of my sites to serve as placeholders.  I was more attentive to the individual anchored web sites and not so much the part that is infrastructure to the others.  That must change.

Now that I am adding software, especially Movable Type, to my web-server account, the organization and maintenance of the anchor becomes more important: It is at the anchor level that the additional software operates.  

This has led to my introduction of a repaving project at nfoCentrale itself.  I also introduced my first Movable Type blog, this one, under nfoCentrale.  

The repaving accomplishes three purposes:

    1. The nfoCentrale site becomes an useful part of the complex as a repository of information that applies to the overall complex.
    2. The ad hoc techniques for developing, deploying, and backing-up content, including the blogs, are transformed to consistent, systematic practices that I can handle easily and reliably.
    3. It helps confirm that what I provide to manage and organize the sites does not interfere with Movable Type operation. 

This post serves point (3) by ensuring that recent updates have not disturbed the way Movable Type accesses the material it uses at the anchor level.

Once I am satisfied that little bit done to integrate Movable Type into my now-refined nfoCentrale Web Development and Deployment Model, I will take the next step: confirming that I can create a replacement for one of the blogs in an anchored nfoCentrale domain by using the same Movable Type installation.   The guinea pig for this wil be Spanner Wingnut's Muddleware Lab, part of

This is the first nfoCentrale status post since I upgraded the nfoCentrale site and the supporting deployment model in the last few days.  It's success will confirm that I have not broken anything badly, so far. 


Reblog this post [with Zemanta]

About this Archive

This page is an archive of recent entries in the sites category.

ecostructure is the previous category.

strumenti is the next category.

Find recent content on the main index or look in the archives to find all content.


OpenID accepted here Learn more about OpenID
Powered by Movable Type 4.34-en