Planet Drupal

Subscribe to flux Planet Drupal
Drupal.org - aggregated feeds in category Planet Drupal
Mis à jour : il y a 35 min 13 sec

Cheeky Monkey Media: What's up with User Pathways Design ...?

jeu, 01/09/2016 - 18:36
What's up with User Pathways Design ...? Spela Thu, 09/01/2016 - 16:36

A user pathway (sometimes called user flow and user journey)  is the path a visitor takes on your website before completing the action you would like them to take.

You can tackle the user pathway, after you have completed your user research and user personas.

Here's how ...

Setting the Stage for the User Pathway Step 1 - Determine what your Macro and Micro goals are 

For example, as a business solutions company that specializes in web development and design, and marketing communication, the final goal we would like visitors to our website to take is to contact us with a project or challenge they need help with.

As a nonprofit, your final goal might be to get a donation, a registration, or a contact form filled out.

Catégories: Elsewhere

Annertech: Places to Visit outside of Dublin while at DrupalCon

jeu, 01/09/2016 - 17:23
Places to Visit outside of Dublin while at DrupalCon Coming to DrupalCon Dublin but planning to travel around Ireland a bit? Previously we blogged about our top recommendations to see and do in Dublin, but I know some of you are planning to stay for longer and so here are our recommendations for places to visit outside Dublin.
Catégories: Elsewhere

ThinkShout: See No Email, Hear No Email, Speak No Email

jeu, 01/09/2016 - 15:00

Listen up, Drupal savvy MailChimp fans. We’ve got some news for you: MailChimp recently rolled out a newer and more robust version of their API - MailChimp API version 3.0! Now I can probably guess what you’re thinking so I’ll just come out and say it: this means MailChimp’s API version 2.0 is about to become deprecated, and we’re not monkeying around.

For those of you using the 8.x and 7.x-4.x branches of the MailChimp module, feel free to sit back and relax - you are already using MailChimp’s API v3.0. Those of of you still using the 7.x-2.x and 7.x-3.x branches, get ready: API v2.0 will be phased out on December 31st, so we encourage you all to upgrade.

Don’t be a furious George - we’ve got you covered. Our documentation up on Drupal.org has been updated, and we’ve provided information that will help make your upgrade experience as seamless as possible. We’ve even included a shiny new FAQ page this go around. For additional support, feel free to post questions on Drupal Answers.

Alright, let’s get down to monkey business. Those of you who upgrade are about to have a module that is regularly maintained, has an improved infrastructure (see the README.txt on the 7.x-4.x branch for more info), and can be integrated with the new MailChimp E-Commerce module (more on that in a future blogpost) - now, that’s something to go bananas for!

Catégories: Elsewhere

Drop Guard: Free Drupal security for a good cause

jeu, 01/09/2016 - 11:00

Being casual about open source security is not funny. Headlines like the Panama Papers this year showed that an improvident dealing with security and updates can cause a huge damage. Fees are still a crucial reason for people to hesitate to secure their business by using charged services. This is not a pitty - this is grave.

There are many people out there who give a lot without receiving a reward. They see more benefits in helping and strengthen people, any kind of living being or purpose than in a regular salary.

Drupal Drupal Planet Security announcements non-profits Drupal Community
Catégories: Elsewhere

ImageX Media: The Top Five Ways Drupal 8 will Benefit your Business

mer, 31/08/2016 - 21:41

Drupal 8 includes more than 200 new features and enhancements for developers, and there’s been no shortage of information on the technical advantages of upgrading.

Catégories: Elsewhere

Aram Boyajyan: Changing user display name in Drupal 7 and Drupal 8

mer, 31/08/2016 - 21:15
Changing user display name in Drupal 7 and Drupal 8

Every website that displays user information on the front end will use profile fields such as first and last names for representing the members. By default Drupal shows only the username, which is definitely something you will want to change.

Modifying this is relatively simple. You could always choose which fields to use in Views, Rules and other modules, but the main problem is maintenance - the setup will be spread across many different pages and it's not the most optimal solution in the long run.

The right way is to change the way user display names are formatted by the system itself. This article will show you how to manage this for both Drupal 7 and Drupal 8 in your custom code.

aram Wed, 31/08/2016 - 21:15
Catégories: Elsewhere

myDropWizard.com: Drupal 6 security updates for Flag!

