Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 4 min 42 sec ago

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

Wed, 08/31/2016 - 21:41
!-- field.tpl -- div class=field field-name-body field-type-text-with-summary field-label-hidden !-- theme hook suggestions: -- !-- hook:field -- !-- tpl file: * field--text-with-summary.tpl.php -- !-- tpl file: * field--body.tpl.php -- !-- tpl file: * field--blog.tpl.php -- !-- tpl file: * field--body--blog.tpl.php -- pa href= 8/a includes more than 200 new features and enhancements for developers, and there’s been a href= shortage/a of a href= on the a href= advantages/a of upgrading./p /div !--/field.tpl --

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

Wed, 08/31/2016 - 21:15
spanChanging user display name in Drupal 7 and Drupal 8/span divpEvery 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./p pModifying 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./p pThe 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./p/div spanspan lang= about= typeof=schema:Person property=schema:name datatype= xml:lang=aram/span/span spanWed, 31/08/2016 - 21:15/span ul class=links inlinelia href= rel=tag title=Changing user display name in Drupal 7 and Drupal 8 hreflang=enRead morespan class=visually-hidden about Changing user display name in Drupal 7 and Drupal 8/span/a/li/ul Drupal 6 security updates for Flag!

Wed, 08/31/2016 - 19:49
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpemAs you may know, a href= 6 has reached End-of-Life (EOL)/a 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 a href= 6 LTS vendors/a are and we're one of them!/em/ppstrongToday, there is a Moderately Critical security releases for the a href= module for multiple Access Bypass vulnerabilities./strong/ppspanThe 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./span/ppSee the a href= advisory for Drupal 7/a for more information./ppHere you can download the patch for a href= or a href=!/ppstrong/strongIf 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. :-)/ppstrongIf you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please a href= out our D6LTS plans/a./strong/ppemspanNote/span: if you use the a href= 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

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

Wed, 08/31/2016 - 16:02
img typeof=foaf:Image src= width=200 height=152 alt=A Pro Tip from Mediacurrent title=A Pro Tip from Mediacurrent / pOr, just adding this setup to your current theme, even if it is Ruby.../p Drupal 8 Tutorial #44 : CKEditor CodeSnippet Module

Wed, 08/31/2016 - 11:45
!-- google_ad_section_start --div class=field field-name-field-tutorial-description field-type-text-long field-label-hiddendiv class=field-itemsdiv class=field-item even property=schema:descriptionpWith CKEditor CodeSnippet module you can insert strongcode snippets with syntax highlighting/strong into the editor./p /div/div/divdiv class=field field-name-field-tutorial-youtube field-type-youtube field-label-hiddendiv class=field-itemsdiv class=field-item even property=schema:videoa href=/drupal/filters-editors/drupal-8-tutorial-44-ckeditor-codesnippet-moduleimg class=img-responsive typeof=foaf:Image src= alt=Embedded thumbnail for Drupal 8 Tutorial #44 : CKEditor CodeSnippet Module //a/div/div/div!-- google_ad_section_end --span property=schema:name content=Drupal 8 Tutorial #44 : CKEditor CodeSnippet Module class=rdf-meta element-hidden/spanspan rel=schema:url resource=/drupal/filters-editors/drupal-8-tutorial-44-ckeditor-codesnippet-module class=rdf-meta element-hidden/span

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

Wed, 08/31/2016 - 11:20
a href=;utm_medium=drupal-planetamp;utm_campaign=node-64 title=One or Multiple. Make a Bootstrap Carousel from a Multiple Value Drupal Fieldimg class=img-responsive src= width=620 height=465 alt=Lego Uncle Jim in Greece at the cafe title=Lego Uncle Jim in Greece at the cafe //abr pEarlier this week I wrote how to create a a href=/blog/making-bootstrap-carousel-drupal-paragraphs-single-twig-templateBootstrap Carousel using the Drupal Paragraphs module/a.  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./p pThanks 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./p pWhile 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 a href= carousel/a.  You would just need to change the markup to fit your specific framework./p pSo, 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/p pa href=;utm_medium=drupal-planetamp;utm_campaign=node-64 title=One or Multiple. Make a Bootstrap Carousel from a Multiple Value Drupal FieldRead more/a/p

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

Wed, 08/31/2016 - 11:00
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedpspan style=color:#000000;span style=font-size:14px;span style=font-family:georgia,serif;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. /span/span/span/p /div/div/div

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

Wed, 08/31/2016 - 02:47
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenp style=text-align:center;emThis post is part of a href= series about recent changes at the Drupal Association/a./em/p pLike each of the Drupal Association teams, Marketing amp; 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./p pWe 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./p pIt’s a feat that’s always been impossible without help from community members like you. There’s the work a href= does in the content issue queue. What a href= and a href= do on our social accounts. And what a href=, a href=, a href=ábor/a, a href=, a href=, and many more do to coordinate releases. There’s more than we can count./p pBut 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./p h2 First, an apology/h2 pWe’re sorry. This isn’t just business; our work is emfor you/em. 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./p pIf 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.)/p pSo, if we let you down, we’re sorry. Your trust is invaluable to us. We try to earn it every day./p h2 But we must decide/h2 h3 Criteria/h3 pThe Association has two priorities:/p ulli Create sustainable financial health/li li Get more organizations with large, complex digital ecosystems—government agencies, publishers, universities, etc.—to choose Drupal/li /ulpThis means prioritizing revenue-generating initiatives. It means changing, or adding to, some of the user experience on—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./p h3 Clarity/h3 pWe 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./p pWe 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./p p style=text-align:center;iframe allowfullscreen=true frameborder=0 height=366 mozallowfullscreen=true src=;loop=falseamp;delayms=3000 webkitallowfullscreen=true width=600/iframebr /ema href= available on Google Drive/a/em/p pClarity 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./p h3 Capacity/h3 pWhat can two people do or coordinate well? What can we complete and sustain?/p pA 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./p pOur 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./p h2 What we’ll do/h2 pThere 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. (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./p pSo, 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:/p ulli Drupal marketing and communications (e.g., release support)/li li D.o content management of promoted areas (e.g., the a href= homepage refresh/a and “Drupal for industries” content)/li li DrupalCon marketing and communications, and sponsor and partner fulfillment/li li Membership (for people and organizations)/li li Supporter Program fulfillment/li li marketing and communications/li li Camp engagement (we’ll create a 2017 camp kit before January; promise)/li li Elections support/li li Association communications, generally (e.g., writing and editing posts like this)/li /ulh2 The work we won’t/h2 pTo make the work we’ll do possible, there’s work we can’t give as much attention./p pThere’s work we, unfortunately, won’t do at all./p ulli Help build new D.o Sections (the a href= Tatiana led/a is paused for now)/li li D.o content management of areas that aren’t being promoted/li li Support the Drupal Store (its inventory will be liquidated)/li li Share Community Spotlights/li li Manage content (the subdomain will be phased out)/li li Promote our webcast series/li /ulpAnd there’s work we’ll reduce or others will lead./p ulli Global Training Days (we’re setting up a community working group to coordinate it)/li li Advertising content production (we’ll depend on designers we trust)/li li Email newsletters (we’ll send fewer than the four we do now)/li li Sticker distribution (we’ll bring them to DrupalCons, but won’t ship them around the world)/li /ulpThis process will be fluid. As we adjust to these changes, these work lists may change again. If so, we’ll let you know./p h2 How can you help?/h2 pIf you help the Engineering and Events teams by a href= back in ways Tim mentioned/a or a href= as Rachel suggested/a, you help us too. But there are things you can do to help MarCom specifically./p olli strongBecome a member/strong. The revenue helps, of course. But it’s also a href= of the best ways to advocate for community programs/a./li li strongRefer friends and colleagues/strong. 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./li li strongSupport Global Training Days/strong. Join the group at a href= and add your 2016 events there. And if you want to know more about the working group we’re organizing, a href=mailto:lizz@association.drupal.orgemail Lizz/a./li li strongContribute in the content issue queue/strong. Especially for a href=;status=Openamp;priorities=Allamp;categories=Allamp;version=Allamp;component=Case+studiescase studies/a, a href=;status=Openamp;priorities=Allamp;categories=Allamp;version=Allamp;component=Services+listingservices listings/a, and a href=;status=Openamp;priorities=Allamp;categories=Allamp;version=Allamp;component=Training+listingtraining listings/a./li li strongSubmit even the non-DrupalCon surveys/strong. It’ll help us make decisions based on what you like, appreciate, value, and actually do./li /olp /p hr /h3 img alt=Picture of Bradley Fields src= style=width: 120px; height: 120px; margin: 2px 8px; float: left; /About Bradley/h3 pa href= Fields/a joined the Drupal Association in March 2015 as Content Manager. He now leads the content team as Marketing amp; Communications Manager./p pWhen 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./p /div/div/div

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

Tue, 08/30/2016 - 19:59
spanFrom Intern to Employee: What to Expect in the Transition/span spanspan lang= about= typeof=schema:Person property=schema:name datatype= xml:lang=brandt/span/span spanTue, 08/30/2016 - 12:59/span Matt Carmichael time datetime=2016-08-30T12:00:00ZAug 30, 2016/timeimg src= width=1300 height=731 alt=Photo of Matt Carmichael sitting at table with other Palantiri typeof=foaf:Image /div class=lede pInternship experience is extremely valuable, especially in web development. So what can you expect in the transition from coursework to client work?/p /div In this post we will cover... ulliThe benefits of having an internship/li liWhat learning challenges you can expect/li /ulsection class=ctah3 class=cta__title /h3pWant to work at Palantir?/p span class=cta__link a href= us your resume!/a /span /sectionpThe 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!/p pI 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. /p pThe 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. /p pAt 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. /p pIssues 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./p pOnce 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. br /  /p aside class=ctah3 class=cta__title /h3pStay connected with the latest news on web strategy, design, and development./p span class=cta__link a href= up for our newsletter./a /span /asideul class=list--simpleli class=taga href= hreflang=enCommunity/a/li li class=taga href= hreflang=enDevelopment/a/li li class=taga href= hreflang=enPeople/a/li /ul

Chromatic: Drush SQL Sync Alternative: SQL Sync Pipe

Tue, 08/30/2016 - 19:56
pUsing Drush to sync databses (codedrush sql-sync/code) is a valuable tool, but it is not always an efficient choice when dealing with large databases (think over 1GB). a href= Sync Pipe/a (codedrush sql-sync-pipe/code) is a Drush command that provides an alternative for codedrush sql-sync/code that streams the database dump directly from the source to the destination as opposed to codesql-sync/code saving the database dump, transferring it via rsync and then importing the dump file. As an added bonus it excludes cache tables by default./p h2Benchmarks/h2 pBelow are examples from the command's README, syncing the same 1.05Gib database using the two different methods:/p h3drush sql-sync/h3 precodeCommand: drush sql-sync @alias.sandbox --no-cache Transfer size: 88.1MiB (compressed using rsync) Import size: 1.05GiB Total time elapsed: 46 minutes 47 seconds /code/pre h3drush sql-sync-pipe/h3 precodeCommand: drush sql-sync-pipe @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 /code/pre pWhat are you waiting for? Download and install SQL Sync Pipe and get started!/p precodedrush dl drush_sql_sync_pipe --destination=$HOME/.drush drush cc drush /code/pre blog: Documentation overhaul

Tue, 08/30/2016 - 18:11
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item evenpOne of the biggest content areas on—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./p h2Background/h2 pImproving documentation on has been a part of a larger effort to a href= rel=nofollowrestructure content on the site/a based on a href= rel=nofollowcontent strategy/a we developed./p pThe new section comes after a href= rel=nofollowa few we launched earlier in the year/a. It also uses our a href= rel=nofollownew visual system/a, which will slowly expand into other areas./p h2Goals and process/h2 pThe overall goal for the new Documentation section is to increase the quality of the community documentation./p pOn a more tactical level, we want to:/p ulliIntroduce the concept of maintainers for distinct parts of documentation/li liFlatten deep documentation hierarchy/li liSplit documentation per major Drupal version/li liNotify people about edits or new documentation/li liMake comments more useful/li /ulpTo achieve those goals, we went through the following process:/p pFirst, 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./p pWe 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./p pOur next step was to incorporate the feedback, update our wireframes, and create actual designs. And then we tested them again, in person, during DrupalCamp / Incorporated feedback again, and started building./p h2The new system/h2 pSo, how does the new documentation system work exactly? It is based on two new content types:/p ollistrongDocumentation guide/strong: 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./li listrongDocumentation page/strong: a content type for the actual documentation content. These live inside of documentation guides./li /olpimg alt=Documentation guide screenshot height=1571 src=/files/documentation-guide.png width=1138 /br / Example of a new documentation guidebr //p pAll 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 / 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./p pMore information on various design decisions we made for the new documentation system, and the reasons behind them, can be found in our a href= rel=nofollowDrupalCon New Orleans session/a (a href= rel=nofollowslides/a)./p h2Current status/h2 pRight now, we have the new content types and related tools ready on / 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./p pWhile working on the migration, we are recruiting maintainers for the new guides. If you are interested in helping out, a href= rel=nofollowsign up in the issue/a. Please only sign up if you actually have some time to work on documentation in the near future./p pThere 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 a href= rel=nofollowsome of the steps/a that need to happen once the documentation has been migrated into the new system./p h2Next steps/h2 pAs 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./p pimg alt=Documentation page screenshot height=1184 src=/files/documentation-page.png width=1138 /br / Example of a documentation pagebr //p h2Thank you/h2 pLastly we want to say thanks./p pThanks to all the community volunteers who wrote those 10,000 pages over the years. Thanks to the a href= rel=nofollowDocumentation Working Group members/a for their expertise, insight, and patience./p pAnd, of course, thanks to staff. Unfortunately due to a href= rel=nofollowrecent changes for the Engineering team/a, 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: a href= rel=nofollowDyanneNova/a, a href= rel=nofollowjaperry/a, and a href= rel=nofollowjoshuami/a. Thank you!/p/div/div/div

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

Tue, 08/30/2016 - 18:00
div class=field-content-banner glazed-util-float-right float-right a href= typeof=foaf:Image class=img-responsive src= width=300 height=140 alt= //a /div div class=field-body pJust 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./p div style=text-align: center;a href=http://glazed-demo.sooperthemes.comimg src= title=source: div style=text-align: center;Above: our Glazed main demo. a href=http://glazed-demo.sooperthemes.comClick to view full demo/a./div h3 class=st-title bg-glazedGlazed Construction Design, Product Updates/h3 pToday'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 themenbsp;and drag and drop builder are lightyears ahead of the minimum viable productnbsp;we released 14 months ago. To our customers who joined us in the beginning and are now renewing for the second year: strongThank you so much!nbsp;/strong/p p style=text-align: center;a href= target=_blankimg alt= class=block-center data-fid=1264 data-media-element=1 src=// style=width: 75%; typeof=foaf:Image/a/p div class=field-blog-image field-inline first last img typeof=foaf:Image class=img-responsive src= width=848 height=300 / /div pOur construction theme (a href= target=_blankclick to view demo/a) 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, strongwithout writing a single line of code/strong.nbsp;/p pNo 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./p pFor more details about todays products updates check out the a href= Changelog/a and a href= Builder Changelog/a./p p/p h3 class=st-title bg-glazedWhy WordPress Is Taking Turf From Drupalnbsp;/h3 pIt'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./p pThemes are becoming more sophisticated and crawling into Drupal territories like for example education, magazinesnbsp;and community websites./p p/p p style=text-align: center;img alt= class=block-center data-fid=1267 data-media-element=1 src=// style=width: 75%; typeof=foaf:Image/p p10 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./p pStarting 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 and help us with our mission to show the world that Drupal is capable of doing what WordPress does and more.nbsp;/p pOur 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 a href= 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 anbsp;strong90% decrease in costs/strongnbsp;of building and running a Drupal website./p h3 class=st-title bg-glazed style=text-align: left;Enjoying The Ridenbsp;/h3 pThe 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. Howevernbsp;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./p pAllthough 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 andnbsp;AJAX capabilities. Something that Drupal provides out of the box./p p style=text-align: center;img alt= class=center-bllock data-fid=1266 data-media-element=1 src=// style=width: 75%; typeof=foaf:Image/p pIf 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.nbsp;/p /div

Appnovation Technologies: Becoming an Appnovator

Tue, 08/30/2016 - 17:21
div class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encoded p style=text-align: center;img alt= class=media-image height=270 width=480 typeof=foaf:Image src= //p/div/div/divdiv class=field field-name-field-blog-header-image field-type-image field-label-hiddendiv class=field-itemsdiv class=field-item evena href=/blog/becoming-appnovatorimg typeof=foaf:Image src= width=1400 height=400 alt= //a/div/div/divdiv class=sharethis-buttonsdiv class=sharethis-wrapperspan st_url= st_title=Becoming an Appnovator class=st_facebook/span span st_url= st_title=Becoming an Appnovator class=st_twitter/span span st_url= st_title=Becoming an Appnovator class=st_sharethis/span /div/div

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

Tue, 08/30/2016 - 17:04
span data-quickedit-field-id=node/70/uid/en/teaser class=field field--name-uid field--type-entity-reference field--label-hiddenspan lang= about=/user/16 typeof=schema:Person property=schema:name datatype=rfay/span/span span data-quickedit-field-id=node/70/created/en/teaser class=field field--name-created field--type-created field--label-hiddenTue, 08/30/2016 - 08:04/span div data-quickedit-field-id=node/70/body/en/teaser class=clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__itempLong 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.)/p/div div class=node__links ul class=links inlineli class=node-readmorea href=/blog/d6lts-on-d8 rel=tag title=Drupal 6 Long Term Support is My Favorite Feature of Drupal 8 hreflang=enRead morespan class=visually-hidden about Drupal 6 Long Term Support is My Favorite Feature of Drupal 8/span/a/lili class=disqus-comments-numa href=/blog/d6lts-on-d8#disqus_thread data-disqus-identifier=node/70 hreflang=enComments/a/li/ul /div

InternetDevels: Collection of great free responsive Drupal themes 2016

Tue, 08/30/2016 - 14:53
div class=field field--name-field-preview-image field--type-image field--label-hiddendiv class=field__itemsdiv class=field__item evenimg src= width=937 height=622 alt=Collection of great free responsive Drupal themes 2016 //div/div/divdiv class=field field--name-body field--type-text-with-summary field--label-hiddendiv class=field__itemsdiv class=field__item evenpAccording to the best practices of a href= target=_blankresponsive web design/a, 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./p a href= more/a/div/div/div

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

Tue, 08/30/2016 - 07:00
img typeof=foaf:Image src= width=600 height=300 alt= / pAre 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! /p h3Who We Are:/h3 pspan style=font-size: 14px;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. /span/p h3The Position:/h3 pa href= Technical/a...a href=/blog/felipa-villegas/hang-out-some-cool-people-we-are-hiring class=more-linkRead more/a/p

DrupalCon News: Join Us for the New DevOps Summit

Mon, 08/29/2016 - 23:33
div class=field field--name-body field--type-text-with-summary field--label-hiddendiv class=field__itemsdiv class=field__item evenpWe added a new summit to the DrupalCon line-up this year: the DevOps Summit, on Monday, 26 September. It's a day filled with keynotes, an industry leaders panel, open discussions, and networking./p pDevOps is a popular part of DrupalCon. There are 12 sessions dedicated to DevOps topics like continuous integration and serverless architecture. But we're excited to add more programming for DevOps fans far and wide. With the summit, we've dedicated time and space to offer networking and collaboration activities./p/div/div/div

Fuse Interactive: Bean vs. FPP - Structured content outside of nodes

Mon, 08/29/2016 - 23:12
pOne of the issues I had with Drupal when I first started working on it was how to handle the one-off pages or sections of a site that didn’t fit into something like a Node. Nodes work for repeated pieces of content that will share the same structure, but as soon as we have complicated, one-off pages or sections, we start to need something more./p

Lullabot: Internal API Design for Distributed Teams

Mon, 08/29/2016 - 18:00
div class=rich-textdiv class=rich-text__contentpMy first real project with multiple distributed teams and a timeline measured in weeks (not months!) was the launch of a href= Tonight Show with Jimmy Fallon/a. With six weeks to go from nothing to a CMS, a website, and multiple apps, we were forced to figure out the best way to keep all the teams always moving. I wrote then about a href= Binding your Web APIs/a, but I think it#x2019;s time to clarify and update some of it#x2019;s points for maximising your team#x2019;s productivity./p h2Introduce the teams/h2 pBefore features are defined, APIs are designed, and work is started, it#x2019;s really important to have some sort of team introduction. This doesn#x2019;t need to be a long meeting. What#x2019;s important is to get at least one technical person who will need to create or use APIs from each distinct team introduced. At a high level, identify the API providers and consumers from a business perspective. Determine who owns the APIs and their specifications. Make sure each technical person understands the goals of the project. Then, unless you are one of those technical people, get out of the way! Leave the meeting, drop the call, and let those people get to work./p h2Lay the API Foundation/h2 pa href= API makes assumptions/a - about the basic structure of data, about authentication, and about maintenance and updates. Before determining your core objects, figure these things out. Discuss if you#x2019;re implementing an RPC API or a REST API. Decide if you#x2019;re supporting JSON, XML, or both. For REST APIs, find a suitable specification that supports the a href= Factors/a you need, like a href=http://jsonapi.orgJSON API/a or a href=, and use it to structure your data and API to simplify client and server implementations. Decide on authentication protocols, like OAuth or HTTP basic. Decide on a versioning strategy such as versioned URLs or custom MIME types. Steal from existing internal implementations where possible. Finally, start writing code./p pThe problem with beginning implementations now is that there is no source of truth for the API. It#x2019;s easy for teams to start making bad assumptions, leading to rework and putting your launch at risk. Instead, use a tool built for managing API documentation like a href=https://apiblueprint.orgApiary#x2019;s Blueprint/a or a href=http://swagger.ioSwagger/a. Ideally, the tools will let you easily generate API stubs too. Doing so will unblock client implementations, as they won#x2019;t be dependent on the production API to start their work. Best yet, when there is disagreement between implementations, the docs become the arbiter of what is right. Sure, documentation can be wrong or miss key details, but it#x2019;s much easier to understand a spec than someone else#x2019;s code. Best yet, since the first API consumer will be an involved participant in writing the docs, your API will have docs ready to go when that second consumer comes along./p pNow, your teams can start writing code, pulling in the core libraries for authentication and data structures./p h2Design API Objects/h2 pNow that you have the basic API details figured out, you can start to design objects (or in REST parlance #x2018;resources#x2019;). At this stage, you are modelling data, and not actions. Assume every object has a GET call, even if it#x2019;s not immediately clear that it#x2019;s needed. Letting your clients inspect the state of objects will help them to debug your API and their code without relying on expensive calls and meetings that suck up time from getting things done. Design the object schema to be as #x201C;obvious#x201D; as possible#x2014;don#x2019;t use #x2018;image#x2019; in one object attribute and #x2018;picture#x2019; in another, unless they mean different things. Use REST best practices such as using URLs as canonical identifiers of objects. A critical step many teams miss is determining who manages unique IDs. With the inherent concurrency and assumed unreliability of HTTP requests, identifying which systems manage which IDs is something not to forget./p pAgain, at this point you should have new documentation and stubs, but no code. Let your documentation continue to be the source of truth./p h2Design API Operations/h2 pUsing your work to this point, API operations should start to have intuitive implementations, especially if you are using REST best practices. Map your various CRUD operations to GET / POST / PATCH / PUT / DELETE as required. Find good HTTP status codes to communicate the results of REST calls (my favourite new discovery is a href= Conflict/a)./p pOne common mistake services teams make at this point is to create a #x201C;wide-open POST endpoint#x201D; that accepts arbitrary data, and then to reverse-engineer the data into an implementation. Remember, our goal is to keep any sort of dependencies between the teams to a minimum. This sort of development methodology maximizes the dependencies between the teams, and requires implementations that might be totally wrong. It makes what should be an strongexplicit/strong API contract strongimplicit/strong. When the API calls break, there#x2019;s no documentation to fall back on, forcing calls and meetings that block all the teams./p h2Implement All The Things!/h2 pAll the work so far has been to get to this point of productivity. By now, there should be no hard dependencies between the teams. Stubs can be replaced by implementations as development continues. New APIs can be added quickly by following the existing patterns. API consumers can even make assumptions about how an API would likely be designed before they contact the API team. Questions and iterations can be focused on tickets and documentation comments, helping to preserve the feasibility of the launch date. Stakeholders, project managers, developers, all win./p pemHeader image from a href= simplest foundation, a padstone/a/em/p /div/div

