1.Version Control:
Experience with version control and versioning is crucial for web developers. Version control is an essential part of the Drupal community. Versioning allows easy management and maintenance of Drupal projects. Version control is used in-house to manage each client project as well.
2.Command Line Interface (CLI):
Being able to work comfortably using a CLI is very important. It helps you be more productive. You can automate repetitive tasks, perform tasks without jumping from application to application, and the ability to use tools like Drush to perform tasks that would normally require you to navigate 3 or more mouse clicks to accomplish.
3.Package Managers:
Package managers are important to the Drupal installation. Whether it is installing Sass or Bootstrap from node or Drush from composer, it is important to know how package managers work and exactly what you are running before running commands on your computer.
4.Contributing Back:
Contributing back to projects and core is vital for Drupal community. When you find an issue or you would like to implement a functionality to Drupal, you should think about giving back to the community.
If you find an issue on an existing project or core, check to see if there is an existing ticket on that project. If there isn’t, you can create one, and if you can debug it and resolve the issue you can contribute a patch to that issue. If you don’t know exactly how to debug the issue you can have an open conversation with other developers and maintainers to help resolve the issue.
Contributing and interacting in the community moves Drupal forward.
5.CSS Preprocessors:
Within the last couple of years, there has been a movement to CSS preprocessors to add a programmatic feel to CSS2 and CSS3. Some developers are against preprocessors because it adds a little more overhead to a project. Whether you use them or not, you may have a client or framework that uses one. That's why you have to be familiar with how to use a preprocessor.
6.A Framework:
Within Drupal community, there is often talk of headless Drupal.
Headless Drupal setups usually use a framework for the front-end. It may be Angular, Angular 2, Backbone, Ember or something different. However, most of the frameworks have two things in common: they are often written in Javascript and make use of templating.
7.Templating:
It is important to know the principles of templating so that you can easily pick up and learn new frameworks. Whether it is Mustache, Twig, Jade, or the templating syntax from within Angular, there are similarities between the syntax and the principles that can be applied to each of the languages. This will allow you to quickly step from one to the next with a smaller learning curve.
8.Basic Debugging:
Debugging a problem correctly can save you valuable time by getting you directly to the cause of an issue instead of looking over each line of code one by one. It is essential to know how to do basic debugging when working with Drupal. Sometimes the error messages can give you enough information, other times it is necessary to step into Devel or XDebug and step through the project to find the exact location where the code is not working correctly so that you can start solving the problem
9.Unit Testing / Code Testing:
Testing your own code is important. When it comes to code testing you have many options, from TTD and BDD, you can write unit tests to cover your classes, linting to make sure you are writing “good”, standardized code. Linting can be helpful for writing code that others can easily navigate and sets up some best practices for you to follow.
10.Learn to use Drush:
Drupal has a shell interface called Drush that allows you to perform various tasks from the server’s command line. It’s a powerful way to automate certain tasks like syncing databases between two servers. It also allows you to get common tasks done without having to navigate through Drupal’s Admin interface.
You can do cool things with Drush like:
1.clearing Drupal’s cache – drush cc all
2.overview of your Drupal website – drush status
3.install the views module – drush dl views
4.enable the views module – drush en views
No comments:
Post a Comment