12/9/2023 0 Comments 11. drupal vmLarge tasks like "theme the site" aren't very helpful and comment threads in tasks like this often become unwieldy, defeating the purpose of using a project tracker. How often is a project ready to launch and then at the last minute a stakeholder chimes in requesting changes? This is demoralizing and frustrating for the entire development team. Note the "and stakeholders" - this includes project managers, content and QA folks, and anyone else who has a role in the project. I'm a firm believe that commitment to a project tracker must include 100% of the development team and stakeholders. Commit to the entire team using a project tracker I've seen way too many projects invest in a full-on CI/CD system only to have it ignored because developers didn't have the time and/or expertise to utilize it properly. There's a lot of focus on DevOps in the Drupal ecosystem (with good reason), but before you jump into a continuous integration/continuous development (CI/CD) system, be sure you have the basics first and then add complexity only as necessary. At the very least, projects of all sizes should have not only a dev and live environment, but developers should have local environments as well. Having a professional developer workflow should go without saying, but I often come on-board small, single-developer projects that have a remote development environment and a live environment - and nothing else. Commit to a Local->Dev-Stage->Prod developer workflow With sustainability, and all of the elements that contribute to it in mind, I present the 11 tips to start a Drupal project right. I want to build sites that are easy to maintain, easy to update, and easy for different developers to cycle in-and-out of. I always want to be involved in a solution that provides good value not only now, but for the lifetime of the project. One word I use often when speaking with current as well as prospective clients is "sustainability". The breadth of this experience has really contributed to my ability to provide more value for my clients. There have also been projects with massive budgets as well as projects with no budget. I’ve been alone on project as well as with large teams of developers. I have worked on projects of all sizes from large Fortune 500 companies to small local businesses. After all, it is this community that has made it possible for me to have the success that I have found so far. In addition to documenting the process for myself as well as my current and future clients, I also wanted to share what I've learned with the Drupal community. For well over 10 years, Drupal training and development has been the focus of my consulting business over the holidays I took some time to look back and really think about the lessons I've learned and how I can utilize them moving forward. As someone who has been building Drupal sites for over 12 years now, I'd like to think that my knowledge and expertise has grown at a rate similar to the power, flexibility, and complexity of the Drupal project itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |