The last week three of us from Cocomore went to the little town of Szeged in Hungary around 175km south east of Budapest.
The DevDays were all about developing Drupal 8 further and enhance drupal.org. The only topic was contributing to Drupal in the one way or the other. Whatever you are, either a developer, a themer, a site builder, a devop or a business man, everyone has his/her part in this amazing community and everyone found a spot where he/she could help to foster Drupal further.
How’s this for a session title? “Newfangeldy mobile and front-end crap for people who last touched front-end code back when grunge was a thing.”
Or this one? "Markup Ain't Easy or: How I Learned to Stop Worrying and Love An Object-Oriented RenderAPI"
I finally got to take a long & hard look at fields and why they have so much divitis + a solution of how to change it for Drupal8. It ended up beeing a ton of markup & css examples on a flat html page
take a look please provide feedback, here or on the issue or at my twitter etc.
We will review some of the pretty neat Drupal contributions coming this year. The community as a whole has really outdone themselves. Step aside Drupal 8, you are about to get passed up. Without further ado, here is our top 10 Drupal contributions for 2014.
The best way to design and modify your Drupal site is with overrides.
If you're not sure how overrides work, read our introduction to Drupal overrides.
One of the most powerful ways to override Drupal is with sub-themes and sometimes even with sub-sub-themes. These allow you to safely override any themes you download from Drupal.org.
This is a dense topic, and this post is very long. So, let me provide a short summary here before you all tl;dr me, which would be deserved. The long and short of it is that Association staff and other community members have to figure out a better way of working together.
It is with a mixture of bitter and sweet that I am officially announcing that I'm leaving Commerce Guys for a new position elsewhere. I have really enjoyed the last 3 (nearly 4) years at Commerce Guys. They have been an amazing place to grow both as a person and as a programmer. During my time there I've had the opportunity to work on numerous big projects and interesting technical challenges. Commerce Guys funded me to work full time on Drupal 8 as an initiative owner for months on end, and without that investment of time, I personally wouldn't have grown so much, nor would I have been able to contribute to Drupal 8 to the same degree. I cannot stress how great of an experience working there has been for me, and I'm thankful to all the people there who made that possible and made my own time there so enjoyable. I look forward to seeing them do great things.
As for my future, I am actually moving to Acquia. An interesting job position opened up there that will allow me to be the interface between Drupal's developer community and Acquia. This is especially interesting to me because it makes me part of the feedback loop that is intended to help Acquia understand what portions of Drupal developer experience are in need of improvement. In this role, I'll work in whatever capacity I have at my disposal to help mitigate these issues and improve Drupal from a developer experience perspective. In addition to this I'll function in the same capacity for various Acquia product offerings, and I find that very exciting as well.
In truth most developers want to escape client work, and despite what you might think, that is impossible if you want to continue development. We can only strive for better clients, whether that is literally a higher quality client, or whether you manage to make yourself your primary client, we always have clients. In many ways I think this move makes YOU my client, yes you. The whole of the Drupal community will be my singular client. I’ll interact with you at different levels, we’ll talk personally, we’ll talk corporately, we’ll interact at camps and cons. I’ll try a few things and I’ll probably fail at a few things, but I took this position because Drupal is really important, and I want to be a part of crafting its future in whatever capacity I might have available to me. This job opens that up in ways I hadn’t considered before, and that’s very exciting. Technically speaking, this is a marketing position, and I know that’s weird for a developer, but this is no mistake, I’ll just be marketing DX improvements, and gathering information about where DX is lackluster so that we can craft a better solution, together. I look forward to this role and this work, and I hope you do as well.
Kris “EclipseGc” Vanderwater
As mentioned in my previous blog post "Catching the Community Train" Lisa, Bojhan and myself will be working on a website to better facilitate the process of designers contributing to Drupal. Following my last blog post we sent out a questionnaire to current and previous contributors in order to gain some valuable insights that will help us move forward. In this blog post I will analyze the answers we received and share what they mean to me and how they will be instrumental in our success of helping designers more easily get involved in Drupal.
In the very recent period this new thing popped up in the Drupal community that has everybody talking: the Acquia certification for Drupal developers. I'm writing this article minutes after actually taking this exam to share with you my impressions.Why did I take the certification?
One of the things that prompted me to it was Angie "webchick" Byron's article about her experience taking the exam. It sounded interesting but also relevant to me as a Drupal developer. It announced an exam that could determine my value in this field.
A second aspect I'd like to mention is the fact that I work with Drupal but do not have an IT background. I am, what you call, a self-taught. Therefore the idea of having a certificate to prove my worth sounded good to me. So I took the opportunity and the exam that came with it.Impressions
There are 2 ways you can take the exam: on site (physically) or online. To deliver its online exam, Acquia collaborates with Web Assessor, a secured testing environment.
I chose the second option which meant I had to install some software onto my computer and go through a substantial verification process. This included biometric baseline recording of the face and keystrokes in order to be able to authenticate when I start taking the test. I know, advanced stuff.
To a certain extent I understand the need for this highly secure exam taking environment that prevents people from cheating. However, Web Assessor could have made things easier for people to take these necessary steps. What do I mean by this?
For one, there are contradictory instructions on the site. In one place it says you don't need an external webcam and microphone and in another it says you are not allowed with the built in computer ones. So which one is it? In the end, I did it with my internal ones, so it is possible.
I finally got through the hurdles of installing the software, closing all my apps, creating the biometric baseline, etc to arrive to the booking of the exam. It was very flexible and I could book a time in the same day: that's what I did. I liked that very much. However, I had to wonder about the timezone, just select an hour and hope it corresponded to my timezone. There was no indication as to which one was being used. Luckily, it was the right one so there was no problem. Therefore, in case you are wondering, it will be the timezone you are in when you book.
The whole process of preparing for the exam with Web Assessor took about an hour. Not so much the settings themselves but reading and understanding what I have to do, what I can do and what I can't do.But what about the test?
I'm going to go right out and say it: the test was hard. But I was expecting it to be hard because otherwise it's pointless. It had only multiple choice questions with only one correct choice most of the time. For the others, you have checkboxes instead of radios.
Timewise, I had 90 minutes which for me was enough. I even got a chance to review some questions to change the answers and submitted the exam with some minutes to spare. And I appreciated the option to flag questions I'd like to review later.
I can't really go into what questions I got or how they were formulated but they were well balanced with regards to the domains covered by the exam.
One problem I had though was with the code formatting. Some of the questions contained code snippets that were a bit tricky to read / understand. I believe a bit more effort can be dedicated to making them more readable - especially when they are in the available choices. I recommend therefore, if possible, putting all code snippets in code blocks and properly spacing them.
I submitted the test and immediately got my result. Passed. It gave me a very good feeling and made me happy to take it. One thing I was disappointed with was the fact that I couldn't see which questions I got wrong. This may be just me but I was left a victim to obsession over which were those battleground questions that made me think so much. But anywho, we move on and develop some more Drupal sites.
Congrats Acquia on this great new initiative!
Today we are proud to announce that amazeelabs.com, our main website, has been re-launched ON DRUPAL 8.
After countless hours of emotional debate we came to the conclusion that we required a bold move to communicate our position as Switzerland’s #1 Drupal agency. To put this straight we actually are the proud owners of the first company web presence on Drupal 8 - on the entire web!
We strongly believe that a website isn't the final destination after all, it’s just the medium for the creation and promotion of a site’s content.
Gregory Gerhardt, Managing Director and Founder of Amazee Labs, commented: ”For too long our brilliant design has fought an uphill battle against the evil work of copycats. Our new website design shall rest uncopied - simple, authentic, close to its roots."
We hope you like our new face.
Every Drupal site builder will at some point experience the dread of accidentally making configuration changes on production thinking it's their local site. This sort of thing can easily happen when you have 20 tabs opened and forget which site you're currently browsing.
Luckily there's a module you can use to indicate which environment (local, staging, production, etc.) you're currently viewing and it's called Environment Indicator.
The module helps to separate each environment by displaying a coloured indicator. The indicator itself is fully configurable. You can change its colour, position and text.
In this tutorial, you'll learn how to create an indicator in two ways: through the module's UI and with some code in settings.php.
The next alpha for Drupal 8 will be alpha 11! Here is the schedule for the alpha release.Apr. 20-22, 2014 Only critical and major patches committed Apr. 23, 2014 Drupal 8.0-alpha10 released. Emergency commits only. Apr. 24-27, 2014 Disruptive patch window
Have you ever wanted to be able to have a single page where you could update pricing and/or stock for your entire store? Look no further! Today you'll learn how to create a price and/or stock updater in 5 minutes with Views and the Editable Views module. It isn't perfect, but it can save you a bunch of time!
Getting started in Drupal can be daunting. The first hurdle most people encounter is the terminology Drupal uses. Some terms may be completely unfamiliar while others have a different meaning depending on the context. The faster you learn to understand and speak Drupaleze, the easier it will be to communicate with other Drupal developers more effectively. To that end, here are a list of terms commonly used in the Drupal world:
Preview of: A Complete Guide to Being the Best Drupal Shop on the Planet - A session delivered by Kenny Silanskas at NYC Camp 2014
For years Drupal has been known for its powerful content management capabilities. Many large companies leverage Drupal for its rich features and vibrant community of contributors. More recently Drupal has caught the eyes of many developers as a viable framework for web application development. Enterprises shifting from a .NET development environment may find some of Drupal, PHP’s, and the LAMP stack in general a bit challenging to fully adopt.
We’ve been sharing lots of big news at the Drupal Association lately. From hiring a CTO to lead the Drupal.org Tech Team, to implementing a content delivery network (CDN) for parts of Drupal.org, we’re making big, exciting improvements at the Association — and they wouldn’t be possible without our Supporting Partners.
Go multilingual. Your biggest markets are most likely non-English speaking. To maximize your online presence, offer at least two language options. Find out if any of your systems aren’t equipped with multilingual capabilities, so you can address the challenge before you transition.
Accommodate many currencies. Check to see if your currencies are converting correctly. Make sure that the currency and date displays always reflect a user’s local currency, so that they’ll have the simplest possible path to purchasing from you.
Be agile. Time is of the essence when it comes to penetrating potential international markets. Strategize your globalization with an eye for efficiency. Adopt the tools that will help you stay fast, including translation management, which enables companies to capture, reuse and recycle their online content—providing the best efficiency for current, consistent content for all customers, everywhere.
Localize. When you translate content, make sure that you also localize—use the appearance and colloquialisms that your audience is familiar with. Otherwise, you risk alienating your customers with cultural faux pas, such as using a color that signifies bad luck, or translating a phrase that works in English, but means something unbecoming in your target language.
By addressing these five aspects of global-ready eCommerce, you’ll jump on the fast lane to effective globalization.