![]() ![]() Around 2010 I implemented my own version of PhpGedView with family trees for Webb, Britt, McCain & Iredale families. We learned some good insights, but ultimately didn't get too far.Ībout ten years later, I wanted to take my Webb family tree information that I had gathered with the help of a few relatives and create a collaborative genealogy environment, with all the types of content I envisioned, though in more of a genealogy format. I built that first prototype with my brother, using ColdFusion Markup Language and the Fusebox Application Framework. I was so excited and took it as an omen I should give it a try. I had gone to a Macromedia ColdFusion workshop and won a give-away copy of ColdFusion. Separately, the journey to build GreatAlbum started in 2001, when I tried my first attempt at building a prototype. Thus began my journey with Drupal that has now spanned nearly 15 years and almost as many websites - typically as charitable hobbies for nonprofit organizations. While I recognized that it wasn't quite as widespread as WordPress, and more complicated to learn, I liked that it seemed to have the most robust capabilities of the three. I spent a week researching open source content management systems, narrowed it down to the top three - WordPress, Drupal and Joomla!, and ultimately decided upon Drupal - I think version 4.6 at the time. edu email address), so that wasn't an option. Keep in mind, this was only two years after Facebook had launched, and a few months before it was available to the general public (not requiring a. As you know, this world is evolving very quickly.When I joined the Reunion Organizing Committee for my high school class, for our 20th reunion in 2006, I thought it would be cool to organize it on a website. ![]() Mobile access - can only be truly effective when the code has been properly structured with CSS as the driver for presentation, and when the site design goals have been implemented.ĭoes this help? We don't have a precise pathway mapped since much depends on the development of the supporting programs and their requirements and our ability to initiate changes based on adoption of newly-enhanced software.Site design - new menu system and changes to theme development, perhaps more along the line of Wordpress, although that is not the model.This would allow admin/users to create their own templates and contribute them to the project on many facts/events. Template construction for a revised GEDfact Assistant (includes the Census Assistant).There are tons of little side projects, many driven by NFR, but they include: This is a huge and difficult task and it will be some substantial time before we are able to implement the code to achieve this goal. As has been well noted elsewhere, our intentions are to allow GEDCOM (traditional family tree) import and export, but once within webtrees that structure would cease to be used. Doing so would add tremendous improvement in managing and displaying large amounts of data (lots of INDIs, FAMs, SOURs, and media elements) in lists and on pages presented by webtrees. Longterm, we wish to abandon the GEDCOM standard as the framework for management of the data. ![]() ![]() These requirements are a major factor in our ability to proceed on this portion of the project as well as others, including PLAC in history management. This would be made easier if we required PHP 5.3 (preferred v5.4) and MySQL 5.5. This includes preparing the code for HTML5.Īdditional goals include a complete rewrite of the now, at best sporadic and troublesome, media management. The second effort was to clean up presentation via interface improvements and move many hard-coded portions from the base code into CSS for display manipulation. To some extent, this has been covered in other places.Īt this time, the first effort (close to complete) was to port the PGV code and change the product to an entirely database driven project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |