This is final installment of our four-part blog post series that encapsulates the advice, tips and must-do elements of career building in the Drupal Community from the panel of experts collected for DrupalEasy’s DrupalCon Austin session; Drupal Career Trailhead; Embark on a Path to Success. It will be listed with other career resources for reference at the DrupalEasy Academy Career Center.
Jason Smith (Silcon.Valet), Solutions Architect for Mediacurrent, joins Mike, and Ryan to talk about one of the highest-trafficked sites in the world re-launching on Drupal: weather.com. Other topics discussed include the Acquia CEO’s recent Reddit AMA, sprint nutrition, and Damien McKenna.
I wanted to post this here, since this is more of my sounding board for the Drupal community, but the details are on my personal blog: starting October 6, I will be working for Acquia as a Technical Architect in their Professional Services group!
What does this mean for this site/blog, Hosted Apache Solr, and Server Check.in? Not much, actually—they will continue on, likely at the same pace of development they've been for the past year or so (I'll work on them when I get an odd hour or two...). I am still working on completing Ansible for DevOps, and will actually be accelerating my writing schedule prior to starting the new job, since I'll have a little wedge of free time (a.k.a. unemployment!) between Mercy (my current full-time employer) and Acquia.
When Google Tag Manager and Drupal work together, great things can happen. Both from a web developer's perspective and from a marketer's perspective. We'll take a look at how it all comes together.
I'll be heading out to Denver to give a Sunday keynote at DrupalCamp Colorado.
The theme of the event is "Enterprise Drupal," so we'll be diving in to what that phrase actually means for development firms.
If you're in Denver, please come on down and say hello.
When working in a team or in an environment where your code and systems are going to be used by people other than yourself, it is especially important that your site development process is clear, simple, and easy to understand. This, of course, is easier said than done when developing a complex Drupal site. However, when our developers, site-builders and themers are all on the "same page" with code organization and philosophy we are a more effective and efficient team.
After speaking with members of the Drupal community, we believe it is time to start a discussion on how to have a process in place so as to minimize the friction when developing in a team/cooperative environment. In an effort to deep dive into our process this article will be the first in a series of articles discussing our SDP.
A lot of our SDP revolves around how to organize your code so that a developer or site-builder can quickly on-board to a project and larger teams can work together with minimal down-time. The broad pieces of our SDP are:
- Everything is in code.
- Sites are built using install profiles and the install profiles have a specific directory structure.
- Install profiles use Drush Make to capture dependencies on external modules, themes, and libraries.
- Drupal migrate is used to populate test content during the development phase. (optional)
- Features are used to capture site configuration. (optional)
- While a site is in development all functionality must be present after a fresh site install.
- After a site goes live update hooks can be used to enable new functionality on the production site.
- Use a virtualized environment which mirrors production. (recommended)
What do you think?
Do you have an process expressed or implied? Leave comments below and lets keep this conversation going.
Commerce Authorize.Net Card Present is a new Drupal 7 module sponsored by Last Call Media that allows a Drupal website to accept payments by swiping a credit card through a USB credit card reader.
Developed to accompany Commerce Point of Sale (POS), another module sponsored by Last Call Media, Commerce Authorize.Net Card Present can be used in conjunction with Commerce POS to set up a fully functional Point of Sale system in Drupal 7.
For more information on how to install and configure this module, please visit Commerce Authorize.Net Card Present's project page.
On the weekend of July 12-13, 2014 the Central NJ Drupal Group held a core sprint focusing on the upcoming release of Drupal 8. The sprint was attended a great group of Drupal enthusiasts from Chicago, Montreal, New York, Virginia, and of course New Jersey. We took over the Cowerks coworking space in Asbury Park, NJ for the two days and it provided us a fun space to work the day and night away on a variety of issues.
With only seven beta blockers remaining at the time of our sprint, two were on the top of our list of items to work on. Fifteen people participated in person, and the group made progress on two beta blockers (leading to core commits) as well as many other issues.
See the full recap for more details on participants, issues worked on and completed, and a photo gallery.
Have you ever wanted to show only selected information on a content type to anonymous users and more information to authenticated users? It turns out that you can use Display Suite to provide field-level permissions for an entity.
On Thursday, July 24th, we had a live webinar where we introduced Open Enterprise Intel. If you missed it, don't worry, we have the video right here as well as on YouTube available in HD.
... Read more
Acquia is constantly working to improve our service offerings, and that means cleaning up existing features and adding new ones that we know will make a big difference in people’s workflow for the better. Despite the scale of some of these improvements, they’re not always immediately visible at first glance, so I’ve taken a bit of time to highlight three recent ones.
DrupalCon Amsterdam: Growing the Community & the Project Through Grants, Scholarships, and Mentoring in Amsterdam
Grant and scholarship recipients have been selected for DrupalCon Amsterdam. We had a huge number of wonderful applicants, and selecting our grant and scholarship recipients was a challenge.
For applicants seeking grants, we focused on the importance of each candidate to the Drupal project and code as a whole. Scholarships, meanwhile, were awarded based on the impact or influence on the Drupal community and Drupal adoption that the person would have at their home region— though these were just a few of the many factors taken into account during the selection process.
We’re please to announce the following grant and scholarship recipients below:Grant Recipients
- Nathaniel (catch) Catchpole - United Kingdom
- Larry (Crell) Garfield - United States
- Dave (Dave Reid) Reid - United States
- David (David Hernández) Hernández Ruiz - Spain
- Dan (dcmul) Mulindwa - Uganda
- J Branson (j.branson) Skinner - United States
- Joël (joelpittet) Pittet - Canada
- Jose (Jose Reyero) Reyero - Spain
- Jeremy (jthorson) Thorson - Canada
- Kalpana (kgoel) Goel - United States
- Patrick (patrickd) Drotleff - Germany
- Brian (realityloop) Gilbert - Australia
- Ricardo (ricardoamaro) Amaro - Portugal
- Sébastien (SebCorbin) Corbin - France
- Shyamala (Shyamala) Rajaram - India
- Janez (slashrsm) Urevc - Slovenia
- Evgeniy (Spleshka) Maslovskiy - Belarus
- Tim (stpaultim) Erickson - United States
- Kristof (swentel) De Jaeger - Belgium
- Yves (yched) Chedemois - France
- Zsófi (zsofi.major) Major - Hungary
- Aldibier (aldibier) Morales - Colombia
- Alvaro (alvar0hurtad0) Hurtado - Spain
- Andrey (andypost) Postnikov - Russian Federation
- Carlos (camoa) Ospina - United States
- Luis Eduardo (edutrul) Yelaya Escobedo - Peru
- Grzegorz (grzegorz.bartman) Bartman - Poland
- Konstantin (konstantin.komelin) Komelin - Russian Federation
- Weber (Mac_Weber) Macedo - Brazil
- Ivan (rootwork) Boothe - United States
- Tanay (saitanay) Sai - India
- Shabana (Shabana Blackborder) Navas - India
- Tarek (tarekdj) Djebali - Tunisia
We’re excited to see all these great people at DrupalCon Amsterdam, and can’t wait to learn from them and make the project even better. When you see our grant and scholarship recipients around volunteering at the event or mentoring new sprinters, give them a high five for being amazing! And regardless of whether you’re receiving financial assistance or not, if you’re coming to DrupalCon, you can share you knowledge and help make Drupal even better too by signing up to become a mentor.
Growing the Drupal project can’t happen if our community doesn’t grow, too— and there’s no better way to help grow the community at DrupalCon Amsterdam than to give back by teaching new skills and ideas to basic, intermediate, and advanced Drupalers.
It has been a weekend in the spirit of headless Drupal, front-end optimizations and server side hacks. The result is I updated my blog to Drupal 8. Since you are reading this, it must mean it is live.
First let's start with the cold facts (almost chronologically ordered by request lifetime):
Other front-end technologies used that does not directly relate to the request itself:
Yeah, that's mostly just a novelty act. There is no real gain there. Quite the opposite, I have added some hacks to get around some limitations.
HHVM does not work very well with logged in users right now, but works alright for serving anonymous content.When I reload and look at the source code, there is no css loading. WAT?
Yeah, I am just assuming you remember the styles from last page load. Also, I have made it an image to have a 1 HTTP request CMS, right?No, really. How does that work?
The real magic is happening by checking if you as a user already have downloaded my page earlier. If you have, I don't need to serve you css, as far as I am concerned. You should have saved that last time, so I just take care of that.OK, so you use a cookie and save css in localstorage. Does that not screw with the varnish cache
Good question. I have some logic to internally rewrite the cached pages with a key to the same varnish hash. This way, all users trying to look at a css-less page with the css stored in localstorage will be served the same page, and php will not get touched.What a great idea!
Really? Are you really sure you have thought of all the limitations? Because they are many. But seeing as this is my personal tech blog, and I like to experiment, it went live anyway.Give us the code!
And since I am feeling pretty bad ass right now, let's end with Clint Eastwood as an animated gif.Tags:
The last months I was busy with a friends art project. Today I'm very happy to announce that it went public on july 15th and is doing good so far.
Jule, the founder of Port of Art, approached me last summer, asking if I could help her building an online market place for artworks. Working primarily as a freelance Drupal developer, knowing that her budget is tight and that she is certainly not the first one with this idea, I hesitated. But I gave it a thought and after several meetings I agreed. I liked the idea and I liked Jules approach, that is very trusting and positive without being naive. I like good people ;) She also gave me the impression of being able to value constructive input, even if it means to change previous ideas. That is a good feature in clients!Basic ideas with a special flavor
The basic requirements were pretty simple:
- Content management for static content pages as well as for special content like the artworks that are sold on the site
- Search artworks by different filters
- Legal compliant checkout process
- Integration of external payment providers (limited to paypal for the moment being)
- Contact forms
- Multilingual content and communication
- Integration of social media
- Some map views for geo visualization
- SEO, customizability, ...
So far that was relatively straight forward and we all love Drupal for that.
But there were some special requirements too, that had a huge impact on my choice of modules to realize this with.
- Artworks don't integrate with a basic warehouse approach. Each one should be unique and can be bought only once. Therefor there was no need for a shopping cart either.
- Artworks can be bought for a fixed price or as an auction.
- Artworks under a certain price are not sold via the site, but instead the customer and the artist are put in touch directly and have to figure out the details independently of the platform.
- Artists should be able to upload their artworks, pay a fee to get them published and than manage the selling and delivery on their own.
- Artworks expire after a certain time that depends on the publishing fee that the artist is willing to pay.
- Once an artwork has been sold on the site, an additional fee has to be paid.
- Fully customizable e-mails
The main content is obviously the artwork. This is a node type with additional fields to represent attributes of an artwork. Then there are static pages, artschools, faqs and webforms. On the user side we have two frontend user roles for customers and artists that get enhanced using the Profile 2 module.Additional considerations
The situation that our development team was faced with: Small budget, tiny team (only 2 people), the project's concept still a little in the flux. The founder had no technical background or previous experience using Drupal but needed a customized shop system that she could actually manage after we finished the project and went on to other things. So one of the goals during development has always been to make things configurable. Special text at a certain page? Build a setting for that. A special criterion that controls logic during checkout? Don't hardcode it somewhere! Build a setting for that as it might change later and you don't want to change code for simple things. I love drupal for it's easy variable management and quick form building capabilities. Building an admin form to control certain behaviors takes rarely more then 10 minutes. Obviously there are things that you can't build that way, but when you can, do it. I feel much butter with it and the client loves it too because it gives him control.Conception and development process
One of the things I knew before, but that got confirmed again: Communication is the key. The client has never did a web project before. That meant that certain good practices and workflow, concerning the development process as well as the final product, were not clear to her. So we (the designer and me) spend a good amount of time helping her figure out what was realistic and which compromises needed to be done in order to deliver the product without cost explosion or an exagerated time frame. Being honest and communicating potential problems early on, as well as the clients openness towards constructive input, was something that attributed a lot to the perceived quality of the development process. Including the client in the development and design decisions also allowed us to educate her on the technical aspects of the product and raise awarness about technical implications, making her see advantages and restrictions in different areas that she didn't consider in the beginning.
We didn't formalize the process, but we ended up with some kind of agile development with three distinct roles: Conception and design by the client, frontend by the designer and backend logic and architecural design by me. That worked very good for us.
First, there is Rules. A crazy wonderland for workflow configuration that amazes me every time I look at it. But I've almost never used it. Call me old fashioned, but when business logic or complex relations must be build, I prefer to build them on my own. I want as much logic as possible in the code, not in the database. So for all the power Rules provide, I still prefer not to use it.
Then there is Commerce. We have never build a real-world website with it, so our experience was very limited. We thought about it. Very seriously. Then we decided against it. From todays perspective that was probably an error. But given the special requirements we were afraid of having to spent too much time customizing and altering the workflow that commerce proposes. This was more of a gut feeling. And at the end I'm not sure it was the right decision. We ended up with conceiving and building a full fledged product management incuding the purchase logic and payment. The obvious advantage when you write something like this on your own, is that you have a lot of fine grained control about flow and design. But the price is pretty high considering the amount of time necessary. At the end we have a considerable code base that needs to be maintained. So next time, I hope I'll remember this an give commerce a more in depth examination regarding the potential for the problem at hand.Crucial contrib modules / add ons
It's hardly necessary to mention, but we couldn't have build the site so easily without the usual candidates: Views, Webform, Better Exposed Filters, Address Field, CTools, i18n, References, Profile 2, Geofield, Global Redirect, Libraries, ...
The fantastic wookmark jquery plugin is responsible for the display of the central search component of the site. Our designer loves it!Some modules that got born or advanced
I build MEFIBS for this site. I had a need for that functionality before, but never quite as strong as this time, so I decided to solve it as a self contained module instead of hacking things together. Though there are some problems currently with a few new features that I added recently, it is already in production and doing pretty well. Have a look at the filter and sorting blocks on the artwork search page: . Two independant blocks without duplicating a views display or intensive custom form altering. That's pretty neat.
Hopefully the jQuery Update module will also profit. During development I ran into issues with the admin version feature introduced here: https://www.drupal.org/node/1524944. I wrote about it in jQuery version per theme. This resulted in a feature patch that is currently on a good way to get committed soon.
Another module I find myself using often is my sandbox module Mailer API. It's a bit cumbersome to use as a developer, but for the client it's perfect. She can customize practically every mail that will be send by the system. It's all on a single configuration page and supports multilingual setups. A test mail feature is also included to see what mails will look like. And a batch mailer that the client often uses to address a bunch of people. It's like very easy home made promotional mails in a consistent look and feel. Made the client happy.
For frontend eye candy we have build a jQuery plugin that is responsible for the collapsible checkbox filter elements in the left side bar.Some module discoveries
During the work on www.port-of-art.com I found some modules that I didn't know before.
The Form API Validation module allows you to simplify validation rules in custom forms, using predefined validation rules. And you can also add your own rules which we used for the price entry validation needed when artists publish their artworks.
The Physical Fields module provides fields for physical dimensions and for weight attributes. That was exactly what we needed for physical goods. It saved us the time to configure fields in field collections.Conclusion
At the end of the project I can say, that everyone involved has had a good and productive time and enjoyed the process and the result. The client is happy for all the things she can do with the site. Now she can concentrate on managing business and extending marketing. The designer was happy. Even if some of the design decisions might not have been the best ones looking at the requirements profile from today. I feel positive though that the system fully matches the clients expectations and that it'll be a valuable tool for developing her business. If the site manages to establish itself, it's more than probable that we would rebuild the system, at least some substantial pieces like the shop component.
We as the site builders are happy too. We feel that we have done a good job and that we managed to keep resources and expectations in balance. I would do it again, which always feels like a good measure.Category: Drupal Planet7.x
It's fair to say, on a fresh install the content authoring experience in Drupal needs improvement. WYSIWYG editors are often criticised for various reason such as the ugly HTML they are known to generate or the power they give users to mess up typography. While these are valid criticisms, there is definitely a right and wrong way configure these editors. Doing things the right way will empower users while keeping them safe from nasty pitfalls. Note: this guide assumes you're already familiar with a typical Drupal WYSIWYG setup.Provide a true WYSIWYG experience
It's important that a WYSWIYG editor represents exactly what appears on the front-end of your website. While it seems obvious, it's easy to ignore and has a big impact on a user's experience.
Our WYSWIYG stack is: