Look at related code in Drupal core for additional guidance on route naming.Links and tasks should mirror route names.Prefix routes with the module's namespace.For example, all custom block class names should end with "Block." If a class, service, or plugin extends a base class, use the base class name within the child class.Don't use abbreviations and be as specific as needed to ensure things make sense to other developers.As previously stated, when in doubt, look at other people's code.Follow Drupal's naming conventions because dozens of smart people have contributed to them.Send us information about you and your conditions and we will study if we can work together. We like to be surprised.įinally, although we are thinking about an indefinite profile we can also evaluate the possibility of freelancers for those moments of peak work. We know that what we ask for can be a lot, that's why this list of requirements and wishes is always subject to the capabilities you offer us. In general, to progress professionally, we don't like to stay stagnant. ![]() ![]() Slaying dragons as a team (problems sometimes grow and spit fire, and the team will be there to support you). Making, applying and evaluating patches, and contributing to the Drupal community.Īuxiliary technologies such as Gulp, Ansible, PHP CS, Ionic, Angular, TypeScript, Nginx, Apache, Virtualbox, Docker, Linux.ĭevelopment with Git using branches and pull-request for functionalities.Īutomatic integration using Jenkins adapted to Drupal.ĭevelopment with tests using Behat and PHPUnit. Pleasant work environment with high flexibility (in the good part).Īnnual budget for technical events related to Drupal and working technologies (Drupal Camp, DrupalCon, Drupal Dev Days, etc).ĭrupal, from the basics of programming such as coding standards to the latest contributions of the 9.x branch, including consolidated workflows such as Drupal Project.ĭrupal development, module development, theme development. Weekly working hours to c ontribute to Free Software projects with the freedom to choose what to spend them on. Intensive working day during part of the summer. Salary depending on experience and knowledge, between €30,000 and €40,000.įull working day from 8:00h to 17:15h, with one hour for lunch, except on Fridays because we finish at 15:00h. Profiles that can support you like GitHub accounts,, etc. System administration knowledge (web servers, reverse proxies, caching, Redis/Memcached, containers, etc). Knowledge of good development practices such as dependency injection, patterns, coding standards, etc.Īngular and TypeScript or other JavaScript technologies (React, Vue.js).Įxperience in Behavior Driven Development ( BDD) and Test-Driven Development ( TDD).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |