Planet Drupal

Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 34 min 48 sec ago

Midwestern Mac, LLC: DrupalCon Austin 2014 - Notes on my First Timer's Guide

Mon, 26/05/2014 - 21:50

I wrote A First Timer's Guide to DrupalCon two years ago, and 99% of the advice in that post is still relevant. I've been preparing my presentation DevOps for Humans: Ansible for Drupal Deployment Victory! for a few months now, and since DrupalCon is less than a week away, I thought I'd take a few minutes to supplement the earlier post:

Categories: Elsewhere

Hook 42: Prepping for DrupalCon Austin sprints: Sprint leads, component maintainers, experienced contributors & mentors, update core issue queues this week!

Mon, 26/05/2014 - 21:40
Monday, May 26, 2014 One week to go!

It’s hard to believe that DrupalCon Austin starts in a week. Woohoo! We’re excited to have 5 of our team members going… 3 of them (Lindsay, Marc & Patrick) have never been to a DrupalCon before and I’m sure they’ll have a great time with sessions and BoFs and parties and their very first sprints. For the first-timers, don’t miss the Get Involved with Core and Contribution Sprints on Friday where you can get the help you need to make Drupal better while having a fun time with the community (and remember to stick around for the extended sprints on the weekend too ;). For those of you with issues you want help with, read on…

Are you a sprint lead? Core component maintainer? Experienced contributor? Mentor?

tldr; Please update issue summary remaining tasks, link to contributor task documents, note which are novice tasks, and add "needs" tags.

Community members at DrupalCon Prague. Photo credit: Josef Jerabak.

Every DrupalCon, we have attendees from all walks of life, from all skill levels, and from all over the world come together to learn and share and hang out with our amazing Drupal community. This diversity is great since it provides an opportunity for more experienced community members to focus on more complex issues while mentoring newcomers to help out with tasks at their level and interest. We are very lucky to have a large group of key contributors, mentors, and knowledgeable community members who’ll be spearheading the Austin sprints. If you are interested in mentoring, please sign up to mentor… we’d love more help.

Sprints, sprints and more sprints!

DrupalCon is definitely not a 3-day event… come join us for sprints on the weekend before and after DrupalCon (for extended sprints), from Monday through Thursday in the Coder Lounge, and on Friday for the Contribution Sprints. Check out the sprint sign up sheet if you haven’t already.

So far, there are about 20 (!) focused sprint topics planned. If you want to focus on a particular part of core or a community ("contrib") module that’s not listed on the signup sheet, just add it to the list. While many have chosen a group to sprint with like D8MI or the Drupal Media Initiative, there are still a number of sprinters who are open to working on any topic.

Drupal.org sprint at Drupal Developer Days Szeged. Photo credit: TCPhoto.eu.

If you can’t attend DrupalCon Austin, we’ll miss you at the sprint tables, but you can still sprint as a remote member of the team! Just sign up and mark yourself as a remote sprinter. All help is appreciated and you can experience a part of DrupalCon from the comfort of your own home. ;)

With lots of sprinters, too!

While there will be a lot of sprints going on, we’ll have plenty of sprinters to help out. Austin will have between 300 and 600(!) new contributors and about 300 experienced contributors. That’s a lot of motivated sprinters... so let’s get ready to do this!

We want to get prepped so that everyone can hit the ground running and not trip over each other. ;) For the new recruits, we will need a good amount of well-defined novice issues to keep them productive and happy. This is where we need the help of mentors and experienced contributors. (But! We do not want to turn the whole issue queue upside-down and know you are busy getting ready for Austin. If experienced contributors update just a few issues each, we should be fine.)

First, let's consider: who are the new contributors? New contributors are knowledgeable about their areas of interest but they might not be familiar with the Drupal core contribution tools and process. And, some will be new to Drupal as well.

Why do we try to match new contributors with novice issues? Working on a real task on a real issue which really helps Drupal, but is doable in a short period of time, gives new contributors a chance to learn the Drupal contribution tools and process without having to focus on challenging architectural overreaching epic problems. A good novice task gives people a first successful contribution experience and empowers new contributors to move on with other issues in the future.

Let’s get organized!

Ok, we’ve got lots of sprints and lots of sprinters. Great! You veterans can help make sure that the right issues make it to the people with the most appropriate skills to contribute to the issue.

DrupalCon Prague sprints. Photo credit: Amazee Labs.

Even for the most experienced developer, the Drupal issue queue can be a pretty daunting thing at first glance, especially if someone has never been involved in a full issue resolution lifecycle. Leaders in the community can prepare the issues for clear assignment, and mentors can get the new contributors familiarized with the issue process.

Smooth execution of an issue resolution helps get the time sensitive issues done. Hiccups and variations in the issue process can disrupt community members that are focused on priority or difficult issues. So, for example, while we want to encourage contribution, a beta blocker is not a good first-Drupal-contribution issue.

We don’t want non-novice tasks being tackled by novice contributors since they are new to the contribution process. And, we don’t want experienced contributors doing novice tasks when they could be reviewing issues or working on issues that need their expertise and experience. To better achieve this goal, we can update our issues this week so they are well tagged and have an clear, accurate list of next steps.

To quote YesCT:

...the combination of adding tags, and updating the issue summary remaining tasks section with a links to contributor task documents makes it really easy for someone new to Drupal or new to an issue to know what the next steps are and how to do them…Let’s Get Queuing!

Step 1: Re-read the issues you know about.

Step 2: Update the remaining tasks section to accurately reflect what still needs to be done. Link each remaining task to the appropriate contributor task document so there is plenty of context for the sprinter. The remaining tasks template is helpful. (Dreditor has an issue with a build to add a button to help with this.)

Step 3: Tag the issue with "needs" tags, e.g. "Needs tests", "Needs issue summary update", or "Needs manual testing". Use established tags from the list of "needs" tags. Don't make up new tags.

Step 4: Identify which of the remaining tasks might be good for someone new to contributing to Drupal and mark them novice in the issue summary. See What makes a good Novice task on drupal.org.

Note: the entire issue does not have to be novice. Identify specific tasks within an issue that are small, well-defined, and doable. (Avoid issues that are long, contentious, or urgent, even if they have some potential novice tasks.)

Not all tasks are novice. Some rerolls are difficult; some issue summaries are difficult; some manual testing is difficult, etc. When marking a task Novice, consider that we want new contributors to do to be able to get the task done.

Step 5: Tag issue with "Novice" tag if there are any novice tasks. Remove the "Novice" tag from any issues that do not have novice tasks.

Step 6: Add additional, established tags that give further context to the issue. Tags can express information like: issue topic (e.g. Usability), initiative (e.g. D8MI), and skill level (e.g. Novice). (Typically, focus information (e.g. sprint, beta target) is added or subtracted from issues by initiative leads or maintainers.)

Tagging like a pro

If you want help on the issues you care about, tagging issues well is the best way to get there. Be sure to use individual tags rather than long compound ones.

For example:

DON’T: Drupalcon austin sprint novice usability needs manual testing

DO: sprint, Usability, Needs manual testing

The Drupal.org issue tagging docs are a great place to learn how to tag like a pro but here are the highlights:

  1. Use existing Drupal.org issue tags and be consistent with other core issues. For example, "Configuration system" is used for configuration management issues (not "CMI").
  2. Add established special use / "needs" tags like "Needs usability review".
  3. Add established topical tags like "CSS" and "Accessibility".
  4. Use consistent capitalization and formatting, and avoid special characters.

Mentors will be using the issue tags to find issues appropriate for both the new and experienced contributors. Tag wisely! ;)

Learn more…Getting new contributors to help outMore about DrupalCon Austin sprintsThanks for the feedback! :)

Committed by: Kristen Pol, YesCT, aimeeread, xjm

This blog post was born out of a request from Cathy Theys (YesCT) on a weekly Drupal 8 Multilingual Initiative meeting. Cathy has been a fantastic mentor in the Drupal community and wanted to give the community some tips for Austin. She has been busy doing lots of other awesome community work so we are happy to help voice her wisdom and experience to the greater Drupal community.

Cathy. Photo credit: Josef Jerabak.

Thanks to Cathy, Jess, Aimee, Gábor & Nathaniel for pointing us at the great wealth of community resources, providing notes in IRC and Google docs, and reviewing and finetuning this blog post! It takes a village to raise a Drupal. :)

If you have more resources or tips to share, please leave a comment.

See you in Austin! Sprints for the world! Woohoo! Kristen Pol Topics: Tags:
Categories: Elsewhere

Doug Vann: Top Ten Things To Bring With You To DrupalCon! Austin!

Mon, 26/05/2014 - 21:19
This is a shameless RERUN of last year's post which was enjoyed over 9.5K visits and apparently helped a LOT of people. So here it is AGAIN! :-)

Are you going to Austin for DrupalCon 2014? You're about to enjoy 3,000 PLUS ppl getting their Drupal on! This will be my 7th year at DrupalCon. 
I've devised this TOP TEN list of THINGS TO BRING, from the experiences I have had.
ALSO: Look below to see what ppl added to the list last year! Let me know if this comes in handy! Be sure to add your packing preparation advice if you have something to contribute! ;-)
 

[1] COMFORTABLE SHOES
Seriously!
You're going to be doing a LOT of walking wether it's in the convention center OR in town.
If you buy new shoes BREAK THEM IN BEFORE you leave.
Also, consider some comfortable inserts for your shoes. 


[2] MOBILE POWER PACK

Don't find yourself stuck with a dead mobile phone. I use the Motorola Universal Dual-Charging Portable Power Pack [pictured right] Don't count on having access to a power outlet at the event to keep your devices charged. I leave the power pack plugged into my phone either in my pocket or in my bag. I'll typically do this after lunch so that I have plenty of power for the evenings.


[3] BUSINESS CARDS
And PLENTY of them!
Maybe you don't own a business or run a big freelance operation, but either way, you need something to give some one to remember you by. You're going to meet a lot of people and some of them you will want to keep in touch with. Do yourself a favor and get in the habit of giving out a card when you meet someone. Just get your name, number, web-address, email address, what your skills are, your twitter handle, LinkedIn url, etc. Make it easy for people to stay connected to you! 


[4]GOALS
Make a written [or typed] list of what exactly it is you want to accomplish while at DrupalCon. Do you want to learn some very specific skills? Do you want to understand the mobile web better? Do you want to exchange cards with representatives of higher-ed organizations? Maybe you want to spend time at the booths of each Drupal shop and checkout employment opportunities?
Whatever it is you want to do, MAKE A LIST and check it each and every day of the event. 

[5] YOUR HIT LIST!
Who do you want to shake hands with while you're there? A famous podcaster or module maintainer? While I don't want to promote stalking or anything... It is reasonable to take advantage of the fact that we're all in the same place for a couple of days.

Make a list of some of the people you want to THANK for their tireless work to make Drupal awesome. Don't hesitate to walk up to the people you admire and appreciate and say hello. There are no ROCK STARS in Drupal! [OK. I guess there really ARE!] But, regardless, you should feel very comfortable reaching out to any one. If you need to, ask someone you know to introduce you. I'd be happy to do that for anyone! ;-)

[6] PEN & PAPER
Don't underestimate the power of the written word.
You're going to have times where you want to write something down without booting up a mobile app or your laptop.
You're also going to want to write something down on your business card before you hand it out OR write something on someone's business card when they hand it to you. 

[7] YOUR STORY
Every one has a story. Be prepared to share some of yours. You will certainly be asked some or all of the following questions:
What do you do with Drupal?
When/How did you discover Drupal?
How long have you been doing Drupal?
How have you contributed?
What brought you to attend DrupalCon?
 

[8] CURIOSITY
I don't recommend bringing a multi-million dollar Mars research robot with you, but you should bring some good ol' fashion CURIOSITY to DrupalCon
You're going to be surrounded by immense talent and knowledge covering more topics and areas than you can digest in the short period of the event.
I encourage you to wander off into uncharted territory and expand your horizons! 

[9] WARDROBE
This may sound like a no-brainer, but here are some tips.

Bring more than you think you need. You may discover that you want to change between the day events and the evening events.
Pack some options. You may discover a group that wants to hit the beach, or go hiking, or go swimming, or go dancing.
Seriously... I can't tell you how many events I've been to where amazing opportunities pop up to have some fun! Don't let your wardrobe hold you back! 

[10] ROOM FOR SWAG
OK. I know I already have you packing upwards of 200+ pounds of stuff for DrupalCon but there's just one more thing to consider.
You're going to get a LOT of free T-Shirts AND there will also be opportunities to buy some stuff as well. So PLZ PLZ PLZ plan on a cary on or extra room in your bags for SWAG!

There you have it! I hope this helps you out. 
I look forward to your feedback! :-) 

Drupal Planet

View the discussion thread.

Categories: Elsewhere

Drupal Easy: Don't Be Afraid! We'll Walk You Through It! Migrate in Core Testing Sprint at DrupalCon Austin

Mon, 26/05/2014 - 20:47

Getting involved with Drupal core development is scary. There's a lot of really smart people involved and it can be intimidating. The learning curve can be steep and an "easy" task can turn into hours of frustration. Your inner voice tries to convince you that you don't know enough to contribute to Drupal core, and your fear of embarrassing yourself has you referring to Drupal core contributors as "them" instead of "us".

Luckily, the Drupal community provides a cure for all this. DrupalCon sprints. Imagine a day where the entire community comes together looking (stalking, perhaps) for new contributors, regardless of their skill level, sits them down at tables with some of the most experience developers in our community, and takes the time to take them from zero to productive in less than a day. Sound exciting? It should - and if you're going to be in Austin next week, then there's only one place you should be on Friday, June 6.

-->

read more

Categories: Elsewhere

Ryan Szrama: Getting to work on a stronger Drupal Commerce 2.x

Mon, 26/05/2014 - 18:49

I don't like being sandy but I love building sand castles. The potential is high but the stakes are low. You have unlimited raw material to build whatever you can imagine, and if you screw up you can just knock it over (to the delight of your children) and start again.

When your constant is impermanence, you adjust your expectations accordingly. If the sands shift or the tide rises, you shrug it off and start again or go back to bocce. However, if you were somehow bound by the fruit of your labor, you'd think twice about the when, where, and how of your building.

Lyle and I started developing Ubercart when Drupal 5 was still in beta, and we put up with the impermanence because we were just two dudes learning a lot and working from a clean slate. Moving that forward to Drupal 6 took even longer because our codebase grew unwieldy, so I decided at Commerce Guys to trim the fat and start over. We didn't learn every lesson moving to Drupal 7, though, as it was still unstable when we began developing Drupal Commerce. With an unstable Views module. And an unstable Rules module. And an incomplete Entity API.

I don't think we would've done any differently, as the flip side of the instability is the opportunity to positively impact the development of the projects you depend on. For Drupal 8 we ended up contributing to core in other ways while tackling a full Drupal Commerce rewrite more slowly than we hoped. Even the code that we did develop against Drupal 8 is now outdated, as we had to juggle managing our existing ecosystem, writing new code, and rewriting that code to track changes in Drupal 8 itself.

However, we've recently been given the opportunity to host a variety of developers / documenters in Paris from June 30 - July 4 to re-evaluate our Commerce 2.x roadmap with the direct help and guidance of key members of the Symfony project. Specifically, we'll be looking to both move our code "upstream" from our Drupal modules into generalized Symfony bundles and take advantage of existing Symfony projects where possible.

Our target is an even leaner codebase with connections to the broader world of PHP based eCommerce. If you have any insights in this direction, please comment or contact me directly and consider joining us in Paris to learn and contribute.

Categories: Elsewhere

Drupal Easy: Our Big (even by Texas standards) DrupalCon Session

Mon, 26/05/2014 - 17:07

It’s no secret DrupalEasy’s commitment to Drupal talent career development is as big as our passion for Drupal itself. What’s not been so conspicuous, is the role of so many organizations that share that commitment, many of whom support dozens of our students with mentoring, internships, jobs and referrals. Their stealth ends in Austin.

We are so happy to announce (and lure you to) our Texas-sized panel of awesome Drupal talent-focused players who will be enlightening us at the Drupal Career TrailHead; Embark on a Path to Success business track lab session at DrupalCon. The team includes insightful executives, living case studies, career experts, and recruiters for Drupal’s fastest growing organizations that represent what is and what will be coming down the pike for Drupal talent in the US and abroad.

Nancy Stango, CEO of BlinkReaction, will charge up the session with her take on where growth is the greatest, and where you should be focusing your talents to steer your career toward opportunity-rich niches. Nancy knows a little bit about growth; having just hired 35 excellent Drupalers to Blink over the past few months, and comes to DrupalCon with one mission; to hire 35 more.

-->

read more

Categories: Elsewhere

Dries Buytaert: Drupal 8 Q&A session at DrupalCon Prague

Mon, 26/05/2014 - 16:54
Topic: DrupalDrupalCon

Do you have questions about the upcoming Drupal 8 release (or Drupal 9 and beyond)? On Thursday, June 5 at DrupalCon Austin, I'll be moderating a question-and-answer core conversation with a panel of key Drupal 8 contributors. Questions are submitted in advance online, and anyone can submit a question. I will curate the submissions to ask the panel the most interesting and relevant questions.

This is a rare opportunity for the community to communicate directly with the trailblazers who are shaping Drupal 8 into the best release of Drupal yet. Help us make the most of of it -- submit your questions now!

Categories: Elsewhere

Drupal core announcements: Beta blocker deadline target what? A quick guide to Drupal 8 release management tags

Mon, 26/05/2014 - 15:58

Drupal 8's feature freeze was over a year ago, and we are close to releasing a Drupal 8 beta to provide testers and contributed module authors with what they need to prepare for Drupal 8.0. What does this mean for issues in the core queue? When we look at Drupal core issues, we should ask two questions:

  1. Is this issue worth holding up the entire Drupal 8 release (no one can use Drupal 8 until it's done)?
  2. If not, what deadline does it have?

Here's a guide to how we organize issues based on the answers to these questions.

Critical issue priority
In the Drupal core queue, issues with the critical priority must be resolved before we create a Drupal 8 release candidate. These are the issues that will hold up Drupal 8's release--for a week, a month, however long it takes--even when everything else is ready. The Drupal 8 branch maintainers are currently reviewing issues to decide which will and will not block release. (See the criteria for critical issues.)
beta blocker issue tag
Beta blockers are critical issues (we would not release Drupal 8 without them being resolved) that are needed to provide a stable data model and stable critical APIs. (See Dries' explanation of the beta criteria.) Only the Drupal 8 branch maintainers should add this tag.
beta deadline issue tag
Non-critical issues (we would not hold up release for them) that significantly change the data model or critical APIs, and therefore can only be committed before the first beta is released. If they're not finished by the time the beta is ready, they must either be postponed to Drupal 8.1.0 or Drupal 9.
beta target issue tag
Beta targets are issues that we prioritize for the beta release, but that are not critical and therefore will not hold up the release cycle. These issues might also go into beta2, beta3, etc. if they don't also have the beta deadline tag.
rc deadline issue tag
Issues that are not critical but can only be committed before the first release candidate is released (for example, an Approved API change). If they're not finished by the time the release candidate is ready, they must either be postponed to Drupal 8.1.0 or Drupal 9.
minor version target issue tag (new!)
Add this tag to issues that might be good candidates for a Drupal 8.1.0 or another minor release, like new features, major UI improvements, etc. Consider whether beta or rc deadline issues could fall in this category. (See the Proposal to manage the Drupal 8 release cycle for more information on minor versions.)

Note: There is no "rc blocker" or "release blocker" tag. The critical issue priority indicates release blockers. Non-release-blocking issues marked "critical" will be downgraded.

So that's Drupal 8's release management in a nutshell! Help us release Drupal 8 to the world as soon as possible by focusing on the most important changes, and think about which improvements can wait for Drupal 8.1.0 or be done in a contributed project.

Categories: Elsewhere

Gábor Hojtsy: Drupal 8 multilingual tidbits 16: configuration translation development

Mon, 26/05/2014 - 15:46

We learned how configuration translation works on the conceptual level and through the Drupal 8 built-in user interfaces in the previous article of the series. In this article, we'll cover how can developers integrate with configuration translation.

Explaining the structure of configuration

We used your main site configuration file as an example in the previous article. Let's review that again (system.site.yml):

uuid: ''
name: Drupal
mail: ''
slogan: ''
page:
  403: ''
  404: ''
  front: user
admin_compact_mode: false
weight_select_max: 100
langcode: en

There are clearly some translatable elements here. Which ones? Well, at least the site name and slogan would be. How would Drupal know though? There is nothing in this file to tell Drupal about that. There is also no code in handling this configuration that needs to deal with that. We wanted to introduce language support in the most transparent way. Instead Drupal supports a static description format to describe the structure of configuration, that we call configuration schema.

Categories: Elsewhere

OhTheHugeManatee: Drupalcamp Helsinki Takes on the World

Mon, 26/05/2014 - 15:14

Last weekend I got to keynote Drupalcamp Helsinki with my friend and often-collaborator, scaragucc – and what a great camp it was! Organizer Lauri Eskola deserves tremendous credit for taking this camp to the next level. They doubled their attendance from last year, attracted positive attention from some great notables in the global Drupal world, and got their local community energized to engage more. At all the various after parties there were frequent toasts of “one of the best Drupalcamps in the world!”

Lauri and I met at the last Drupal Dev Days event, in Szeged. That was also hailed as an example of a hugely successful Drupal event, and he took the lessons from their in-depth report to heart. To be fair, the local volunteers and sponsors also clearly busted their humps getting people registered, and finding good session speakers to work with.

The result was a really positive Drupal event for all of us. Their attendance shot past the 200 mark for the first time, their code sprint had more involvement than ever before, and their social activities were a huge success. We left Finland full of positive feeling for the local association there, the city of Helsinki, and of course the sauna culture! This was a great example of what a Drupal community event can be. I’m looking forward to next year already.

Categories: Elsewhere

Don't Panic: A blog about Drupal: Drupalstatus.org - A new star on the Drupal sky

Mon, 26/05/2014 - 12:59

For long, I've been using Droptor to get an overview of all my Drupal sites and it's a powerful service that not only gives you an overview but also statistics of your content and several checklists (security, performance, SEO and health) to see how your website is doing. It's great and much needed, but there isn't happening a lot at Droptor. I've submitted several suggestions on how to improve their service and they have applauded them, saying that these suggestions will come in newer versions of Droptor but then ... nothing.

Categories: Elsewhere

undpaul: How to convince potential customers to use Drupal

Mon, 26/05/2014 - 12:02
We are always on the lookout for new clients. And there are many clients looking for services like ours. Some clients know they want Drupal. Others still have to be convinced. Especially here in Germany, we have to compete against TYPO3, because it's an established content management system for the enterprise. We believe Drupal is similar or superior to what TYPO3 and others can accomplish, but it's not easy to convince others about it. In order to win a client, you might list some advantages of Drupal and show some of the sites you've built with the system. However, you can't show the backends of most sites you've built for clients and a plain install of Drupal is not very convincing.   A demo system is a great way to show the potential of Drupal, but creating your own is time-consuming to build and maintain.   Gladly, Acquia provides a free demo distribution called Demo Framework. The demo is a personalized, multilingual platform with modern responsive capabilities including previews for different devices. With its beautiful interface and sample commerce and multimedia integration, it's perfect to show just what our favorite content management framework Drupal is capable of. drupal planet english
Categories: Elsewhere

Vasily Yaremchuk: Anchors Panels Navigation Module

Mon, 26/05/2014 - 11:57

Several years ago I have a dream to put my own personal site into One Page solution.
Due to I'm Drupal developer Drupal was selected as platform for my site.
Thus Single Page Website Module was done.

This module is some kind of out of box solution. One can turned it on, do several settings on the module settings page and have One Page website on Drupal CMS engine.

But due to architecture of the module it has a lot of significant restrictions that will be difficult to resolve. The main problem is the limited number of themes that people can use with that module. By the fact Bartik theme and it's subthemes only works correct with the module. This issue connected with some automatic actions that module should perform with page template to make it One Page site.

There are a lot of other issues and limitations that restrict significantly abilities of Single Page Website module. There is no any multilingual support and there is no ability to set two One Page Landings, there is no ability to have link in menu that go to the separate Drupal or external page and so on, and so on...

The talk about weak and strong points of Single Page Website module is out of scope of this post, I'm ready to provide my thoughts but in the other post that will be created soon I hope :-)

The topic of this post is Anchors Panels Navigation Module. What made me make a second approach to the One Page site on Drupal? I think that if we can use higher layer of abstraction in the architecture we can avoid any theme dependence. But we should find some kind of wrapper to combine our One page site from different content parts.

I have used Panels module. If you would like to create some Landing Page with anchor navigation inside it, please use Anchors Panels Navigation module. Please use development version it should works, but some decoration moments I should finished before an official release.

There are several simple steps that you should do to obtain One Page site on the base of Panels with anchor navigation:

  1. Turn on Anchors Panels Navigation module. Panels, Panel nodes and Ctools are required also.

  2. Create several pages with content that you would like to have on One page Panel
  3. Create Panel an put nodes that you did on previous step into the Panel areas.
  4. For each region that you would like to have anchor set CSS id in Panels settings.

  5. Put several links to created Panels node with anchors equal the IDs into any Drupal menu. You can have some other links in that menu too.

  6. Now you have Landing Page with anchors. The module does not provide any CSS altering of the page so to set your menu in fixed position you should do some CSS changes manually. I found CSS Injector module is helpful to set some specific CSS rules on the separate Palels page.

The results here: http://apn.yaremchuk.ru

Feel free to ask any questions and send any ideas about that approach. Thanks!

Blog tags:
Categories: Elsewhere

Web Omelette: New features for Block Inject

Mon, 26/05/2014 - 09:01

I've worked recently on some new features for my contrib module Block Inject and I thought I'd share with you what's new.

Based on some feature requests from the community, I've implemented two new things that make this module more flexible. They are available in the 7.x-1.2alpha5 release onwards.

Theming

First, the injected region is now wrapped in a <div> with some default classes on it for easy styling. I've also created an alter hook for this so you can add easily your own classes there depending on the $node object the region is injected in.

An example implementation of this hook:

function hook_block_inject_attributes_alter($attributes) { if ($attributes['node']->type == 'article') { $attributes['attributes']['class'][] = 'article-block-inject'; } }

The $attributes parameter is an array with two values: the node object and another attributes array that gets transformed into HTML attributes by the drupal_attributes() function.

Site building

The second new feature of the module is the possibility to specify default paragraph offsets for an inject region depending on some conditions related to the node body field.

For example, when creating the inject region you can set it so that the region gets injected 5 paragraphs lower than the middle if the total number of paragraphs is over 20. Or move the region higher by 2 paragraphs if the total number of paragraphs equals 6.

Feel free to check it out and let me know what you think.

In Cool Modules | Drupal var switchTo5x = true;stLight.options({"publisher":"dr-8de6c3c4-3462-9715-caaf-ce2c161a50c"});
Categories: Elsewhere

PreviousNext: Drupal 8 Now: Composer dependencies in Drupal 7

Mon, 26/05/2014 - 08:39

One of the key goals of namespaces in PHP is to avoid collisions between class and function names between different libraries. Using namespaces and the PSR-0/4 standard creates a clean and simple way of sharing code across projects. This is a core part of the Drupal 8 architecture.

This approach has been a large factor in the PHP Renaissance and the huge amount of sharing of code across PHP external libraries.

In this post, I will show how we can leverage external libraries in existing Drupal 7 sites, using similar techniques to how it is being done in Drupal 8.

Categories: Elsewhere

Gizra.com: The @amitaibu show (unplugged)

Sun, 25/05/2014 - 09:00

Wait, what? Did you actually think I'm going to be in a DrupalCon without giving a presentation? Oh, the fact that my session was not selected made you think that. I see. I can understand how that could have caused the confusion.

So the thing is that I have a presentation titled "The Gizra Way" that I've been giving for the past year all over Israel, and recently in DrupalCamp Spain. Reactions were pretty good.

My prediction is that most watched #DrupalcampEs video will be @amitaibu session as soon as it is available. Really inspiring!

— penyaskito (@penyaskito) May 17, 2014

We are still looking for a place to do it. Maybe in a BoF room. Or in the staircase. Or a bar near the hotel. And you know what? I'm really excited about this idea. It feels like I'm preparing for the unplugged version of my show. Anyway, we'll tweet the time and location once we find the place.

Continue reading…

Categories: Elsewhere

Drupal Association News: Next Drupal Association Board Meeting: Live and in-person at DrupalCon Austin

Sat, 24/05/2014 - 18:44

Twice a year we get the opportunity to hold our monhtly Drupal Association board meetings live and in-person! We are more than excited to get to Austin to greet old friends and meet many new ones. While we're (mostly) all there, we hope you'll join us for the June board meeting. We''l be in room 10B on the third floor of the Austin convention center at 11:45 am. Lunch will be served there, so no need to battle the lunch lines downstairs before you join us.

For those of you who can't join us in Austin, you can still join us remotely, as per usual. 

What's on the agenda this time?

  • An abbreviated Operational Update from staff. We normally provide metrics and full narratives for all the areas of our work. Because this meeting is so early in the month, we are unable to provide those metrics. We'll catch you back up in July.
  • Presentation of the 2013 Audit. All the news is back from our auditor and we are ready to share the findings with you.
  • Updates from the Drupal.org Working Groups. They'll share what they've been focused on and what's coming up.

All the materials for this meeting are available in the public board folder for this meeting. Looking forward to your questions and ideas!

Flickr photo: Erik Mallinson

Categories: Elsewhere

Jeff Beeman: Light-weight solution to provide custom view modes and suggest related templates in Drupal 7

Sat, 24/05/2014 - 18:43

When it comes to providing custom view modes for entities in Drupal, most developers turn immediately to Display Suite or Entity View Modes. Display Suite is very powerful, but I've found it to be far too "heavy" for most of my use cases. In this case, by "heavy" I mean that the module days way more than I need it to. It does a lot of things I simply don't want on my site. Entity view modes is a lighter-weight approach to supplying additional view modes, but I found that even it was cumbersome when it came to managing my view mode configuration in an easily-deployable way.

I wanted a simpler solution, and I knew it couldn't be that hard to provide this functionality in a custom, streamlined module.

The code snippets below do the following:

  • Define new display modes. As you'll see, this is super easy to do in code.
  • Suggest node templates based on the view mode of the given node. e.g. a teaser template vs. a full display template.
  • Suggest page templates based on the node type being viewed. e.g. alter the page markup for Article nodes.
Categories: Elsewhere

DrupalCon Austin News: ATX Hack for Change: One Weekend, Infinite Impact

Fri, 23/05/2014 - 23:32

Just before DrupalCon Austin, you can join Austin changemakers and techies for a weekend of high-energy hacking, snacking and good will at the Austin Hack for Change.

Categories: Elsewhere

DrupalCon Amsterdam: Call for Site Building Sessions

Fri, 23/05/2014 - 18:43

The Drupal 8 release is getting closer, and with it we keep hearing more and more questions about it. Share your Drupal 8 knowledge with the world at DrupalCon Amsterdam: the Site Building Track Team is calling for sessions, and we want YOU to help us out.

We are looking for proposals of sessions focused on Drupal 8. Our goal is to get everybody updated on the current status of Contrib Module 8 Status. There will even be a special two hour session which will allow Drupal 8 Module Maintainers to give a short update about the status of their modules.

If you're interested in giving a 12 minute session about your module, talk to Schnitzel or post it as a comment here.

As we all know, DrupalCon is about more than just Drupal 8, so let’s not forget Drupal 7 and 6! With Site Building we can achieve and build great sites without needing to code-- and since there are a lot of ways to reach a goal, let’s share the knowledge, and teach each other how to achieve great things. Are you using a module in really cool ways? With real life examples? Propose a session!

A special focus will also be set on layout modules. There are a lot of modules which allow us to position content on a Drupal Page. Let’s compare and analyze them, so everyone will know what each module is for and can decide for what to use them. Are you proficient with a layout module? We love to hear about it!

Submit a Session

--
The DrupalCon Amsterdam Site Building Track Team
Michael Schmid (Schnitzel), Amazee Labs
Ivo Van Geertruyen (mr.baileys), One Agency

Categories: Elsewhere

Pages