mer, 31/08/2016 - 19:49

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Moderately Critical security releases for the Flag module for multiple Access Bypass vulnerabilities.

The module includes a view that lists each user's bookmarked content as a tab on their user profile. The permissions on this view are setup incorrectly, allowing any user who has permission to use the 'bookmarks' flag to see the list of content that any user has bookmarked.

See the security advisory for Drupal 7 for more information.

Here you can download the patch for 6.x-1.x or 6.x-2.x!

If you have a Drupal 6 site using the Flag module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

Catégories: Elsewhere

Mediacurrent: Converting a Drupal 7 Site from Straight Css to Use Node.sass

mer, 31/08/2016 - 16:02

Or, just adding this setup to your current theme, even if it is Ruby...

Catégories: Elsewhere

WDTutorials.com: Drupal 8 Tutorial #44 : CKEditor CodeSnippet Module

mer, 31/08/2016 - 11:45

With CKEditor CodeSnippet module you can insert code snippets with syntax highlighting into the editor.

Catégories: Elsewhere

Jim Birch: One or Multiple. Make a Bootstrap Carousel from a Multiple Value Drupal Field

mer, 31/08/2016 - 11:20

Earlier this week I wrote how to create a Bootstrap Carousel using the Drupal Paragraphs module.  We can modify this approach to add a Bootstrap Carousel on a field.  I use this most on nodes that have a Featured Image field, one where we can use as a hero image, and one where we can set the Open Graph Meta image on a per node basis.

Thanks to social media outlets like Facebook, LinkedIn, and Twitter, every piece of content published to the web should have an image attached to it, define by the og:image meta tag.  But what happens when the content has or deserves more than one image?  If the field allows multiple, we can display them as a carousel/slideshow.

While I am discussing images in this blog post, this technique could be used for any type of field.  And even though I develop using the Bootstrap front end framework, the same theory could be applied to other frameworks and javascripts like the Slick carousel.  You would just need to change the markup to fit your specific framework.

So, all we need is a multiple value field.  Once we have defined which field that is, take a look at this markup and replace your template's markup with it.  The file name would be field--FIELD-NAME.html.twig

Read more

Catégories: Elsewhere

Unimity Solutions Drupal Blog: Strategies for Revenue Streams for Digital Publishers

mer, 31/08/2016 - 11:00

Coupled with increasing literacy rate publishing industry in India has seen tremendous growth in the past decade. Contradicting the global trend, in India the Newspaper industry has seen 8% growth last year. Most of this growth is driven by vernacular newspapers. It is expected that in the next decade regional newspapers grow at a rate of 12-14% as primary source of information. Although there is an increase in the adoption of digital books, digital news is yet to be accepted by Indians. 

Catégories: Elsewhere

Drupal Association News: MarCom changes, and how we’ll keep moving forward

mer, 31/08/2016 - 02:47

This post is part of a series about recent changes at the Drupal Association.

Like each of the Drupal Association teams, Marketing & Communications (MarCom) has a broad range of responsibilities. Our job is to persuade and sell, but also to inform and educate. About our work. About yours. About what it’s like to be part of this community.

We contribute to more than 20 Association programs and products, like Membership, Supporter Program fulfillment, and DrupalCon support. Day-to-day community engagement—via Zendesk, Twitter, Facebook, issue queue, etc.—is part of each of those.

It’s a feat that’s always been impossible without help from community members like you. There’s the work Dave does in the content issue queue. What Paul and Alex do on our social accounts. And what Jess, catch, Gábor, David, Michael, and many more do to coordinate releases. There’s more than we can count.

But it’s also a feat we used to have more staff to handle. A year ago, we were a team of five. After retrenchment and reorganization, we’re a team of two. As we support and advance the Association’s initiatives to increase Drupal adoption, we have to make hard choices.

First, an apology

We’re sorry. This isn’t just business; our work is for you. We think about the impact it has every day. Having to stop doing some of that work—even the work some may consider little things—isn’t something we take lightly.

If we don’t have a sticker shipping budget, it may impact the energy you create at a meetup. If we don’t support Global Training Days, maybe the next would-be contributor in your region isn’t inspired to learn Drupal. And if we don’t share stories of grant recipients, maybe you don’t know that your membership dues make an immeasurable difference in people’s lives. (They do, by the way.)

So, if we let you down, we’re sorry. Your trust is invaluable to us. We try to earn it every day.

But we must decide Criteria

The Association has two priorities:

  • Create sustainable financial health
  • Get more organizations with large, complex digital ecosystems—government agencies, publishers, universities, etc.—to choose Drupal

This means prioritizing revenue-generating initiatives. It means changing, or adding to, some of the user experience on Drupal.org—to better present Drupal as an answer to the questions our new primary audience has. And it means amplifying stories that persuade that audience to make Drupal part of their systems.

Clarity

We have a lot of work to do. And we won’t be able to do it alone. For those reasons and more, we need to make a promise about the content we publish.

We started on the following content strategy statement based on insight from our leadership. It describes our goal, methods, and primary audience in relation to each other.


Slides available on Google Drive

Clarity gives us the best chance to be efficient, effective, and consistent. So, we’ll keep narrowing that statement. It’s an important step toward giving the content we create—or ask others to create—a chance to live up to a shared potential.

Capacity

What can two people do or coordinate well? What can we complete and sustain?

A team that churns out content but doesn’t, for example, regularly pause to evaluate each thing it creates—that doesn’t turn that knowledge into insight for what it makes next (or doesn’t)—isn’t doing its job well.

Our decisions about what work we will and won’t do aren’t just about what we can somehow make happen. They’re about what we can turn into sustainable growth.

What we’ll do

There are products and programs that are critical to our identity. We’re not a membership association if we don’t have a membership program, for example. Then there are mission-critical initiatives. Drupal.org (D.o) is an incredible platform, so promoting Drupal without using the site would undercut our mission. And there are fiscal health requirements, like DrupalCon ticket sales.

So, most of our work will stay on our to-do list. It’ll just be prioritized differently. These are the areas of work that either stay mostly as-is or grow:

  • Drupal marketing and communications (e.g., release support)
  • D.o content management of promoted areas (e.g., the planned homepage refresh and “Drupal for industries” content)
  • DrupalCon marketing and communications, and sponsor and partner fulfillment
  • Membership (for people and organizations)
  • Supporter Program fulfillment
  • Jobs.drupal.org marketing and communications
  • Camp engagement (we’ll create a 2017 camp kit before January; promise)
  • Elections support
  • Association communications, generally (e.g., writing and editing posts like this)
The work we won’t

To make the work we’ll do possible, there’s work we can’t give as much attention.

There’s work we, unfortunately, won’t do at all.

  • Help build new D.o Sections (the initiative Tatiana led is paused for now)
  • D.o content management of areas that aren’t being promoted
  • Support the Drupal Store (its inventory will be liquidated)
  • Share Community Spotlights
  • Manage assoc.drupal.org content (the subdomain will be phased out)
  • Promote our webcast series

And there’s work we’ll reduce or others will lead.

  • Global Training Days (we’re setting up a community working group to coordinate it)
  • Advertising content production (we’ll depend on designers we trust)
  • Email newsletters (we’ll send fewer than the four we do now)
  • Sticker distribution (we’ll bring them to DrupalCons, but won’t ship them around the world)

This process will be fluid. As we adjust to these changes, these work lists may change again. If so, we’ll let you know.

How can you help?

If you help the Engineering and Events teams by giving back in ways Tim mentioned or contributing as Rachel suggested, you help us too. But there are things you can do to help MarCom specifically.

  1. Become a member. The revenue helps, of course. But it’s also one of the best ways to advocate for community programs.
  2. Refer friends and colleagues. Ask people you know at organizations that aren’t using Drupal to contact us. We need to know how these organizations make their decisions, and why they haven’t decided on Drupal.
  3. Support Global Training Days. Join the group at groups.drupal.org/global-training-days and add your 2016 events there. And if you want to know more about the working group we’re organizing, email Lizz.
  4. Contribute in the content issue queue. Especially for case studies, services listings, and training listings.
  5. Submit even the non-DrupalCon surveys. It’ll help us make decisions based on what you like, appreciate, value, and actually do.

 

About Bradley

Bradley Fields joined the Drupal Association in March 2015 as Content Manager. He now leads the content team as Marketing & Communications Manager.

When not at his desk, he’s curating Spotify playlists, watching an animated Disney movie, on the hunt for great whisk{e}y, or reading Offscreen magazine. He lives in Portland, OR.

Catégories: Elsewhere

Palantir: From Intern to Employee: What to Expect in the Transition

mar, 30/08/2016 - 19:59
From Intern to Employee: What to Expect in the Transition brandt Tue, 08/30/2016 - 12:59 Matt Carmichael Aug 30, 2016

