In the marketing world, content is still king. The internet is an endless ocean of content that is easily accessible at any time, on any device.
This episode we are going to have an interview with Matt Davis, to talk about his work with Weather Underground, and decoupling Drupal from the presentation layer, or die trying. This is our second third take on Episode 18, and we need to thank Oscar Mejivar for coming on. We will be re-recording that episode at a later date, so please tune in because outside my horrible production skills, it’s was a great topic and we want to share it with you. Stay tuned.
Drupal core announcements: Drupal core security release window and 8.1.0 release on Wednesday, April 20, 2016
The monthly security release window for Drupal 8 and 7 core will take place on Wednesday, April 20.
This does not mean that a Drupal core security release will necessarily take place on that date for any of the Drupal 8 or 7 branches, only that you should watch for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).
This is also the release window for Drupal 8.1.0, the next scheduled minor release of Drupal 8. To ensure a reliable release window for the patch release, there will be a Drupal 8.1.x commit freeze from 12:00 UTC Tuesday to 12:00 UTC Thursday. Read the release candidate announcement for more information on the minor release.
The next window for a Drupal core patch (bug fix) release for all branches is Wednesday, May 04. (Drupal 6 is end-of-life and will not receive further releases.)
While we are above the tech average, we are still always striving to foster inclusivity and embrace the involvement of individuals across the gender spectrum. To help celebrate where we are and where we are going, we would like to formally invite you to Tuesday's Women in Drupal event. This event is open to all women, trans* individuals, those who identify outside of the gender binary, and allies.
Palantir: On the Air with Palantir podcast, Ep. 04: Everything You Need to Know About DrupalCon New Orleans
DrupalCon is just a few weeks away in New Orleans, so this time around our Account Manager Allison Manley is joined by our CEO and Founder George DeMet, Drupal veteran and PHP guru Larry "Crell" Garfield, and Senior Front-End Developer Lauren Byrwa. They share thoughts about the conference generally, what they're excited about specifically, and what they're expected from the Driesnote, among other topics.iTunes | RSS Feed | Download | Transcript
We'll be back next Tuesday with another episode of the Secret Sauce and a new installment of our long-form interview podcast On the Air With Palantir next month, but for now subscribe to all of our episodes over on iTunes.Heading to DrupalCon this year? On the fence and need to be convinced? Let's schedule a time to talk so we can explain why you should attend this conference.
Allison Manley [AM]: Hi, and welcome to On the Air with Palantir, a podcast by Palantir.net where we go in-depth on topics related to the business of web design and development. It’s April 2016, and this is episode #4.
I’m Allison Manley, an Account Manager at Palantir, and today we are going to give a preview of what to expect from the upcoming DrupalCon in New Orleans which is taking place May 9th through the 13th. The website is drupalcon.org if you want to see more. I’m a newbie to DrupalCon — this will be my very first one — so I gathered a bunch of my seasoned colleagues here at Palantir who have attended in the past to get their thoughts on the upcoming conference.
I am here with three of my fabulous colleagues that are going to be attending DrupalCon with me. So I have Lauren Byrwa, who’s one of our senior front-end developers.
Lauren Byrwa [LB]: Hi!
AM: George DeMet, founder and CEO.
George DeMet [GD]: Hello.
AM: And Larry Garfield, Senior Architect and Community Lead. How are you?
Larry Garfield [LG]: Hello, world.
AM: So what we’re doing here is basically a preview of DrupalCon. DrupalCon is coming up in a couple of weeks, in New Orleans, which is very exciting. How many DrupalCons is this for
each of you?
LG: I think this will be #21.
AM: Out of how many? How many have there been?
LG: Maybe 25? I’m a staple at this point [laughs].
GD: It’s a good question. Not as many as you, Larry, but probably, if I had to guess, between 15 and 20.
LB: I’m actually only at #2 for Cons. So not a whole lot compared to these guys.
AM: I’m a complete newbie, so we’ll get to that later — what I can expect — but before we get to what most people or new people can expect from DrupalCon, or what DrupalCon is about — we know that Drupal was started by Dries Buytaert. Did I pronounce that right?
LG: Close enough for an American [laughs].
AM: What is the correct pronunciation, please?
LG: Well, I’m an American too. ‘Drees Boy-thart’ I think is closer, but don’t quote me on that. Dries, feel free to correct us.
AM: I’m sure he will later [laughs]. So what is DrupalCon about?
LG: DrupalCon is the summit of the community. It is the largest Drupal in-person event in the world by a very wide margin. It’s a place for the whole community of whatever stripe to gather and discuss, learn, teach, plan, work, play, drink, and several other things along the same lines. A lot of conferences are very developer-centric or very business-centric, or very whatever. DrupalCon is — these days, DrupalCon is a Web conference with a Drupal angle to it. There’s sessions for back-end developers, there’s sessions for front-end developers, there’s sessions for project managers, there’s sessions for content strategists, there’s sessions for business owners — whatever you do, if it involves Drupal or the Web in some way, there’s at least a couple of sessions that are worth going to for you.
GD: I would agree, and I would say that even if you don’t do Drupal or you’re not someone who’s really immersed in the technology or the community, it’s still a conference with really great value. You can get a lot out of it, and I think particularly for folks who are new to DrupalCon, it’s a really great way to get immediately connected with the community. And it’s often a very overwhelming way. We’re a very friendly and welcoming community, sometimes overly so.
LB: I would like to think of DrupalCon as our family reunion, for all Drupalers. We’re there to learn, we’re there to share, but mostly we’re there to collaborate. And that can happen in sessions, that can happen at happy hour,that can happen anywhere. But it’s a great way to get plugged into the community.
AM: So I am a newbie, as I said — this will be my first. So what should I expect from DrupalCon? Am I just going to walk in and be completely overwhelmed at first?
LB: I think at my first DrupalCon — overwhelmed? Yes, definitely expect to be overwhelmed no matter what. But feel comfortable, feel welcomed. Everybody is excited for newcomers. Everyone is excited to get to know you, to hear your ideas. So stand up and talk, and listen, and ask questions. And go up to people that intimidate you, and tell them that you’re a huge fan and that you work with their tools every day and that you like what you saw in this blog post. And they’ll be flattered and want to know what you think and why or why not you agree or disagree. But talk to everybody. Talk to them on Twitter, talk to them in person, talk to them at bars — everything you can do to soak up as much information as possible. That’s always my number one.
LG: The main thing you should expect at DrupalCon is 3000 introverts playing extroverts, who really want to talk to you and teach you things because that’s what they do. And if you’re up for talking to people you’ve only heard of, or never heard of, and just learning from every person you run across, you’ll do just fine.
GD: And I think — so when we’re at our booth, every year without fail I’ll be standing there and someone will just kind of come up to me, and they’ll have The Look in their eyes. It’s very clear that this is their first time, they’re feeling very overwhelmed. And it’s really funny, this happens every time, they’ll make eye contact, come over to the booth, pull out their program guide, and be like, where do I go? And there’s so many different things you can do and places you can go and sessions you can experience, and it really is about — I think for folks who are going, it’s really taking a look at the sessions, figuring out ‘what do I want to get out of this event’, and focusing on that. And if you are getting overwhelmed, just find a friendly face, and they’ll more than likely be able to help you out and point you in the right direction – ‘oh yeah, I know the person doing that session, they’re awesome, go to that session if you want to learn about this, so-and-so is like the world’s expert on that’. All kinds of opportunities to just soak everything in, and learn what you can. It’s a really fun, really intense time.
AM: Great, I’m really looking forward to it. So every year Dries gives a keynote. And it’s fairly spectacular, I’ve seen a bunch of them on YouTube. They’re very involved. So what are you anticipating this year from the Driesnote, as he calls it?
LG: I have no idea what Dries is planning. I think the best keynote he’s given in recent years was in Amsterdam, where he was talking about actual practical changes to our process. That’s where he introduced the plan for putting credits on the site, which got implemented later. And I think that’s been a great thing to encourage contributions from companies and clients and commercial organizations, which we absolutely need.
I’d like to see something inward-looking. By that point Drupal 8.1 will have just come out, and that’ll be the first time we’ve done that type of release in, I think, ever in Drupal. So I suspect he’ll be talking about that and the implications of being able to evolve the system more smoothly than in the past. That’s my prediction, such as it is.
[this was cut from the original recording due to audio issues, but is left intact for the transcript]
GD: I’m hoping that Dries will take this opportunity to talk a little bit more about what the vision and future direction of Drupal is going to be, not just from a technical standpoint but really from an — answering the question, why does Drupal exist? What we’ve seen over the last few years, particularly as we’ve been through the Drupal 8 cycle, is that Drupal has changed and evolved tremendously. And at the same time the kinds of people that use Drupal, and the ways that they are using it, have changed tremendously. And I think that a lot of folks in the community have moved along with those shifts, but others might be feeling a little left behind, like they’re not really sure. Maybe if you’re somebody that’s joined Drupal at a point in the past, and you’ve had a particular motivation for doing so, the project and the community may be very different now. I think as we go through that change and that evolution, having a shared understanding and grounding in what our shared values are as a Drupal community and a project would be really cool to hear from Dries.
LB: I would say we’re actually at a place right now where we don’t entirely know what’s next for Drupal. We’re not waiting on D8 any more — there’s a whole slew of things out there. And so I agree that the future of Drupal is going to be a big topic. I think in addition to that, this is our good chance and this is Dries’ good chance to really press on contribution, and to recruit people.
A lot of our hardcore developers that helped build D8 are feeling a little burnt out. They too are celebrating the release, but in addition to that, they’re feeling a little burnt out after years and years of press to get it there. So I think contribution is going to be a really big topic this year — trying to figure out how to get people involved and how to get new blood in the system and new
ideas. To really push us towards that future, that’s going to be important.
AM: That’s a lot to cover in one keynote [laughs].
GD: The expectations are always incredibly high for these things. And it’s really often almost too much to ask, that one person will be able to cover this much in an hour or an hour and 15 minutes. One thing I’ve seen is that sometimes, when Dries delivers, he really delivers in a really great way. But I also know that it’s really hard to do that. So hopefully everything will click in place. I’m looking forward to it.
AM: Me too. So what are the big talking points in Drupal right now? Obviously I can assume Drupal 8. What else do you think will be the big things?
Zyxware Technologies: Question Bank for evaluating Drupal Developers as part of the Drupal Open Curriculum Initiative
We have been involved with the Drupal Open Curriculum initiative under the Curriculum and Training group in groups.drupal.org for the last few months and have been helping build up the content for the initiative. One of the important pieces of content that is expected to be developed as part of this initiative is the question bank with objective type questions that can be used to evaluate the progress of the training of Drupal developers.DrupalgiveDrupal TrainingDrupal PlanetTeaching DrupalNews
April 9 was a day filled with enthusiasm as we set forth with “The Drupal Global Day training” here at Valuebound. With a crowd of over 20 people and 5 trainers the knowledge sharing session was very fruitful.
The session started with an introductory note on Drupal to the diversified audience from different industries right from IT & ERP to Digital Marketing. Having gained the basics of Drupal, trainers encouraged the attendees to start with their first hands on experience of Drupal. The participants were excited to create their own website without using a single line of code.
The session was filled with lot of queries & heated discussions making it an interactive conclave. Drupal Global Training Day turned out to be successful when a large part of the…
The Supercache module is the result of an attempt to improve Drupal 8 efficiency when dealing with cache tag management and other design issues with several caching components that make it a pain to deal with Drupal 8 based applications that change a lot.
An out of the box Drupal 8 install will issue about 2,100 database statements for a simple task such as performing a log in and creating two articles.More articles...
- Drupal on IIS or Apache
- Adding native JSON storage support in Drupal 7 or how to mix RDBM with NoSQL
- Drupal 8 performance: the Supercache module
- Decent PDF generation in Drupal
- Using Heatmaps to boost conversions: Heatmap.me Drupal integration
- Database Transactions in Drupal
- Twig PHP extension binaries for Windows
- Making namespaced callbacks work in Drupal 7 (without hacking core and with bound parameters)
- When PHP crashes: how to collect meaningful information and what to do with it
- Setting up Code Syntax Higlighting with Drupal
Avoid common pitfalls when updating Drupal modules. The new Update Extended module takes the guesswork out of a few tricky situations where regressions can slip into your site and break working functionality, especially when using a dev release.Read More
A tell-tale sign that a website is a Drupal site is the login page. If you go to WEBSITE_URL/user of most Drupal websites the login form that you're presented with is almost always the default and very Drupal-looking login. Now there's an easy way to change that on Drupal 8.
In the first post in this series, What Is Distributed Content Management?, I defined two perspectives on that term: the distributed management of content and the management of distributed content. While doing so, I used the example of a large university and the need to consider both aspects of Distributed Content Management as part of an effective digital strategy for higher education. In today’s post I’ll develop that concept a bit further so we can discuss a few use cases in detail.
Setting The Scene
To ensure we’re all on the same page, imagine a large university. For fun, let’s call it “Drupal University.” Similar to many higher education institutions, the academic programs at Drupal University are split into multiple schools (let’s say 7) and each of those schools house a number of departments. Some of the smaller schools may only have 3 to 5 departments, but others, such as Humanities or the Medical School, may have upwards of 25. And let’s not forget that each of those departments is responsible for a number of different academic programs. Toss in the requisite assortment of research labs, student organizations and administrative departments - you can see how quickly our college’s web presence gets complex! At this scale we’re likely dealing with hundreds of different websites, all of which have requirements around content. It’s the perfect platform for Distributed Content Management! Let’s explore a few use cases that might pop up. Don’t worry, we’ll start with an easy one.
Use Case 1: Publishing Workflows For Individual Websites
For the web platform at Drupal University, this strategy is obvious. Unless they employ an absurdly enormous central communications team, large universities simply must distribute their content production. This doesn’t necessarily mean throwing open the gates! Consideration of a content approval workflow is a critical part of the content strategy for any organization that employs Distributed Content Management. Publishing workflows, whether manual or automated, must be tailored not only to the university, but to each school, department or group that’s in charge of a website. Content to be published on the undergrad admissions websites likely requires significantly more oversight than the blog of an 8-person research lab. The Medical School, with its 25 departments, probably has its own marketing and communications departments while a smaller school fights for the attention of centralized resources. This is definitely a case where one size doesn’t fit all.
Use Case 2: Sharing Content Out - Centralized Content On A Distributed Web Platform
Even the most decentralized universities have content that is centrally produced. In some cases it may be easiest to just hyperlink to that content in its original location; however, consider, a news story about a student winning a prestigious award. That story, produced by the Communications Department for the News section of the college’s main website, may be reposted in its entirety in numerous strategically advantageous places: the homepage of the student’s academic program, the websites for her research lab, a site run by Admissions, another targeted at alumni. Copying and pasting becomes a less efficient option the further content is distributed - more so when you consider the possibility of edits and possible unpublishing. In later blog posts, I’ll discuss some of the techniques and products organizations are using to efficiently share content across numerous websites.
Use Case 3: Sharing Content In - Decentralized Websites As Points Of Origin
Another interesting use case presents itself when we consider distributed websites as the starting point for content creation. Most universities maintain a central calendar of events, whether on a main website or in an Event Management System. In a well-formed distributed content model, with an an appropriate CMS like Drupal, the same metadata that allows visitors to filter events - audience, department, program, etc. - can be easily used to syndicate those events to various websites. Unfortunately, the same level of consideration is not always given to the publishing of new events. Because central event calendars feed information to the entire college, they are often protected systems, editable only by a subset of users with appropriate permissions. Content managers who are generally empowered to manage their own content may not have the same access to do so, or, in cases where they do have permission, find themselves needing to enter content into an entirely different system to get it published to their site. But why should this be the case? By extending the same technologies that allow websites to receive events from a central calendar, we can enable content managers to publish events to the calendar from within the same website they usually manage. (The same content approval and publishing workflow considerations apply, of course.)
Use Case 4: Integrating With Controlled Content Systems
At the far end of the Distributed Content Management spectrum are systems that need to publish consistent, controlled content to websites with no possibility for discrepancies across multiple sites. A common case of this in higher education would be a Course Catalog System (Acalog, SmartCatalog, CourseLeaf, etc.). One of the primary jobs of these systems is to integrate with the university’s Student Information System, providing the canonical description of a course, its contents, credits, costs, etc. If a university chooses to publish course descriptions on individual program sites, eliminating user error and neglect - mistakes made through copying and pasting, older content not being updated, etc. - is of great importance. As such, determining a strategy for directly integrating with these systems, rather than relying on a standard approach to decentralized content management, must be an important part of a university’s content strategy.
In my next post I’ll continue exploring use cases for Distributed Content Management but switch our focus to the pharmaceutical industry. Thoughts or questions? Reach out in the comments below or tweet them to me at @HankVanZile.
Tagged with Comments
With 15 years of experience in the Information Technology field, and 10 of those years focused on leadership, I’ve learned first hand the value of investing in people and setting them up for success. Before joining Mediacurrent, I started a QA department from scratch and grew it to its current size. Prior to that, I built an IT team. If you're an incoming leader, here's how to start building your own QA/IT department.
At Acquia India, 15 of us had enrolled ourselves in a self-guided D8 study group program. Most of us are developers who are very familiar with D7. Some of us are already working on full time Drupal 8 projects while some of us are trying out some pet projects.
The format of our study group looks like the below:
We meet for 20 mins in the morning every alternate day (Mon, Wed, Fri) to discuss the activity card of the day
We disperse and then complete the prescribed exercise offline during the day
Often, we discuss the challenges or blockers from the day’s exercise on the next call
We have built a set of Activity Cards for this program. These cards assume you are very familiar with D7 and will cover topics that have significantly changed between D7 and D8. Each Activity card consists of:
A small objective
Some cards have an additional secondary tutorial / reference material and a bonus exercise
The exercises are crafted so they don’t take more than an hour to complete after reading the prescribed primary tutorial. Sometimes, they do take longer though.
These cards could be a great learning tool for small teams that might want to form a similar D8 study group.
These cards were built by a small team learning D8, than by someone who has already mastered it. So the could be prone to errors. Drop a note to me or comment here, if you see any errors in the cards, or if you have any suggestions on any of the cards, or if you wish to collaborate with us in building new cards.
The cards are available here. An embed of the doc is right below here. We have around ~10 cards as of date. We will keep adding more cards to the collection as our study group progresses.
Cover Pic Courtesy: http://blogs.lawlib.widener.edu/
Acquia Developer Center Blog: Drupal How-To: Adding Images to Your Site. The Basics, and How to Tweak the Defaults
In this 3-part Drupal How-To series, I'm going to show you how various options for configuring images on your site.
Here, in Part 1, we'll see how to tweak the default image options. In Part 2, we'll see ways to allow WYSIWYG and inline images. In Part 3, we'll see the latest options for responsive images.Tags: acquia drupal planet
Ever since Drupal 6's End-of-Life on February 24th, there have been countless blogs and articles about why you should upgrade to Drupal 7 or 8 as quickly as possible.
But this may be the only article arguing that you SHOULDN'T upgrade from Drupal 6! ;-)
If you have a complex Drupal 6 site, and you haven't started the upgrade process yet - contrary to conventional wisdom - the best answer may be: keep waiting.
No, this isn't an April Fools joke, and we're not being sarcastic. :-)
Want to know why? Keep reading!
Evolving Web is heading down to DrupalCon New Orleans this May. This will be the first North American DrupalCon since Drupal 8 was released, so excitement will be in the air.
With Drupal 8's release, lots of new Drupal projects are being planned. As part of DrupalCon, we'll be leading a Drupal Project Management Training on May 9th.read more