Drupal Planet

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 43 weeks 5 days ago

Blink Reaction: Everything First

Wed, 2014-02-26 07:35

“Mobile first” is perhaps the hottest buzzword in web development today, but we as an industry are still struggling to articulate just what “mobile first” means. How does that influence your projects? Are there specific rules to follow? Or does it simply mean always giving mobile users first consideration at all phases of the project?

Categories: Drupal

ThinkDrop Consulting: Introducing HubDrop.io: bridging the gap between Drupal.org and GitHub

Wed, 2014-02-26 07:02

NOTE: This blog post cross posted from http://blog.hubdrop.io/2014/02/08/the-future.html

This project is simply something I wanted to do. No one paid for it. I built it in my spare time as a way to refine the knowledge I learned over the last few years about Symfony, Vagrant, and Chef. I want to grow this tool, but it takes time and a server, which both == money.

So I'm opening up a GitTip account to raise funding for development of hubdrop.io.

But before I do that, I wanted to formally introduce HubDrop to the Drupal aocmmunity.

What is HubDrop?

HubDrop.io is currently a tool that mirrors Drupal projects on GitHub. In the future it will do all sorts of magic things with your git repos.

It was also a learning experience for me, and hopefully it will be for others. I hope to use HubDrop's code as a lesson in building web services.

In the future, I want put together a detailed case study and document the process of building the entire HubDrop service for all to learn from.

HubDrop is also a part of the Drupal community. There is a lot of debate about the drupal.org tools, and the effort it takes to improve them. There was a huge discussion of moving to github outright, years ago. The idea for hubdrop was to act as a bridge, so we don't have to decide for everyone what tool they must use for development, and can maybe get the best of both worlds in the meantime.


I've got some important ideas that I believe in. This project is a tool for the community, and I've come up with these three principles to keep it that way.

  1. HubDrop will always be 100% open source.
  2. Mirroring of public open source code and site projects will always be free.
  3. HubDrop will always strive to survive on community funding, plus revenue from mirroring private repos.

We'll see how it goes. I am a cynic idealist. If the funding comes in, there's so much that can be done.

Future Features

There are a number of features that I am sure everyone is thinking of. Here is my priority list:

  1. GitHub to Drupal sync.

    This will allow projects to move development to GitHub, while maintaining a mirror on drupal.org for releases, presence in the community, etc.

    This is already working for the "drupalprojects" organization, but I have to run a command on the server to do so. This is a very tricky feature because you have to decide who gets commit access.

    I have this working as well, and I'll write more about it later, but the point is, the next step is letting developers create their own repos in any organization, and plug it into Drupal's git service. This part will require some work because there is no database in hubdrop and I'd like to keep it that way.

  2. Private 3rd Party Mirroring (and merging)

    By which I mean, mirroring your Pantheon, Acquia, or other git host repo on your own GitHub account or organization, private or public.

    I already set this up as a test by messing with the pushUrl and it works, but its lumped in with the contrib projects. Also this depends on feature #1 because we need some kind of authentication to set this up.

    The merging part is mainly for Acquia Cloud. We could let devs keep their drupal code in the root of their repo, and automatically sync it to your acquia cloud repo, which must keep drupal atdocroot.

  3. Drupal Core Update Merging

    What if you could give hubdrop access to your repo, and, whenever there was a core update, it could make a branch of your master and apply the update for your review? Basically what Pantheon does but for any drupal repo.

  4. Drush Make and Distribution Repos

    Using drupal/drush make-driven-drupal-development? Want to, but don't want to teach your devs to build the site all the time?

    Got a distribution that drupal.org packages?

    HubDrop could track changes to your makefile, and sync that with a full drupal site repo, making for more flexible development and distribution.

All the things

I'll end with a tweet from a fan. HubDrop has already inspired a meme.

While I don't see a need for mirroring all the things, I do think the freedom for developers to develop with the tool they prefer is an important freedom to have.

My hope is that this tool will bring more people together to improve code for all.



Sync all the modules! http://t.co/5db358ZyUw #drupal pic.twitter.com/71gVpXwy11

— Dave Hall (@skwashd) December 1, 2013 Tags: Planet Drupalgithubdrop
Categories: Drupal

Drupal Association News: Drupal.org team week notes #21

Wed, 2014-02-26 06:17

Drupal.org improvements

During the past two weeks we deployed a few Bluecheese issues (#2191021, #2194421, #1195950), accessibility issues (#2095969), Project issues (#2195621, #2184161, #2125307, #2193857, #2159429. Thanks to LewisNyman, mgifford, cafuego, tim.plunkett, trobey and Mark Carver for working on them.

Categories: Drupal

InternetDevels: Ctools access plugin creation for Panels

Wed, 2014-02-26 03:22

Some time ago we've learned how to develop ctools content type for Panels module. Now it’s time for the next plugin type for Ctools, namely - access plugin.

Read more
Categories: Drupal

Modules Unraveled: 097 The Kalamuna (Bootstrap) Theme with Mike Pirog - Modules Unraveled Podcast

Wed, 2014-02-26 02:14
Published: Wed, 02/26/14Download this episodeKalatheme
  • What is Kalatheme?
  • Does this play nicely with Panels/Context etc?
  • I don’t actually have any experience with Panels In Place Editor. What functionality does that provide the theme?
  • What version of Bootstrap are you using?
  • Is Sass-ability built in?
  • On the Project Page, it says you can use other Bootstrap themes. How does that work?
  • You mentioned a subtheme generator. What is that? How does it work?
  • Is this a base theme that people should sub-theme? Or can people use it out of the box.
  • What are the Drush commands that work with Kalatheme?
Use Cases
  • What do you see as the target audience for Kalatheme?
  • Do you know of any sites using Kalatheme that we can look at?
NodeSquirrel Ad

Have you heard of/used NodeSquirrel?
Use "StartToGrow" it's a 12-month free upgrade from the Start plan to the Grow plan. So, using it means that the Grow plan will cost $5/month for the first year instead of $10. (10 GB storage on up to 5 sites)

Episode Links: Mike on drupal.orgMike on TwitterSass Kalatheme on githubKalatheme demo videoKalamuna.comKalatheme Project PageTags: 
Categories: Drupal

Chapter Three: Sharing Drupal

Tue, 2014-02-25 22:59

As the Drupal project matures, new technologists surveying the landscape of available technologies may not pick Drupal as their platform of choice. Chapter Three has met this challenge by encouraging people at the beginning of their careers to explore Drupal and share our love of the platform.

Two years ago, Terence Yang showed up at the BADCamp registration table on Saturday morning and ended up being a stellar volunteer for the entire weekend. The one request he had at the end of the camp was to learn more about Drupal.

The following summer Terence and the Bay Area Video Coalition approached Chapter Three to see if we would be interested in hosting Terence as an intern for their BRIDGES program.

The decision was easy to bring Terence on as an intern. We know from past experience that community volunteers make a great addition to our office.

BAVC's team of videographers Chris Pizarro and Nelson G. Navarrete created a short documentary describing Terence's experience at Chapter Three.

Categories: Drupal

DrupalCon Austin News: March 7; it's the final countdown

Tue, 2014-02-25 15:56

Only 7 precious days remain until applications close for sessions, training, and scholarships at DrupalCon Austin. Help us spread the word about this deadline to your co-workers, user groups, and twitter following-- DrupalCon Austin is shaping up to be our biggest conference yet, and you can help us ensure anyone has a chance to be part of it!

Categories: Drupal

DrupalCon Austin News: So, you want to train at DrupalCon

Tue, 2014-02-25 15:29

Prior to each conference, trainers submit proposals and the training selection team, a global and local track chair, work with the Program Coordinator to select the trainings that will be offered. Many top-quality proposals aren’t selected, simply because there are more potentials submitted than can be offered. To make the path to training more clear, here are some insights into the selection process and how to best present your training for consideration.

Categories: Drupal

Palantir: Supporting the Local Drupal Community at MidCamp

Tue, 2014-02-25 10:33

One of the ways that Palantir gives back to the communities that support the open source tools we use is by helping to organize and sponsor local and regional events. One upcoming event that we’re very excited about is MidCamp, a three-day celebration of all things Drupal here in Chicago March 28-30.

MidCamp is a brand-new Drupal event designed to educate and engage Drupal users and evaluators throughout the Midwest. It will feature three days of training, curated sessions, and sprints for those looking to increase their Drupal knowledge and for the opportunity to rub shoulders with internationally-renowned Drupal experts.

One of those experts is our own Larry Garfield, who will be co-presenting MidCamp’s Saturday keynote along with Lullabot’s Jeff Eaton. They’ll be providing a tour of the upcoming Drupal 8, talking not just about its new features but also its new philosophy.

For those looking for a more in-depth look, Palantir will be offering two half-day training sessions on Friday for Drupal site builders and module developers who want to be able to hit the ground running with Drupal 8 once it’s released.

And with several Palantir team members having proposed sessions for MidCamp and planning to participate in Sunday’s sprints, you’ll be sure to see some of us around all three days of the conference.

Located at the University Center in downtown Chicago, MidCamp is situated within walking distance of many of the city’s tourist attractions, restaurants and nightlife.

But what sets MidCamp truly apart is that it is a community effort, organized and supported by volunteers and sponsors from a wide variety of companies and organizations throughout the region. Among those volunteers is our own Andrea Soper, who is leading the planning team. Other Palantir team members helping out with various aspects of the event include Nate Striedinger, Bec White, and myself. In addition, we’ve also thrown our financial support behind the event as one of its Gold-level sponsors.

Whether you’re an existing Drupal user, developer, designer, site builder, or are someone new to the community, you won’t want to miss out on MidCamp. Visit www.midcamp.org to learn more and purchase your tickets today.

If you’re interested in sponsoring the event or submitting a session proposal of your own, act now, because there are only a few days left.

We look forward to seeing you there!

Categories: Drupal

Mediacurrent: Meet Peter Mallett

Tue, 2014-02-25 08:30

1. So Peter, what's your role at Mediacurrent, both internally and client-related?

I am a "Drupal Developer", so I take care of site builds, writing custom modules, consulting on how to accomplish clients' goals, and a bit of theming here and there. 

2. We're so glad to have you!  Give us an idea of what professional path brought you here.

I got started with computer programming when I was in high school, then was exposed to Web development right after. With the exception of a few side-quests, this is what I've been doing ever since.

3. How did you first get involved with Drupal?

Categories: Drupal

Drupalize.Me: Drupal 8: Start Contributing with the Drupal Ladder

Tue, 2014-02-25 08:23

Here at Drupalize.Me everyone is contributing time to Drupal 8. For my part, I'm turning my attention back to the Drupal Ladder. I was heavily involved in this project when it started a few years ago, and it remains a great resource for bringing people up to speed on the technical aspects of contributing to Drupal Core. The Drupal Ladder is a collection of lessons—organized step-by-step like a ladder—that walk you through the basic tools and processes used by the Drupal community. If you want to contribute to Drupal 8, the Drupal Ladder is an easy place to start, and your first step should be the Drupal Core Ladder. (There are numerous ladders for different topics; stick with the Core ladder initially.) Here are two ways you can dive in:

Categories: Drupal

Digett: Why I Love Pantheon for Drupal Hosting

Tue, 2014-02-25 07:55

We have been using Pantheon for several months now and I am ready to declare it a strong winner for us. If you haven't experienced it, Pantheon is a hosting platform that is optimized for Drupal.

read more

Categories: Drupal

Acquia: Ryan Weaver and Jeffrey A. McGuire compare notes on Open Source

Tue, 2014-02-25 07:44

Ryan Weaver is the single biggest contributor to the Symfony2 framework's documentation (which is excellent, check it out!), a self-described Symfony evangelist, and lead at KnpUniversity.com, makers of fantastic PHP tutorial screencasts like this one on using Composer to include PHP libraries in Drupal 7.

Categories: Drupal

Mark Shropshire: Charlotte Drupal Drive-in Wrap-up

Tue, 2014-02-25 05:50

Last Saturday (February 22nd, 2014), thirty-one Drupalers joined together at Classic Graphics for the Charlotte Drupal Drive-in. The day was full of presentations, BOFs, and general chatting about Drupal and related web technologies.

The day-long, un-conference-style event was the brainchild of Thomas Lattimore. After CharDUG wasn't able to pull together the human resources to repeat the success of DrupalCamp Charlotte 2012, Thomas mentioned that he had an idea. Since he knew organizers had limited time to commit to planning, he wanted to host an un-conference-style event, allowing for simpler planning than a full-blown Drupal camp. You can learn more about his concept on the DruaplEasy Podcast.

The event started with breakfast goodies, a welcome to the event, a thank you to our sponsors, and session pitches. The list of pitched ideas quickly grew to enough items to easily fill the day with sessions in two rooms. The group decided to plan the morning sessions by splitting beginner and advanced topics in separate rooms. The organic nature of the event and Classic's space allowed for the beginner session to split into two rooms when it was clear the group had different needs and questions.

Morning session topics included, contributing to Drupal, beginning site building and theming, integrating Drupal and Meteor.js, and a combined talk about options for dev, staging, production workflows.

During lunch (sponsored by the Drupal Association, attendees enjoyed chatting about the previous sessions and meeting each other.

Command Partners provided a $100 iTunes gift card to giveaway after lunch. Thanks to deekayen for using his Randomizer module to determine the winner!

Next, we planned sessions for the afternoon. Most attendees stayed in our larger room where we had a number of great topics, including Aegir, Acquia Lift, the Demo Framework, and Features. In addition to the main sessions, a group started talking about Open Atrium 2 in small conference room.

The event ended with a wrap-up to talk about what we learned and any lingering questions. Everyone I heard from during the wrap-up and following the event had great things to say about the format. They really liked the organic nature of the event.

From my perspective, the event was a success. The format allowed for a relaxed atmosphere where beginner and seasoned Drupalers alike were able discuss their projects, ideas, and questions. While much of the group was from the Charlotte metro area, we also had attendees from the Atlanta metro area, Boone, NC, Tryon, NC, and High Point, NC.

Some kudos from attendees:

"I really liked the splinter rooms.. it was nice to even start a session in one room and split from there based on what." - Angel Cox

"Awesome. I liked that we built an agenda on the fly using feedback from the group, and that many of the sessions came from users who had pretty specific "how do I do X?" type questions. My favorite presentation ended up being a sort-of group lead discussion on how different people are doing dev-staging-prod release cycles within their organizations. Having a local Acquia employee give (the first!) presentation on Lift was amazing." - Jeremy Edgell

I would like to thank Classic Graphics, the Drupal Association, and Command Partners for supporting the Charlotte Drupal Drive-in. Also, thanks to all those who attended and led sessions. I see a repeat of Charlotte Drupal Drive-in in 2015 in our future!

Thanks to Josh Lockhart for the photos. See more here.

Blog Category: 
Categories: Drupal

Pronovix: Managing paper and virtual loyalty cards with a Drupal site

Tue, 2014-02-25 01:49
/*-->*/ /*-->*/

We have just finished developing a loyalty program system for a Belgian coffee shop, so we thought we could summarize what we’ve learned to help Drupalists working on similar projects.

Loyalty programs are structured marketing efforts that reward and encourage loyal buying behavior. The owner of a loyalty card is identified as a member in the loyalty program who is entitled either a discount on the current purchase, or an allotment of points that can be used for future purchases.

Categories: Drupal

DrupalCon Austin News: project management, team management, communication and strategy sessions wanted

Mon, 2014-02-24 16:49

If you've ever been involved in a digital project of any complexity, you know that project success depends as much on the human factors like communication, accountability and organizational processes as it does good code. In fact, some have said that without good process, you cannot have good code.

Categories: Drupal

Lullabot: Module Monday: Synonyms

Mon, 2014-02-24 14:00

Drupal's Taxonomy system has offered the ability to store synonyms for almost a decade. When the term 'Chicago' is defined as a category, for example, Drupal allows you to add 'Windy City' as a potential alternative. What Drupal doesn't do, however, is use that synonym anywhere. That's where the Synonyms module comes in.

Categories: Drupal

Acquia: Drupal 8 Module upgrade workshop at Drupal Developer Days in Szeged

Mon, 2014-02-24 09:12

Gábor Hojtsy, Jesse Beach (jessebeach), and Jess (xjm) will lead a Drupal 8 module upgrade workshop during Drupal Developer Days in Szeged, Hungary.

Categories: Drupal

Phase2: Static Prototyping and Keeping Drupal Simple (KDS)

Mon, 2014-02-24 09:10

If you ask any Drupal developer about their favorite tools, the probability of Views and Panels being in that list are absolute. They are part of the top 100, and with good reason. They provide GUI tools for querying and layout customization.

They also, however, introduce complexity behind-the-scenes.

The technical debt involved with preprocessing views templates or creating custom panel layouts is hard to justify for projects that have small budgets, tight timelines, or hyper-specific design requirements.

One approach is to have a front-end developer interpret flat designs to DOM output introduced by the implementation. While this is common, it adds technical design debt as you deal with unneeded repeated elements, missing HTML5 tags, and unstructured CSS.

You also introduce QA headaches as the gap between what is designed in Photoshop and what is implemented lies solely on subjective design eye.

I believe a better approach is to use static prototypes and manipulate Drupal to the desired DOM using core API functions.

I call it Keeping Drupal Simple (KDS).

Let’s explore the KDS philosophy as well as some implementation techniques.

Business Goals

Every decision should be tied to a stated business goal. The ‘what if’ scenarios of users, both visitors and site administrators, being able to interact with the options Drupal can provide generally push budgets.

Although being able to think of all scenarios is something developers pride themselves on, most business goals can be solved with specific definitions of success and simpler technical solutions.

One way to focus this effort is to ask the right questions. Instead of asking ‘Do you need to be able to do x?’, follow the principles of Agile and ask ‘What business goal is solved of being able to do x?’

This subtle change allows developers to redistribute their efforts from feature rich technical implementations to high value client experiences. It also forces the client to think about the true value of a feature request as it relates to their audience.

This results in reevaluating the need for modules, like Views or Panels, because site configuration priorities are lower than the design and content creation priorities.

Below are four questions I ask when implementing KDS:

  1. What is the business value of editors being able to change the layout / have a dashboard / administer X type of content?
  2. How do you define a successful site visitor experience?
  3. When do you plan for your content creators to create real content and give you feedback?
  4. What business value is lost if X feature is moved to a Phase 2 or 3?
Project Evaluation

It goes without saying that this approach does not work for every project. Evaluating the needs of your client, the project constraints, and the abilities of your team through proper discovery is essential. KDS may work for you if:

  • The project has a small budget and timeline
  • There is a lack strong front-end acuity on the implementation team, either from availability, skill or budget
  • The front-end team knows [insert front-end framework], but not Drupal
  • Site configuration and layout will remain mostly static after launch

Not all of the above factors are required. If your project does satisfy a majority of the conditions, I would consider KDS.

Static Prototyping

One of the driving factors of cost is design interpretation. Based on a given a PSD design or wireframe set, expectations are set with the client about look, feel, and interaction.

The cost to bridge the gap between what is possible on the web and what is designed can be vast.

This can be mitigated by designing in browser and starting with HTML prototypes. Providing a simple static homepage and interior page can set the proper expectations of menu interaction, block placement, and feedback in various browsers.

Thankfully, methods like style tiles and atomic design take this even further by providing a common design relationship between elements.

This accelerates the on-boarding of new project developers because the styleguide contains both design and DOM conclusions.

The static prototype also becomes the source of truth for all decisions.

  • Being able to explain in concrete terms what elements of a page will and will not have user-defined configuration goes a long way to keeping deliverables within budget.
  • Work is also done in parallel, decreasing inefficiency.
  • Front-end developers communicate ideas via static prototypes to the client while also optimizing their DOM and CSS.
  • Backend developers develop functionality that produces the prototype DOM.
  • The challenge  becomes bending Drupal towards that markup goal.
  • When applying the static prototype within Drupal, the theme becomes the meeting point. Base themes tend to get in the way and add extra markup or classes, so starting from scratch is best.
  • The best way to build a theme from a static prototype is to take your interior page and set it as the page.tpl.php. This gives you a starting point to start swapping static components for dynamic Drupal components.
  • As you swap, you can compare the output of your theme to the static prototype and provide an iterative QA piece for the team.

Some best practices include:

  1. Creating a html.tpl.php and swap out the contents in the <head> tag
  2. Swapping the area where a menu would be for themed menu output via menu_navigation_links()
  3. Combining the static homepage prototype elements and wrap them in a conditional that be set in template.php
  4. Swapping sidebar areas for regions and hard-code them temporarily in template.php to check output

Using your prototype in your tpl files provides an added bonus of only needing to swap out areas if something is dynamic. This accelerates your pace to the deliverable as you’re not bogged down with parts of the DOM that will never change and, thus, do not need rendering from the Drupal ecosystem.

 API Over Everything

The most important technical implementation philosophy developers need to remember when implementing KDS is to always try to use core API. The reason isn’t because 3rd-party modules are bad.

The reason is because 3rd-party modules have assumptions that can lead to technical debt. Many times, budgets are blown because of the work you have to do to undo a default assumption.

For example, if a static prototype homepage has a listing of content, the delivered DOM may use the article HTML5 tag to segment out the content from the rest of the site.

If you build that listing with Views, you’ll have to:

  1. Build the view with the right conditions
  2. Export the view to code
  3. Preprocess the view or create new tpl files
  4. Work to ignore or work-around the extra DOM included from Views
  5. Hope the requirements of the view doesn’t change
  6. Hope the client doesn’t change anything in the Views interface

Conversely, you can use EntityFieldQuery to grab your listing and theme the results in a custom theme function with the exact DOM desired.

In template.php:

/** * Implements hook_preprocess_page(). */ my_theme_preprocess_page(&amp;$vars) { if (drupal_is_front_page()) { $variables['page']['content'] = my_module_listing(); } }

In my_module.module:

/** * List nodes for homepage. */ function my_module_listing() { $query = new EntityFieldQuery(); $query->pager(10); $result = $query->execute(); $output = array(); $nids = array_keys($result['node']); $nodes = node_load_multiple($nids); foreach ($nodes as $node) { $output[] = theme('my_module_listing_single', array('node' => $node)); } $output[] = theme('pager', $query->pager); return implode('', $output); } /** * Theme a single element in a listing. */ theme_my_module_listing_single($vars) { $output = array(); $node = $vars['node']; $output[] = '<article>'; $output[] = "<h1>$node->title</h1>"; $output[] = "<p>$node->desc</p>"; $output[] = '</article>'; return implode('', $output); }

You now have eliminated technical debt from the Views ecosystem and eliminated design debt due to new DOM elements.

While this isn’t a critique on the exporting UI workflow, do take time to consider the impact of multiple environments, multiple developers, multiple iterations of development, and a tight timeline.

What happens to your budget when there is a conflict?

What happens to your scrums when clients want to know what ‘that button does’?

The goal is to deliver high business value, in a limited scope. This, consequently, reduces the likelihood of scope creep introduced by additional configuration options. This also forces the team to concentrate on the business values communicated at project start.

Not sure which API functions to start with? I recommend starting with these 30.


Some frequently asked questions I receive of ‘Why’ or ‘How’ when it comes to KDS technical implementation:

Q: How do I place blocks, if not by the UI?
  • Create an update hook and place the block delta directly in the table
  • Use Context and hook_context_default_contexts().
Q: What happens if I need to update a field or setting, if not by Features?
  • Review the Field API and update through an update hook.
  • Also, Features are great! I’m not knocking Features. Maybe consider using it as a way to stub your update hook with the proper configuration array through the Feature export and piping that into your install / update hook.
Q: What about initial WYSIWYG configuration, Pathauto configuration, or some other common configuration?
  • See answer above.
Q: Seriously, though. Why would I do this when a module does this for me?
  • Code requires commits and commits provide a history. Having a history of what was changed is good. It helps team members and it helps project managers in tight deadlines and budgets. History gives you a breadcrumb trail of work.
  • Learning the Drupal API also gives you confidence of how things work under the hood. Troubleshooting is easier if you know the execution processes behind those buttons.
Don’t Forget Content Creators

Here are a few 3rd-party modules (and caveats) that align with the easy content authoring objective:

  • WYSIWYG – CKEditor 1.13
  • Asset Management – Media 1.4
    • Include these two patches
    • Ensure that the jQuery version is <= 1.7 as there is a bug that breaks the media browser in 1.8
  • Simple Workflow – State Machine 2.2
    • Out of the box, every node goes through a simple draft => published workflow
    • Overrides are done via code only
  • Youtube, Vimeo Integration – Video Embed Field 2.0-beta7
    • Link to a video that turns into a field
  • SEO – Metatag 1.0-beta9
  • Sidebar Elements – Bean 1.7
    • Custom types can be added via code only
    • Fields can be added to block types via the form API

I haven’t had a chance to use Edit or the other recommendations in the Spark distribution. I’ll try to post an update to KDS once I’ve had a chance to evaluate it, especially since it’s in Drupal 8.

KDS is designed to strip down the implementation plan of a Drupal solution from the discovery process to the technical implementation. It’s not a one-size-fits-all nor is it a critique on popular modules like Views and Panels. It’s main goal is to provide a philosophy of simplicity inside the complex world of a Drupal project.

Please let me know what you think!

I’m curious to hear the community’s feedback and if others have found other ways to keep projects streamlined.

In the meantime, learn more about everyone’s favorite module, Views in Chris Johnson’s blog post “Customizing Views With Context!”


Categories: Drupal

Stanford Web Services Blog: Getting Started on Sites: How do I remove the "authoring information" on my page?

Mon, 2014-02-24 08:43

By default, Drupal displays author and date for each node (e.g. "Submitted by Caryl J Westerberg on October 17, 2013 - 8:43 am").  That works great for a blog, but may not be appropriate for all types of content. 

Here's how to remove authoring information:

Categories: Drupal

Powered By