Internship experience is extremely valuable, especially in web development. So what can you expect in the transition from coursework to client work?

In this post we will cover...
  • The benefits of having an internship
  • What learning challenges you can expect

Want to work at Palantir?

Send us your resume!

The transition from student to full-time programmer can be intimidating. The days of submitting buggy and poorly-tested code that is just good enough to get a passing grade are over. Every line of code is just as important as the last, and even the smallest mistakes could lead to catastrophic problems for your team and your client. But trust me, it's doable!

I was lucky enough to have an internship at Palantir the summer before becoming a full-time employee. The opportunity to dive into the professional side of development without having quite the expectations of a full-time employee is priceless in my opinion. It gives you a chance to focus more on the learning experience of being a developer, without stressing as much over productivity and results. 

The most prominent takeaways from my time as an intern were learning and engaging in the process of collaborative programming with a team and also understanding the importance of code quality. In school a majority of the projects are done individually and you rarely have to rely on anyone else to get the job done. This is one of the biggest adjustments to make, as the workplace is the exact opposite. The members of your team need your code to be correct, verbose, and understandable in order to do their jobs. That being said, coding standards cannot be stressed enough in a team environment and doing things ‘your way’ is not going to cut it. 

At Palantir, I was introduced to an extensive Github repository devoted to documenting our code standards and development process. Familiarizing myself with the workflow, documentation, and code style expectations seemed like a full time job in its own right. Every line of code is submitted in a pull request which is inspected by a senior engineer and tested against the standards that are laid out in the developer documentation. 

Issues as seemingly trivial as the size of an indentation and documentation formatting are sent back to the programmer for revisions. Once the code has been through the critique and revision phase and is cleared by the engineer, the code is finally merged into the master branch and is ready to go into production.  This level of attention to details that seem trivial at a glance, but are vital for code consistency and readability, is in place to ensure the best product for the client.

Once you get past the logistics of teamwork, and the code standards become second nature to you, it's all uphill from there. As I settle in and become more confident in my role I realize how exciting worklife is. The opportunity to work with people of all backgrounds and skillsets and to see a project come together from start to finish is what makes it all worthwhile. 
 

Stay connected with the latest news on web strategy, design, and development.

Sign up for our newsletter.
Catégories: Elsewhere

Chromatic: Drush SQL Sync Alternative: SQL Sync Pipe

mar, 30/08/2016 - 19:56

Using Drush to sync databses (drush sql-sync) is a valuable tool, but it is not always an efficient choice when dealing with large databases (think over 1GB). SQL Sync Pipe (drush sql-sync-pipe) is a Drush command that provides an alternative for drush sql-sync that streams the database dump directly from the source to the destination as opposed to sql-sync saving the database dump, transferring it via rsync and then importing the dump file. As an added bonus it excludes cache tables by default.

Benchmarks

Below are examples from the command's README, syncing the same 1.05Gib database using the two different methods:

drush sql-sync Command: drush sql-sync @alias.dev @alias.sandbox --no-cache Transfer size: 88.1MiB (compressed using rsync) Import size: 1.05GiB Total time elapsed: 46 minutes 47 seconds drush sql-sync-pipe Command: drush sql-sync-pipe @alias.dev @alias.sandbox --progress Transfer size: 88.1MiB (sent compressed using gzip) Import size: 1.05GiB Import & transfer time: 27 minutes 05 seconds Total time elapsed: 30 minutes 35 seconds

What are you waiting for? Download and install SQL Sync Pipe and get started!

drush dl drush_sql_sync_pipe --destination=$HOME/.drush && drush cc drush
Catégories: Elsewhere

Drupal.org blog: Documentation overhaul

mar, 30/08/2016 - 18:11

One of the biggest content areas on Drupal.org—and one of the most important assets of any open source project—is documentation. Community-written Drupal documentation consists of about 10,000 pages. Preparations for the complete overhaul of the documentation tools were in the works for quite some time, and in the recent weeks we finally started to roll out the changes on the live site.

Background

Improving documentation on Drupal.org has been a part of a larger effort to restructure content on the site based on content strategy we developed.

The new section comes after a few we launched earlier in the year. It also uses our new visual system, which will slowly expand into other areas.

Goals and process

The overall goal for the new Documentation section is to increase the quality of the community documentation.

On a more tactical level, we want to:

  • Introduce the concept of "maintainers" for distinct parts of documentation
  • Flatten deep documentation hierarchy
  • Split documentation per major Drupal version
  • Notify people about edits or new documentation
  • Make comments more useful

To achieve those goals, we went through the following process:

First, we wrote a bunch of user stories based on our user research and the story map exercise we went through with the Documentation Working Group members. Those stories cover all kinds of things different types of users do while using documentation tools.

We then wireframed our ideas for how the new documentation system should look and work. We ran a number of remote and in person usability testing sessions on those wireframes.

Our next step was to incorporate the feedback, update our wireframes, and create actual designs. And then we tested them again, in person, during DrupalCamp London.
Incorporated feedback again, and started building.

The new system

So, how does the new documentation system work exactly? It is based on two new content types:

  1. Documentation guide: a container content type. It will group documentation pages on a specific topic, and provide an ability to assign 'maintainers' for this group of pages (similar to maintainers for contributed projects). Additionally, users will be able to follow the guide and receive notifications about new pages added or existing pages edited.
  2. Documentation page: a content type for the actual documentation content. These live inside of documentation guides.


Example of a new documentation guide

All of the documentation is split per major Drupal version, which means every documentation guide or page lives inside of one of a few top level 'buckets', e.g. Drupal 7 documentation, Drupal 8 documentation.
It is also possible to connect guides and pages to each other via a 'Related content' field, which should make it easier to discover relevant information. One of our next to-do’s is to provide an easy way to connect documentation guides to projects, enabling 'official' project documentation functionality.

More information on various design decisions we made for the new documentation system, and the reasons behind them, can be found in our DrupalCon New Orleans session (slides).

Current status

Right now, we have the new content types and related tools ready on Drupal.org.
We are currently migrating existing documentation (all 10,000 pages!) into the new system. The first step is generic documentation (e.g. 'Structure Guide'), with contributed projects documentation to follow later.

While working on the migration, we are recruiting maintainers for the new guides. If you are interested in helping out, sign up in the issue. Please only sign up if you actually have some time to work on documentation in the near future.

There is a lot of work to be done post-migration (both by guide maintainers and regular readers/editors). The content is being migrated as-is, and it needs to be adapted for the new system. This means almost every single page needs to be edited. New fields (such as Summary) filled out with meaningful text (to replace text automatically generated by the migration script). A lot of pages include information for both Drupal 7 and Drupal 8, but this content needs to be split, with Drupal 8 information moved to pages in the appropriate version of the guide. These are just some of the steps that need to happen once the documentation has been migrated into the new system.

Next steps

As staff, we have a few follow-up tasks for minor improvements to the content types and tools. However, the bulk of the work is editing and improving the actual documentation, as I described above. This is in your hands now. Not only do we not have enough staff members to edit every single documentation page in a reasonable amount of time, we are also not subject matter experts for many of the topics, and so can't provide meaningful edits. The tools are ready, now it is up to the community to pick them up and write great documentation.


Example of a documentation page

Thank you

Lastly we want to say thanks.

Thanks to all the community volunteers who wrote those 10,000 pages over the years. Thanks to the Documentation Working Group members for their expertise, insight, and patience.

And, of course, thanks to staff. Unfortunately due to recent changes for the Engineering team, this will be the last section we'll have resources to work on for a while. This was a fun and important project to work on, and we are glad that we got to finish it. It is a beautiful legacy of the work we did together with some of our former colleagues: DyanneNova, japerry, and joshuami. Thank you!

Catégories: Elsewhere

Sooper Drupal Themes: "It starts with something small" Next Gen Drupal Themes From 1.0 To 2.5 In a Single Year

mar, 30/08/2016 - 18:00

Just over a year ago I started with something small. I combined some existing technologies to create a drag and drop builder/theme. A combination of jQuery UI, CKEditor, Bootstrap 3 and Drupal. The result was far from perfect but interesting enough to get a bunch of people excited and involved in helping me find out how to improve the product.

Above: our Glazed main demo. Click to view full demo. Glazed Construction Design, Product Updates

Today's blog celebrates the new Construction design that is available today to all SooperThemes members. We've been working towards this release for nearly a year and the reason it took so long is that the core of the Glazed framework theme and drag and drop builder needed to be 100% up to the job. The reliability, sophistication and flexibility of our framework theme and drag and drop builder are lightyears ahead of the minimum viable product we released 14 months ago. To our customers who joined us in the beginning and are now renewing for the second year: Thank you so much! 

Our construction theme (click to view demo) is not the prettiest design I've ever created but that's not really the point. The point is that it looks like a construction theme all the way. It doesn't look like a generic theme that was customized to look a little bit more "heavy industry". Our Glazed framework theme allows you to completely design every aspect of your Drupal site from typography, to colors, grid design and navigation. Combine this with our drag and drop builder and everything you need in a business website can be designed and developed in the browser. From a blank canvas all the way down to the pages, views and forms everything in this demo was created in the browser, without writing a single line of code

No templates were edited, no CSS was written, not even a single hand coded HTML tag was needed to build this unique 40 page Glazed demo.

For more details about todays products updates check out the Glazed Changelog and Carbide Builder Changelog.

Why WordPress Is Taking Turf From Drupal 

It's simple economics. You can buy a WordPress theme for $59,- USD and a few days of customization and content editing later and your client is impressed and your project is comfortably on schedule and on budget. WordPress themes have become a major source of innovation in recent years, offering drag and drop builders, and niche-specific features for magazine websites, directory websites and all sorts of small business websites.

Themes are becoming more sophisticated and crawling into Drupal territories like for example education, magazines and community websites.

10 years ago I moved away from WordPress and Mambo because I simply felt Drupal was better, and I still feel that way. While these WordPress themes are loaded with features, they lack Drupal's modularity, coding standards and interoperability. I sincerely believe Drupal can be a better platform for all these themes. After all, Drupal has built in support for content types, relations, versioning, configuration management, and superior user management and access control.

Starting from today I will focus on offering as many niche designs for small businesses, large businesses, NGOs, governments, educators and online magazines. I hope that you will join sooperthemes.com and help us with our mission to show the world that Drupal is capable of doing what WordPress does and more. 

Our mission as SooperThemes is to promote Drupal as the #1 platform to author content on the web and at the same time to remain the #1 provider of designs and design tools for Drupal. See our roadmap for more details. The way to make Drupal the number one choice again is through the same economics that made WordPress so big, so our initial focus is to disrupt the market with a 90% decrease in costs of building and running a Drupal website.

Enjoying The Ride 

The past year has been a big adventure but also a lot of grinding, bug fixing, technical debt problems and all the things that new products face when they enter the market. However it has mostly been fun and exciting to develop these new technologies for the Drupal community and the reception of our updates is really motivating and powering our new developments.

Allthough pioneering in the area of next gen (drag and drop) Drupal themes meant facing a steep learning curve it can be said that Drupal is actually easier to build on in the long term. Our Drag and Drop builder is very similar to a frontend framewor that uses the CMS as an API. This is somthing that needs hooks and AJAX capabilities. Something that Drupal provides out of the box.

If you are reading this as a prospective customer: please join Sooperthemes and enjoy the ride with us. To our existing customers: keep your eyes open for exciting new features and designs. 

Catégories: Elsewhere

Appnovation Technologies: Becoming an Appnovator

mar, 30/08/2016 - 17:21

Catégories: Elsewhere

Tag1 Consulting: Drupal 6 Long Term Support is My Favorite Feature of Drupal 8

mar, 30/08/2016 - 17:04
rfay Tue, 08/30/2016 - 08:04

Long Term Support for Drupal 6 might be my favorite new feature included in Drupal 8. (I know, that might be stretching things for the fundamentally awesome step forward that Drupal 8 is, but bear with me.)

Catégories: Elsewhere

InternetDevels: Collection of great free responsive Drupal themes 2016

mar, 30/08/2016 - 14:53

According to the best practices of responsive web design, a website neatly adapts to whatever screen it is viewed on. And according to the best practices of our blog, we make collections of free responsive Drupal themes for you to use.

Read more
Catégories: Elsewhere

LevelTen Interactive: Hang Out With Some Cool People-- We Are Hiring!

mar, 30/08/2016 - 07:00

Are you looking for a job in the tech world? Have you ever worked at a company that practiced Agile Methodology? Then this is the job for you! 

Who We Are:

We’re a small web development and marketing agency near Southern Methodist University in Dallas, Texas. We like the occasional ice cream socials and NERF gun battles, but most of all, we enjoy making Drupal websites and helping client's businesses grow. 

The Position:

PT Technical...Read more

Catégories: Elsewhere

Pages