JVS.GURU AF_EATSv5 is the v5.2020 implementation of the EATS framework from Architected Futures. It may barf itself up a few times before we fully get started. For me, it will be Annie, or Annie I, depending on how the successor … Continue reading
I’ve gone back and forth on this for a while now, but from a practical basis I’ve made a decision. Not that I haven’t made this same decision multiple times in the past months, and each time in a different direction. But I’ve found myself spending almost all my time in one camp for the last few months as I pursue architectedfutures.NET, and I find my intention is to stay in that camp unless something significant proves unworkable. In my way of thinking, that’s worth logging as a decision.
I’ve been holding back from declaring a ‘final’ choice in this evaluation because I was still waffling, I wanted to make an informed decision and I wanted my decision to ‘settle.’ Now, after having spent some time working with both WordPress and Drupal, building prototypes and testing various versions of what I want to do with architectedfutures.NET using both systems, I’ve decided to spend my efforts going forward working exclusively with Continue reading
One of the problems with life is dealing with change. Nothing is static. Everything is constantly changing. While that has always been true, the pace of change has accelerated in modern times. The volume of changes that seem to have some impact on us has gone up, and the awareness of change has intensified. We are constantly told that newer and better stuff is now available, to replace the stuff we just bought yesterday, which we may not have had a chance to use yet. We live in an era where we now measure things in internet time. Stability and constancy are old-fashioned virtues. This is a hallmark of technology and is particularly true when dealing with computers and software. Open source software is no exception; in fact, quite the opposite is true. Drupal and WordPress have different schemes for how they drive change into their user communities and offer different facilities to their users to comprehend and administration change. These differences are not inconsequential. Continue reading
Today I found a great resource documenting Functional Requirements for Community-Oriented Software and Technologies. Continue reading
In my journey to create architectedfutures.net, one of the things I’m dealing with is a platform infrastructure choice. My current focus is an investigation of Drupal and WordPress. I haven’t chosen between them yet, and I believe either could do a good job for 80 percent of what I want to do, but there are definite differences in the way the job would get done, and, in the end, what gets done. So I’m digging in further, doing additional experimentation, and even toying with some concepts where I might use both. I often go back to basics, core principles, to help clarify my thinking in this process and ask myself: “What is the goal? What are you trying to do? Which is the better approach to getting there?” This post is a reflection in that vein. This post is also trying to document some history for those who are interested in following, or joining, my journey.
One of the early questions I had about how BuddyPress and WordPress are integrated was: “How do the user profiles for site members correspond?” I’m not familiar with the history of the two products, but BuddyPress is implemented as a plugin component within a WordPress environment. To access BuddyPress you login to a WordPress site through a WordPress login. Creating a BuddyPress user requires that user’s profile to be set up as a WordPress user. On examination, some of the profile information established for a site member is the same and can be synchronized between the two facilities when changes are made; yet other information is different. In fact, the potential exists to have the same type of information about the same party defined by the same labels but containing different details in each area of the combined system. This didn’t seem ideal. My first thought was that I was doing something wrong in my site setup. When I asked for profile synchronization to occur as a feature on a BuddyPress administration panel, I expected full synchronization. As it turns out, my expectations were out-of-scope. Continue reading
Welcome to ArchitectedFutures.info. I hope you find the site helpful and become motivated to return to track my progress and/or make use of the content I’m providing. The purpose of the site is to create a form of breadcrumb trail in my efforts to build a larger, more complex site using either Drupal or WordPress/BuddyPress technology. As I go about the task of building that other site, I’ve decided to document some of my discoveries about these technologies and my efforts on this blog. I hope the material will be useful to others. Continue reading