Before proceeding with publishing revised code, I’m hoping to clean up and reorganize the site this quarter. This will involve not only archiving older documents, code and posts, but also developing a strategy for building a repository of loosely-coupled, service-oriented components.
While I have looked into and could have tried various packaged web-application frameworks, I have not really been keen on features that mostly hide HTML and SQL coding to reduce programming at the expense of future flexibility and interoperability. For example, if I wanted to borrow or share components with others, I would prefer not being forced to install a whole framework package in order to do so. In other words, I would like to be able to cherry pick those tools that do not embed customized nomenclature and method calls in a project’s source code.