Annertech: DrupalCon Dublin: We'll be at Booth 901 (and here's why it's in your interests to meet with us)
As Ireland's leading Drupal devlopment agency, we were thrilled that DrupalCon was coming to Dublin. So much so, we were the first Irish agency to add our name to the sponsorhip list (not to mention being the only Irish agency with people giving presenations at it). For the week of DrupalCon we'll be manning Booth 901.
Base themes in Drupal are incredibly useful but often add bloat to the finished sub-theme when care isn’t taken to remove unnecessary css files, or files that are 5% used and 95% overridden. When porting aGov to Drupal 8 we took the opportunity to improve how it’s theme inheritance is managed, making it easier to create trim, lightweight sub-themes.
I learn best when I have a problem to solve, and with one of our D8 upgrade projects, we had a mess to clean up in the menu system. This provided an excellent oppportunity to get hands-on in Drupal core, learning some of the major differences from earlier versions, and three things in particular:Drupal 8Drupal PlanetMenuLinkContentDrupal ConsoleEntity SystemTechnical
Information from Web analyses is supposed to help understanding user behavior and optimize the individual online performance. But what if the analysis tool is showing nothing instead of numbers and graphics? In the second part of our experience report about the software of Sitecore, we will explain how to run the Dashboard notwithstanding some hurdles.
When installing Drupal, one of the things that some people must do beforehand depending on their specific server configuration is to change "+FollowSymLinks" to "+SymLinksIfOwnerMatch" in the .htaccess file. But another problem is that there is one more place where these people need to repeat the same exact step after installation, or they will undoubtedly encounter an additional problem of having their images not showing up at all:
+FollowSymLinks ProblemTags: Drupal 7Drupal Planet
It's been way to long since we've written one of these, and a lot has happened in the last year. Yeah, that's right, it has been a year since the last "This Month in Drupal Documentation"! I can't even being to summarize the whole year in a single post, so here are some highlights of what is going on right now.
Here's an update from the Documentation Working Group (DocWG) on what has been happening in Drupal Documentation in the last month or so. Sorry... because this is posted in the Core group as well as Documentation, comments are disabled.
If you have comments or suggestions, please see the DocWG home page for how to contact us. Thanks!Documentation Working Group Updates
It's been a while since we've had a working group meeting, though we've each been busy contributing to documentation in different ways. Despite the fact that we're not meeting regularly at the moment we're still available to help answer any questions you've got, or help out with any policy/best-practice issues. Let us know.Notable Documentation Updates
We're recruiting maintainers for guides as they are migrated to the new documentation structure. See [#2682083] for a list of guides that need maintainers. Read about what maintaining a guide entails. If you're already maintaining a guide, thank you! Drupal is easier to learn because of it. This is the result of nearly two years of work by dozens of people, and we're super excited. I'm not going to be able to list or remember everyone that's helped with this but of note. If you see Tatiana, or any members of the Drupal Association's infrastructure team make sure you thank them for their hard work on making this possible.
Going forward I'm hopeful that we'll be able to being to highlight individual guide maintainers and the work they're doing.
Tatiana wrote a great post recently about the changes, and if you haven't been keeping up it's worth reading.
The User Guide has just completed the copy editing phase, and we will begin translating it into other languages shortly. You can read more about that here https://www.drupal.org/node/2762261. And, sign-up to help your language group with the translation.
Jennifer, and Neil have been working hard to make it possible to import the contents of the User Guide to Drupal.org. Work that will hopefully be deployed within the next couple of weeks. Once that's complete you will be able to read the User Guide in it's entirety right on Drupal.org! Super cool.
This is the result of over a year of planning, writing, editing, and coordinating by everyone involved. It's a huge achievement and I'm hopeful that it helps to set a new standard for Drupal documentation going forward.Documentation Priorities
The Current documentation priorities page is always a good place to look to figure out what to work on, and has been updated recently.
One task in particular that we could use some help with at the moment is cleaning up the titles and summaries of recently migrated documentation pages. As pages are moved into guides each one needs to have a summary written. Summaries are a one or two sentence blurb that is displayed on the main guide page helping people get a better idea of what the individual page contains. During the migration we've added quick summaries, but people who understand the material better can likely help summarize the content better. Help us make the summaries better, which helps others find the content they are after.
If you're new to contributing to documentation, these projects may seem a bit overwhelming -- so why not try out a New contributor task to get started?
What are you working on? Let us know and we'll help get your initiatives into the next update.Upcoming Events
DrupalCon Dublin is this month, and Joe (@eojthebrave), and possibly others, will be in attendance. There isn't an official documentation sprint as of yet, but we'll work on getting something organized between now and then. Look for our table(s) in the official sprint room.
Landing pages are powerful inbound marketing tools. They have a simple goal: to convert incoming page visitors into customers of some kind. Landing pages fall into three general categories:
Previously on our blog, we discussed the five basics of content marketing. The first of these five basics of content marketing is understanding your audience, which we achieve by constructing personas. Once you know who your intended audience is, you can tailor your content to help encourage users to progress through each step of their individual buyer's journey.
Happy Friday! We hope you've had a great week and that you're gearing up for an even better holiday weekend.
This episode, we decided to switch it up a little and find out what some of the Mediacurrent team has in store for Labor Day. We hope everyone has a safe weekend and we'll pick back up in October with episode 17.
When building more complex queries using db_select() you will often want to see the exact SQL being generated. This is helpful for understanding the query or simply debugging the results.
I'll show you how to see the exact query being generated with db_select() as well as getting all the values passed as arguments. The examples in this article will be applicable for both Drupal 7 and Drupal 8.
Example #1: using db_select() and creating the query dynamically:
If you guys didn't already know, we're in the middle of the Results Oriented Web Roadshow! You can take a closer look at Tom's adventure across the country here. Our next stop is this upcoming Tuesday, September 6 in Chicago at Timothy O'Toole's Pub!What you can expect: Learning:
We will be giving a short presentation that focuses on the essential techniques to...Read more
The basis for knowing what to focus on for evolving Drupal core is learning about what people want to do with it.
Testing the initial experience of core as a whole has had our main attention so far. Now with focussed initiatives (content workflow, media handling, outside in, layouts,…), we’re adding experimental features with the assumed requirement that we validate and improve them trough feedback from usability testing.
So, we could (should!) create a more regular schedule of more smaller instead of few bigger usability test sessions. What’s our version of getting out of the building and increasing our exposure?
What would it look like if we did test every 6 weeks?
Produce testing scripts for each initiative. These can be reused, eventually updated where needed. Every 6 weeks we run those tests for each initiative. We learn what works, what needs to be improved. Initiative teams can prioritize fixing UX bugs. All things are connected anyway so we’ll learn about overall issues as well.
Feedback from the test participants can feed into ongoing persona work: what are people trying to achieve? Voilà, we’re learning about the Why.
Of course this requires planning, recruiting participants, having a setup for remote testing, getting access to a usability testing lab once in a while, observation, analysis, designing possible solutions, reporting back to the community, creating actionable issues to work on etc. But wow, we’d learn so much about where to focus our efforts.drupaluxusability testdrupalplanetSub title: Something something usability testing
DrupalCon is coming to Dublin next month. Damn, we're exicted. You are too, we know. Actually, apparently there's a small few people still trying to make up their minds on whether to come to DrupalCon Dublin or not.
Sitting on the fence? Don't. Get off the fence, get to Dublin. Here's some reasons why (feel free to add more in the comments).
A user pathway (sometimes called user flow and user journey) is the path a visitor takes on your website before completing the action you would like them to take.
You can tackle the user pathway, after you have completed your user research and user personas.
Here's how ...Setting the Stage for the User Pathway Step 1 - Determine what your Macro and Micro goals are
For example, as a business solutions company that specializes in web development and design, and marketing communication, the final goal we would like visitors to our website to take is to contact us with a project or challenge they need help with.
As a nonprofit, your final goal might be to get a donation, a registration, or a contact form filled out.
Listen up, Drupal savvy MailChimp fans. We’ve got some news for you: MailChimp recently rolled out a newer and more robust version of their API - MailChimp API version 3.0! Now I can probably guess what you’re thinking so I’ll just come out and say it: this means MailChimp’s API version 2.0 is about to become deprecated, and we’re not monkeying around.
For those of you using the 8.x and 7.x-4.x branches of the MailChimp module, feel free to sit back and relax - you are already using MailChimp’s API v3.0. Those of of you still using the 7.x-2.x and 7.x-3.x branches, get ready: API v2.0 will be phased out on December 31st, so we encourage you all to upgrade.
Don’t be a furious George - we’ve got you covered. Our documentation up on Drupal.org has been updated, and we’ve provided information that will help make your upgrade experience as seamless as possible. We’ve even included a shiny new FAQ page this go around. For additional support, feel free to post questions on Drupal Answers.
Alright, let’s get down to monkey business. Those of you who upgrade are about to have a module that is regularly maintained, has an improved infrastructure (see the README.txt on the 7.x-4.x branch for more info), and can be integrated with the new MailChimp E-Commerce module (more on that in a future blogpost) - now, that’s something to go bananas for!
Being casual about open source security is not funny. Headlines like the Panama Papers this year showed that an improvident dealing with security and updates can cause a huge damage. Fees are still a crucial reason for people to hesitate to secure their business by using charged services. This is not a pitty - this is grave.
There are many people out there who give a lot without receiving a reward. They see more benefits in helping and strengthen people, any kind of living being or purpose than in a regular salary.Drupal Drupal Planet Security announcements non-profits Drupal Community
Every website that displays user information on the front end will use profile fields such as first and last names for representing the members. By default Drupal shows only the username, which is definitely something you will want to change.
Modifying this is relatively simple. You could always choose which fields to use in Views, Rules and other modules, but the main problem is maintenance - the setup will be spread across many different pages and it's not the most optimal solution in the long run.
The right way is to change the way user display names are formatted by the system itself. This article will show you how to manage this for both Drupal 7 and Drupal 8 in your custom code.aram Wed, 31/08/2016 - 21:15