Acquia Developer Center Blog: Waterwheel, the Drupal SDK Ecosystem

Mon, 08/29/2016 - 17:56
div class=field field-name-field-blog-image field-type-image field-label-hiddendiv class=field-itemsdiv class=field-item evenimg typeof=foaf:Image src= width=140 height=85 alt=actual waterwheel //div/div/divdiv class=field field-name-body field-type-text-with-summary field-label-hiddendiv class=field-itemsdiv class=field-item even property=content:encodedpAs Drupal is increasingly widely used as a back end for application ecosystems, developers of wildly diverse backgrounds are now retrieving and manipulating data from Drupal in unprecedented ways. With Drupal 8 and core REST support articulating an API-first vision for the decoupled future, Drupal is eminently well-prepared to back a bevy of applications with divergent approaches. There's just one problem: non-Drupal developers don't know Drupal./p pThat's where Waterwheel comes in. Waterwheel is an emerging ecosystem of software development kits (SDKs) built by the Drupal community which ease and accelerate development of applications in other technologies. If you will momentarily forgive the flawed metaphor, Waterwheel helps non-PHP and non-Drupal developers speak Drupal./p /div/div/divdiv class=field field-name-field-blog-tags field-type-taxonomy-term-reference field-label-inline clearfixdiv class=field-labelTags:nbsp;/divdiv class=field-itemsdiv class=field-item evena href=/tags/acquia-drupal-planet typeof=skos:Concept property=rdfs:label skos:prefLabel datatype=acquia drupal planet/a/div/div/div