admin1 - Sun, 2010-09-19 12:25
If you have read the last two pages you might be thinking "enough!" I have my inventory, I have my strategy, now another inventory? You're kidding. And what does the planner have to do with this, whatever "this" is?
"This" is simply a list of your development strategies so that you can plan when to implement each strategy in the development process. The inventory also allows you to distribute the development effort across the development team. So bottom line, "this" will help you identify
admin1 - Mon, 2010-09-06 15:30
Assuming you have read the previous page Create a Feature Development Inventory and you are a builder or developer, maybe you are motivated to review all the requirements first before diving into building a site. Let's assume this is the case and consider creating some development strategies. But before we do, what does a Drupal planner need to know about this? The planner needs to be ready to provide feedback and clarification. Read on to see what I mean.
admin1 - Fri, 2010-08-06 09:41
When you were planning your content, one thing you may have decided was to maintain copies of nodes as they were changed - tracking revisions is a common way to refer to it. Keeping and tracking revisions allows you to return a node to its previous state when someone on your team accidently changed the text to something you didn't want. Why not apply this same strategy to web development. Track the changes made to your site so you can back out changes that don't work.
Planning Version Control
There are several ways to manage version control.
admin1 - Fri, 2010-08-06 09:39
If you need custom coding, where will code be developed? Where will code (core, contributed, and custom) be assembled? Where will code testing occur? Where will user testing occur? Where will the initial content loaded? In contrast to development, where will the live (i.e., production) site be hosted? "Where" is defined by both the physical box (web server) and it's domain.
admin1 - Thu, 2010-08-05 20:58
Part of the development phase includes deciding where the development work will be performed and where the public site will be hosted.
admin1 - Thu, 2010-08-05 14:29
In order to illustrate the inventory concept and its value, let me start with a scenario that most (if not all) of us can relate.
admin1 - Thu, 2010-08-05 11:52
A planner is not necessarily a builder, themer, developer, or coder. A planner isn't always the project manager either. So, what does a planner need to know to support development?
If we assume that the role of planner has been instrumental in gathering requirements for and defining the design of the site, then we can assume the planner is the person who has a complete understanding of what needs to be developed. Or at least has access to those who can clarify the requirements and design if questions come up.
admin1 - Thu, 2010-08-05 10:49
As we move into the next phase of the site life-cycle, we are face again with the question "Where do I start?" And, once again the answer depends on your situation.
Below are processes associated with developing a site.
Given the following processes, when do you do each?
admin1 - Fri, 2010-07-02 07:30
Now that you have the front-end of your site designed, you need to consider what it takes to actually sustain it. Why are we talking about sustaining a site before we have built it? Because there are several ways to develop a solution what you have designed. Some solutions will be user friendly and some could require you know a lot more about Drupal than you want to.
admin1 - Fri, 2010-06-18 16:32
Accessibility "means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web."[fn]Introduction to Web Accessibility - http://www.w3.org/WAI/intro/accessibility.php[/fn] The Web Accessibility Iniative (WAI) at http://www.w3.org/WAI/ provides all the details you need to know regarding accessibility.