I went to DrupalCon this year with the goal of doing things a bit differently this time. I’m a bit of an introvert with people at first, but I’ve been told I don’t come off that way.
I attended both Drupalcon and the Nonprofit Tech Conference this year. They were on the same week, so I started the week at Drupalcon then caught the tail end of NTC.
I went to my first Nonprofit Tech Conference this year! As a heads-down coder day-to-day, it was refreshing – if somewhat exhausting – to spend time talking to new people working on so many cool projects. I was seriously impressed.
Last week, we discussed a few ways design deliverables can be made with the goal of streamlining the front-end development process. This week, we’ll address design complexity and how to simplify things with that same goal.
Here at Advomatic, we frequently get the chance to partner with really creative, disciplined, and talented design shops. Over the years, we’ve identified a few areas where we can be more helpful to them.
The problem If you are using Drupal’s Configuration Management subsystem to deploy configuration out to the production environment, you’ll run into a problem where the configuration .yml files contain your development settings.
I was fortunate enough to get to Baltimore for this year’s DrupalCon. Here’s a few takeaways regarding Drupal’s open-source community. The community is still strong.
How to ensure that satisfaction in your websites remains high, while also levelling out your spending A typical website is created in a burst of activity (and spending), then “launched” to the public. There is probably some really great thinking
Picking up where we left off in Part 2, in which we went over some of the tools and design considerations for accessibility, in Part 3 we’ll review some tips for minimizing accessibility issues by addressing them early in the development process.