Drupal News

Matt Glaman: PhpStorm: PHP Fatal error: Class 'PHPUnit_TextUI_ResultPrinter'

Main Drupal Feed - Fri, 04/27/2018 - 21:00
PhpStorm: PHP Fatal error: Class 'PHPUnit_TextUI_ResultPrinter' mglaman Fri, 04/27/2018 - 16:00 Recently I ran a good ole composer update on a client project. This updated Drupal and PHPUnit. I ran our PHPUnit tests via PhpStorm and ran into an odd error. Here's how I quickly fixed it!

Commerce Guys: Improving Shopping Cart UX with Commerce Cart Flyout

Main Drupal Feed - Fri, 04/27/2018 - 19:09

Last week we announced the Commerce Cart API module with a goal of facilitating new patterns for Commerce 2.x shopping cart management. As far back as the launch of Lush's UK store, we began seeing more sites adopt one such pattern where the cart block just shows an icon or the number of items in the cart but clicking on it expands a sidebar that lets customers update the cart contents via JavaScript interactions:

We saw this more recently with a similar feature on the Orlo watches website launched by our friends at 1xINTERNET:

We expect each successive Drupal Commerce release to cut down the number of things every site developer has to do to launch a new store. Providing a general solution to this cart paradigm would do just that! We received positive feedback on the cart flyout at DrupalCon, so building on the Cart API, we have now released Commerce Cart Flyout to provide a progressively decoupled cart block and form, which gives customers a more modern cart update experience.

What does the Cart Flyout module do?

  • Provides a new cart block which triggers the cart form flyout.
  • Allows quickly changing quantities of an order item.
  • Allows removing order items without a page refresh.
  • Gives flexibility for design and interaction that is not limited by Drupal's Form API and rendering layer.

What is next

  • Provide better user feedback when an operation occurs, such as dimming the form when the auto-update happens.
  • I would love to see the add to cart message's "your cart" link trigger the flyout.

Check out the demo video!

How is it built?

In discussion with Bojan, we decided to use Backbone.js and Underscore.js for the implementation since they ship with Drupal core. Yes, it was a journey back in time, but it also provided a way to ship a contributed project without introducing an additional dependency for end users.

The module stores Underscore.js templates in Twig files that register to the theme registry. The decision to use Twig and the theme registry allows themes to customize the template and markup. We do this for our demo theme Belgrade, which you can see in its code repository: http://cgit.drupalcode.org/belgrade/tree/templates/commerce/cart.

In fact, I used a ReactJS implementation to test the underlying API and prototype this module. If you’re interested, see the test sub-module in the Cart API repository.

Aten Design Group: Managing Pantheon Sites with Terminus

Main Drupal Feed - Fri, 04/27/2018 - 19:03

In the previous post we looked into Pantheon hosting and how we can use it to easily create a suite of similar websites without having to build them individually each time. Often the requirement isn’t only easily creating new sites, but having to maintain them easily as well. When you have dozens or hundreds of websites that need changes applied to them, managing each one individually through Pantheon’s dashboard becomes a bottleneck. Fortunately Pantheon offers a command line interface that allows developers to automate much of that maintenance. In this post we’ll take a look at using Terminus to manage our sites.

Understanding Pantheon’s Framework

Before we can start rolling out features to multiple sites, it is helpful to understand how Pantheon groups the websites it hosts. Websites can be first grouped into an Organization. Within that, they can be tagged in any manner that makes sense for your needs. Both the organization and the tags can be used to filter sites into more targeted groups.

Each site then gets three environments; dev, test, and live are their machine names. Those machine names are important, as we’ll need to know which environment we’re targeting when we do our deployments. A single site also gets a machine name, like my-awesome-site. The combination of site name and environment name create a single instance identifier, which we use in our Terminus commands. For example, to clear Drupal’s cache on a live environment we’d run:

terminus remote:drush my-awesome-site.live -- cache-rebuild

A deployment on Pantheon has to follow a specific process, whether done via the dashboard or through Terminus. First, code must be deployed to the dev environment. Normally this is done with Git by pushing new code into the master branch on Pantheon’s repo. For features we’re deploying to multiple sites, the code must be pushed to the Upstream and then pulled from there. In the dashboard, this takes the form of a button that appears to alert you to new changes. In Terminus, you’d run the following command. Note, the --updatedb flag ensures any Drupal database updates get run as well.

terminus upstream:updates:apply my-awesome-site.dev --updatedb

Second, we have to move those updates to testing and then to production. Again, the dashboard provides a button on those environments when there are updates that can be made to them. In Terminus, this is done with:

terminus env:deploy my-awesome-site.test --updatedb --cc --note=”Deployed new feature.”

As before --updatedb runs the database updates, --cc rebuilds Drupal’s cache, and --note is the description of the updates that gets added to the Pantheon dashboard.

There are many other actions you can handle with Terminus. Their documentation covers the full list. However, out of the box Terminus has the same limitation that the dashboard has. You can only run a command on one site at a time. Thankfully, Terminus has additional plugins that solve this problem for us.

New Commands with Terminus Plugins

Terminus is built on PHP and managed with Composer. This allows for new commands to be built and distributed on Pantheon’s Terminus Plugin Library. We’ll need to install two plugins to run Terminus commands on multiple sites at once: Terminus Mass Update and Terminus Mass Run. Mass Update is created by Pantheon and runs the upstream:updates:apply command on a list of sites that get piped into it. Mass Run builds on that idea, by using the same piping logic and implements it onto more commands. With it you can run Drush commands, create site backups, and deploy code among other things.

To get the list of sites, we’ll use the org:site:list command. We could also use site:list, however since Custom Upstreams are an Organization level feature we’ll more than likely want to filter by Organization; org:site:list takes the name of the organization we want to filter by. To get a list of the Organizations you have access to, run terminus org:list. This returns both the machine name and the ID number of the Organizations, either will work for org:site:list.

Running terminus org:site:list aten will return a table of all sites in Aten’s Organization account. However, we still might only want a subset of those sites. This is where tagging comes in. Adding the --tag flag to our command lets us get only sites we’ve tagged with whatever is passed in. To see all sites tagged with “US” our command becomes terminus org:site:list aten --tag=US. This gets us closer, however it still returns a table of all site information. We only need the site ID numbers as a list for our Mass Run and Mass Update commands. To get this list we’ll add --format=list to our command, making the entire thing:

terminus org:site:list aten --tag=US --format=list

Now that we have a list of the site IDs we want to update, all we need to do is pipe that list into our plugin commands. To deploy a new feature from our upstream, we’d run:

terminus org:site:list aten --tag=US --format=list | terminus site:mass-update:apply --updatedb

Moving that feature through Pantheon’s environments is:

terminus org:site:list aten --tag=US --format=list | terminus env:mass:deploy --sync-content --cc --updatedb --env=test --note="Updated Drupal Core."

Removing a user from all sites they exist on becomes:

terminus org:site:list aten --tag=US --format=list | terminus remote:mass:drush --env=live -- ucan bad-user

Long Commands, Amazing Results

At this point you’ve probably noticed the commands we’re using have become very verbose. This is one downside of this approach: the commands themselves are not intuitive at first glance. For common tasks creating aliases can help simplify this. Leveraging the terminal’s history to bring up past commands and then modifying them speeds up more one-off tasks. But the ability to manage our websites en masse becomes a huge time saver over clicking our way through the dashboard for dozens of sites.

Drupal.org blog: What's new on Drupal.org? - March 2018

Main Drupal Feed - Fri, 04/27/2018 - 17:43

Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.

This month's update comes a bit later than usual, as we return from DrupalCon Nashville. Expect our April update to follow after shortly.

Representing Drupal at Google's CMS Leadership Summit

In mid-March, we attended the Google CMS Leadership Summit, as representatives of the Drupal project. The Summit was a one-day event hosted by Google to unite the 20 or so projects in the CMS space responsible for more than 50% of the content on the web.

The goal was to understand how to preserve an open web, by empowering better authoring experiences, content consumption, and performance in our CMS platforms.

This level of dialogue and engagement with an organization like Google is new and exciting for us, and we're looking forward to ongoing conversations, both with Google and with the other CMS project leaders they assembled at the event.

Drupal.org Updates Researching the anonymous traffic to Drupal.org

One of the focuses of the Drupal Association in 2018 has been to better understand our audience. When it comes to users who register on Drupal.org, and our DrupalCon attendees, we have quite a bit of information about who our users are.

However, when it comes to the wider ecosystem of Drupal users (evaluators and end-users who do not have Drupal.org accounts) we've been largely in the dark for most of the project's history. One way we want to improve this is by working with Drupal Core to add telemetry to Drupal, but that is an effort that will take some time.

In the meantime, we've implemented several Audience Insight tools to help us learn more about our anonymous users. Privacy is always a paramount concern, so we chose only insight tools which provide aggregate, anonymized data, and we wrapped those tools in our own implementation of Do-Not-Track so that we could ensure that user privacy preferences are respected.

The table below demonstrates the job functions held by the anonymous visitors to Drupal.org. (Please note: these job functions might be held within any kind of industry, this data is about the user's role, not their target market).

Job Function

D.O Front Page Visitors

All D.O Visitors

Diff

Engineering

26.20%

44.90%

-18.70%

Information Technology

14%

16.40%

-2%

Business Development

11.60%

9.60%

2.00%

Entrepreneurship

10.30%

10.70%

-0.40%

Arts and Design

7.70%

5.30%

2.40%

Media and Communication

6.60%

6%

0.60%

Marketing

6.30%

3.70%

2.60%

Education

6.10%

4.60%

1.50%

Operations

5.20%

3.50%

1.70%

Program and Project Management

4.30%

4.20%

0.10%

Sales

4.20%

2.60%

1.60%

Consulting

2.90%

3.30%

-0.40%

Research

2.40%

1.70%

0.70%

Community and Social Services

2.40%

1.80%

0.60%

Administrative

2.30%

1.30%

1.00%

We've used this data to inform the redesign of Drupal.org, as well as our new persona pages. Learn more about that process in our April update. The redesign work was carried out in collaboration with SixEleven, who also produced the DrupalCon brand and design for DrupalCon Nashville.

Preparing for DrupalCon Nashville

In the lead up to DrupalCon Nashville in April, the team was in high-gear preparing for the event. We participated in a panel about the future of pull requests on Drupal.org, the public board meeting, and handled the keynote livestream process.

DrupalCon is always an incredible opportunity for the team to connect with the community about upcoming initiatives, drupal.org support requests, and to plan for the future.

We were happy to see so many of you there, and we'll talk more about this in our April update.

Documentation enhancements

Our efforts to improve the quality of Drupal's documentation continued in March and April, as we added features:

  • New D7/D8 guides are now automatically approved, so new project contributors aren't blocked on documenting their projects.
  • Added Drupal version to page title for better searchability.
  • Follow/Unfollow links are available directly on the discuss page of any documentation.
In-context links to newer and older releases

To ensure that users are aware when there are newer releases than the one they may be looking at, we now provide newer and older release history on release nodes. In the sidebar of any release page you will see links and dates to related releases. Among other things, we hope this will prevent users from accidentally installing an older release when another new one has just come out!  

Email notifications for new maintainers

Encouraging succession planning in module maintership is an incredible challenge for any open source project. We want to encourage maintainers to invite contributors to their projects to help maintain those projects, but we recognize that we also have to make sure the appropriate tools are in place to make this a smooth process.

To make sure that new maintainers of projects are welcomed into the fold, we've added email notifications to let a user know when they've been added as a project co-maintainer. If you are invited by an existing maintainer of a project to help maintain it, you should now receive a warm welcome.

Security Release SA-CORE-2018-002

The Drupal Association Engineering Team collaborated with the Security Working Group and Security Team to coordinate 3 significant security releases in March and April.

The primary release was SA-CORE-2018-002, a highly critical security release for Drupal 7 and 8. For more information about all Drupal security releases and PSAs, please visit our security portal.

The volunteer Security Team has always been a tremendous asset to our community, and the Drupal Association is proud to support their work.

Infrastructure Updates DrupalCI: Support for testing themes

DrupalCI has enabled support for testing Themes, so now Theme projects on Drupal.org can include tests. This has become more and more necessary as javascript becomes critical to modern web design, and we hope this will help accelerate the build out of themes for Drupal 8 and increase their quality.

———

As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who make it possible for us to work on these projects. In particular we want to thank:

If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.

Follow us on Twitter for regular updates: @drupal_org, @drupal_infra

Mediacurrent: Friday 5: 5 Questions About Integrating Drupal Data with Component Templates

Main Drupal Feed - Fri, 04/27/2018 - 15:47

Happy Friday everyone. This episode we are joined by Anthony Fournier to talk about his experience in taking the data from Drupal and making it available for component based themes.

Drupal blog: Promoting the Drupal community from within the Drupal software

Main Drupal Feed - Fri, 04/27/2018 - 15:29

This blog has been re-posted and edited with permission from Dries Buytaert's blog. Please leave your comments on the original post.

Jacob Rockowitz recently posted a blog post with ideas about how we can make Drupal more welcoming.

What I found most interesting about Jacob's blog post is that he makes the point that every WordPress site (not WordPress.org) has an 'About WordPress' section in the administration backend that shows both WordPress' values and contributor credits.

This could be an interesting approach for Drupal and is an idea worth exploring. Today, Drupal's values and principles and Drupal's contribution credits live on Drupal.org, but not in the Drupal software itself. When done well, it's probably one of the most impactful ways to educate people and organizations that are new to Drupal about our community and open source. And by having credits in the software, we'd inspire more people and organizations to contribute back. It's an interesting idea.

Editor's note: There is a proposed initiative in the Drupal core ideas queue for adding a channel for project communication in core.

Dries Buytaert: How Drupal influences other Open Source projects

Main Drupal Feed - Fri, 04/27/2018 - 14:23

If you are interested in Open Source and have some time this weekend, watch Steve Francia's DrupalCon keynote called "Drupal and the secret of my success". Steve has been involved in Open Source for over 20 years, and has had the unique opportunity to lead three of the most successful Open Source companies in history. He was Chief Developer Advocate of MongoDB, Chief Operator of Docker, and now he is the Product Lead for the Go programming language at Google. Watch the video to hear Steve's personal story about how Drupal influenced his career, in addition to influencing MongoDB, Docker and Go. I don't often get emotional, but I had to wipe a few tears away during his presentation. Thanks for telling your story and being an inspiration, Steve!

Mobomo: Key Drupal Taxonomy: Part 2

Main Drupal Feed - Thu, 04/26/2018 - 17:35

In our previous blog post, we gave a brief intro to some terms that we believe are necessary to understand the basics of Drupal.   Here we have what we believe to be the next round of terms that we consider necessary to understanding those basics. Recently, we had the opportunity to assist Matrix AMC in migrating from Drupal 6 to Drupal 8.  They were unable to use their website because of the version of Drupal that their website was hosted on was out of date and no longer supported by the Drupal community. While these specific terms are consistent across Drupal versions, they are crucial to understanding the importance of being up to date in with your version of Drupal.      

 

  1. Block– the boxes visible in the regions of a Drupal website.
    1. Most blocks (e.g. recent forum topics) are generated on-the-fly by various Drupal modules, but they can be created in the administer blocks area of a Drupal site.
  2. Region-  defined areas of a page where content can be placed. Different themes can define different regions so the options are often different per-site. Basic regions include:
    1. Header
    2. Footer
    3. Content
    4. Left sidebar
    5. Right Sidebar
  3. Roles- a name for a group of users, to whom you can collectively assign permissions. There are two predefined, locked roles for every new Drupal installation:
    1. Authenticated User- anyone with an account on the site.
    2. Anonymous User- those who haven’t yet created accounts or are not logged in.
  4. WYSIWYG- What You See Is What You Get; An acronym used in computing to describe a method in which content is edited and formatted by interacting with an interface that closely resembles the final product.
  5. Book- a set of pages tied together in a hierarchical sequence, perhaps with chapters, sections, or subsections.  Books can be used for manuals, site resource guides, Frequently Asked Questions (FAQs), etc.
  6. Breadcrumbs- the set of links, usually near the top of the page, that shows the path you followed to locate the current page.
    1. The term breadcrumbs is borrowed from Hansel and Gretel, who left crumbs of bread along their path so they could find their way back out of the forest.
  7. Form mode- this is a way to customize the layout of an entity’s edit form.
  8. Multisite- a feature of Drupal that allows one to run multiple web sites from the same Drupal codebase.
  9. Patch- a small piece of software designed to update or fix problems with a computer program or its supporting data.
    1. This includes fixing bugs, replacing graphics and improving the usability or performance.
  10. User- the user interacting with Drupal. This user is either anonymous or logged into Drupal through its account.

 

 

The post Key Drupal Taxonomy: Part 2 appeared first on .

Chapter Three: Recruit more effectively with Taleo-integrated Drupal

Main Drupal Feed - Thu, 04/26/2018 - 17:07

Most corporate websites have a Career section where people can find out what jobs are open. These sections can range from just a few standing openings to hundreds of vacant positions across multiple job types that open and close frequently. Larger companies traditionally use HR software systems to manage this ebb and flow.

One popular and powerful HR system is Taleo. Many companies simply link offsite to the taleo.com listing, which serves as the company’s only place to see and apply to openings. Other times, that same listing gets embedded on the company’s career section. As you can see in the user journey below for our client MemorialCare, this got the job done, but didn’t really convey a company’s brand or culture.

Jeff Geerling's Blog: Drupal Camp St. Louis is taking a break for 2018

Main Drupal Feed - Thu, 04/26/2018 - 16:57

The St. Louis Drupal Users Group has hosted a Drupal Camp in the 'Gateway to the West' for four years (since 2014), but this year, the organizers have decided to take a year off, for various reasons. Our camp has grown a little every year, and last year we even increased the scope and usefulness of the camp even more by adding a well-attended training day—but life and work have taken precedence this year, and nobody is able to take on the role of 'chief organizer'.

All is not lost, however! There are other great camps around the Midwest, and this year we're directing everyone to our northern neighbors, in Iowa: DrupalCorn Camp is going to be held in Des Moines, Iowa, from September 27-30, 2018!

Dries Buytaert: Promoting the Drupal community from within the Drupal software

Main Drupal Feed - Thu, 04/26/2018 - 15:57

Jacob Rockowitz recently posted a blog post with ideas about how we can make Drupal software more welcoming.

What I found most interesting about Jacob's blog post is that he compares WordPress' approach of promoting its values and giving credit with Drupal's. He makes the point that every WordPress site (not WordPress.org) has an 'About WordPress' section in the administration backend that shows both WordPress' values and contributor credits.


This could be an interesting approach for Drupal and is an idea worth exploring. Today, Drupal's values and principles and Drupal's contribution credits live exclusively on Drupal.org, but not in the Drupal software itself. When done well, it's probably one of the most impactful ways to educate people and organizations that are new to Drupal about our community and open source. And by having credits in the software, we'd inspire more people and organizations to contribute back. It's an interesting idea.

Texas Creative: Updating Drupal Contrib Modules on Pantheon.io

Main Drupal Feed - Thu, 04/26/2018 - 15:40

This guide describes the process for performing updates on “contrib” modules for a Drupal site hosted on the Pantheon platform.

Read More

Acquia Developer Center Blog: Decoupling Drupal 8 Core: Retrieving and Manipulating Content with Core REST

Main Drupal Feed - Thu, 04/26/2018 - 15:11

As we saw in a previous installment of Experience Express, because Drupal has a HAL-compliant REST API available out of the box with minimal configuration, you can easily provision an API that can immediately be employed to consume content entities and manipulate them from other applications. Now that we have successfully exposed content entities as REST resources, used Entity Access to govern permissions, and customized the formats and authentication mechanisms in use by the core REST API, it is now time to move into actually retrieving and manipulating that data.

Tags: acquia drupal planet

Acro Media: Drupal Commerce 2: How to Add a Store Using Default Fields

Main Drupal Feed - Thu, 04/26/2018 - 14:45

 

 

If all you run is a single eCommerce store using Drupal Commerce, adding store fields isn't something you really need to worry about. However, if you start adding additional online stores (multi-store) and/or run a brick-and-mortar store location in tandem with your online store, being able to separate the stores is important. In the case of brick-and-mortar stores, you probably want your customers to be able to view information about them that is unique to a physical store, such as location, hours, contact details, etc. With Drupal Commerce 2, you can do this easily and manage all of your stores from the same interface!

In this Acro Media Tech Talk video, we use our Urban Hipster Commerce 2 demo site to show you how to add and configure a new store using the default store fields. We don't go into adding new fields, but if you're familiar with configuring Drupal then it's not much different than any other type of content. This should get you started. The rest of Drupal Commerce works with multiple stores seamlessly.

Its important to note that this video was recorded before the official 2.0 release of Drupal Commerce. You may see some differences between this video and the current releases. The documentation is also evolving over time.

Urban Hipster Commerce 2 Demo site

This video was created using the Urban Hipster Commerce 2 demo site. We've built this site to show the adaptability of the Drupal 8, Commerce 2 platform. Most of what you see is out-of-the-box functionality combined with expert configuration and theming.

More from Acro Media Drupal modules in this demo

Sooper Drupal Themes: Out Now: Glazed Builder & Glazed Theme For Drupal 8! Check Out Our Revolutionary New Page Building Experience For Drupal

Main Drupal Feed - Thu, 04/26/2018 - 14:04

We Just Released Our Themes And Visual Pager Builder For Drupal 8, An Update We've Been Working On For A Year!

Introduction Video Of Glazed Builder For Drupal 8

view on sooperthemes.com if you can't see the video

When I started building Glazed Theme 3 years ago most Drupal Theme shops had gone out of business. It's not just that Drupal was in a weird place, with Drupal 8 unfinished and Drupal 7's future uncertain.. The market for Drupal Themes had never lived up to the expectations of the Drupal community like WordPress themes did in the their community.

Despite this adversity I decided to restart SooperThemes and invest all my time, energy, and money in Drupal themes once more.

Our new value proposition is no longer just themes. We developed a full Drupal stack including a flexible framework theme, a drag and drop builder, and a complete selection of turn-key demo websites that are based around our open source Glazed CMS Drupal distribution. For small Drupal projects we provide value by providing a complete Drupal website that looks great and is easy to customize. For Fortune 500 companies and some of the largest NGO's and government institutions in the world we now provide tremendous value with our Drupal page builder Glazed Builder.

The Idea That Will Revolutionize Your Drupal 8 & 7 Experience Today I'm proud to announce the release of all our products on Drupal 8! We reinvented the Drupal authoring and site building experience again for Drupal 8 with a Glazed Builder module that was built from the ground up to fit Drupal 8's archictecture and design principles. It has taken us a full year to upgrade all our products, including our page builder, Glazed framework theme, portfolio module, GridStack module, 15 demo themes and 15 installation profiles, and our Glazed Drupal distribution which will soon also have a D8 release on drupal.org. Built From The Ground Up For Drupal 8

Glazed Builder is different from Wix, Squarespace, or any other drag and drop builder: it's made for Drupal and deeply integrated with Drupal APIs. Glazed Builder acts as a Drupal field formatter and you can have multiple instances per page, for your footer, main content, and blocks. It automatically understands Drupal's revisioning system, language systems, and permissions. This makes it the most advanced visual page builder in the world from a website architecture perspective.

Our framework theme Glazed was also rebuilt using twig templates and the new Drupal 8 theme system.

Build, Write, And Edit Visually 

The experience of writing in Glazed Builder is easy like nothing else. You just click anywhere in a piece of content and start typing. Without any menus or network latency, our frontend application is the fast and distraction-free solution that Drupal content editors and marketers deserve! And thanks to the tight integration with Drupal's media systems you can upload and re-use media in Glazed Builder. It even provides easy settings to resize your images and add SEO fields like alt text and title text.

SooperThemes Is Super Fast! Need to edit an article or update the social links in your website's footer? Whatever the task it's just a single click away when using Glazed Builder. Because our page builder is a headless frontend application for Drupal it doesn't need to call the server for most tasks. Adding text, or marketing elements can happen instantly because there is no network delay. Even tasks that rely on Drupal like saving the page or loading a view happens very fast thanks to the expert programming by Drupal developers with at least 8 years of experience. Drag, Drop, Clone, Style

Our software is easy and intuitive to use because we designed it based on established best practices in user experience design. We stand on the shoulders of decades of research in computer interaction design and translated core concepts like dragging, typing, cloning, to a tool that seamlessly integrates with your Drupal website. Since we released the first beta version of Glazed Builder 3 years ago we made hundreds of improvements and have gone through many design changes based on feedback from our customers.

Save Time With Templates We have also made incredible progress in developing template features to improve workflow and productivity. You can save any element or collection of elements in the builder as a user template and it will instantly be accessible in every Glazed Builder instance on your website. We also creating page templates that you can use as a starting point on empty pages. Access A Complete Selection Of Marketing Tools For marketing staff Glazed Builder means liberation! No more need to hustle developers to code a landing page. Our builder provides anything from responsive layouts to countdown timers, sliders, and thousands of icons including the brand new Font Awesome 5 Pro set. Instead of posting a screenshot of marketing content here, I invite you to browse around sooperthemes.com and take a look at our product pages. Each page is built with Glazed Builder, even the blog post you're reading right now is build with Glazed Builder. We believe in eating our own dog food and as you might have guessed sooperthemes.com is themed with Glazed Theme as well. Enough about us.. Get 20% Off For A Limited Time Only

We've never in 3 years discounted our products this much because we believe in the value that we provide. However, because this release calls for celebration we offer 20% discount to new clients!

Remember that today is a great day to join because we won't wait long to disable this discount code after our Drupal 8 product launch!

You can use the discount by entering coupon code LAUNCH18 during checkout

Buy & Download Now

Try before you buy for free on trysooperthemes.com

OpenConcept: Owning a .ee - why I Chose to Start a European Company

Main Drupal Feed - Thu, 04/26/2018 - 13:57

I have to say that historically, I haven't had a good reason to think much about Estonia. It's just the first of the Baltic countries that we covered in history class in high-school. It wasn't until the FWD50 conference in Ottawa where this really shifted.

Siim Sikkut spoke about Estonia building up a digital government from the ground up. The contemporary Estonian government started only 1992, shortly after the WWW started. There were some bold leaders who decided to start not with what other countries had done, but to start digital. He mentioned e-Residency & the ease of starting a new business and I was intrigued.

I already own a digital business, so didn't sign up right away. I think that proximity generally is a bigger factor for our clients than nationality. I am still not sure what the financial opportunities of owning a European company are.

Reading about Estonia's X-Road, I got a sense of how citizens trust government. It is inspiring to see how much access Estonian citizens have to see and manage their own data. It is also amazing to see that Estonian citizens have the right to see who is looking at their file (in real time). It was interesting to see a small country experiment with creating "government as a platform".

I'm one of the co-founders of Civic Tech Ottawa. As an open source advocate, I have been watching the movement of both the open data and open government. Estonia's example kept coming up in discussions of countries that are doing it right. As far as principles for digital government, I was very impressed with the D5 Charter. The Digital 5 (D5) was Estonia, Israel, New Zealand, South Korea & the United Kingdom.

It was shortly after Canada joined (with Uruguay) signed the Charter it became the Digital 7 (D7). This made it real for Canada. Scott Brison put his political weight into shaping a Digital Government of Canada. Learning more about the Estonian system became much more important.

So I signed up to become an e-Resident, got my ID card at the Embassy and logged in to explore what I could of the X-Road. There's not much you can do as an e-Resident, so I decided I needed to also spin up an Estonian company. It wasn't quite as simple as I had been lead to believe. In part this was because I needed to secure a physical Estonian address.

Exploring their system I learned a bit about how the Estonian eID securely connects people to organizations. I needed to use the same card and process to login to several government sites. I also used it to verify that I am an Estonian e-Resident when registering OpenConcept.ee.

I could see first hand how the Estonian model leveraged open source and open standards. As a long time Drupal user I was very happy to see how much this open source CMS is being used in Estonia. Most government departments are using a common base. This allows them to have a consistent look/feel.

It also allows them to invest in common infrastructure to innovate on. With Drupal, they can leverage the community for security, accessibility & multi-lingual delivery. This allows real innovation, focusing on building a consistent secure eID infrastructure.

By focusing on the principles of the D5 Charter I do see a lot of opportunities. The individual technologies will change over time, but the foundation is open source and open standards. If sharing and learning remain key, then governments may one day be real contributors to the open web.

Topic: 

Evolving Web: Let’s celebrate DrupalCamp Montreal’s 10th anniversary!

Main Drupal Feed - Thu, 04/26/2018 - 13:16

The 10th annual DrupalCamp Montreal will be held Thursday, June 14th to Sunday, June 16th at the John Molson School of Business.

While it will be my first DrupalCamp, I am very excited to be part of the organizing committee. I am helping promote the event through social media channels and the local community. I am not a web developer but I think whether you are a Drupal developer or not, I’m sure you’ll have a lot to learn from this event.

5 reasons you should attend:

  • Meet people in the web community

  • Learn about Drupal and other web technologies

  • Learn about web strategy and design

  • Find collaborators for your next project

  • Share your knowledge and your experience with other tech lovers

Who should consider attending:

  • Site builders, developers and site admins who are new to Drupal

  • Drupal experts

  • Project managers, decision makers, content writers

  • Web marketers and designers

We Want You to Speak at DrupalCamp Montreal!

This year, we’re thinking outside the box and encouraging speakers to present on topics beyond the sphere of Drupal. So if you have content strategy techniques to show, a new JavaScript framework you want to talk about, or a CSS technique that you’re excited to use, this is your opportunity to share your ideas with the community and get experience presenting.

Any topic related to web development or Drupal is welcome. The four main tracks of the camp: site building, development, strategy & business and front-end. Sessions can be given in either French or English.

We’re also accepting session proposals until 11th of May, so if you have a great idea or know someone who does, let us know!

Learn Drupal!

The training day on June 14th includes two “What is Drupal?” training sessions (delivered by our very own Suzanne Dergacheva) where you can learn the basics of Drupal:

  • French from 9am to 12pm

  • English from 1pm at 4pm

You can see the details of training here.

Friday 15th of June and Saturday 16th of June will include sessions about Drupal, web technology, strategy, and design.

Registration is now open for the DrupalCamp Montreal 2018. You can sign up for both training or sessions.

Volunteer!

There is another way to join in the camp! If you are passionate about Drupal and web technology and you want to help make the DrupalCamp a success, you can consider volunteering at the event. To become a volunteer, you can fill out the form here.

Celebrate 10 Years of DrupalCamp Montreal

We are becoming a big community! Evolving Web was one of the web agencies that helped organize the first DrupalCamp in 2008 and approximately 50 people attended . This year, we are very proud to be sponsoring the event at the “Diamond” level and we are expecting around 200 - 250 attendees.

See you at the camp!

+ more awesome articles by Evolving Web

진해출장샵》 {카톡er25}er663,c0M 진해출장업소 진해콜걸 진해출장만남추천 진해출장마사지 출장아가씨 진해모텔출장 진해출장안마 진해애인대행

Drupal News Org - Thu, 04/26/2018 - 10:41

진해 출장 샵 "{카톡 er25} er663, c0M 진해 출장 업방 진하 출산 만남 추천 진해 출석 수 출주 아가씨 진해 모텔 출석 진해 출장 안마 진해 애인 대행 진해 출소 샵"카일 er25} er663, c0M 진해 출현 업소 진해 콜걸 진해 출장 만남 추천 진해 출석 수 출주 아가씨 진해 모텔 출석 진가 출산 안마 진해 애인 대행 진해 출장 샵 "진리 출장 업장 진창 콜걸 진해 출장 만남 추천 진해 출석 수 출주 아가씨 진해 모텔 출품 진해 출소 안마 진해 애인 대행 진해 출장 샵 "{카톡 er25} er663, c0M 진해 출장 업방 진화 콜걸 진해 출석 만남 추천 진해 출석 수 출주 아가씨 진해 모텔 출석 진해 출장 안마 진해 애인 대행 진해 출소 샵"카일 er25} er663, c0M 진해 출장 업소 진해 콜걸 진해 출장 만남 추천 진해 출석 기념일 출석 아가씨 진해 모텔 출장 진해 출장 안마 진해 애인 대행

Drupal version: Drupal 8.x

BootBase

Drupal Themes - Thu, 04/26/2018 - 09:49

Matt Glaman: Enabling RESTful web service interfaces in Drupal 8

Main Drupal Feed - Thu, 04/26/2018 - 09:00
Enabling RESTful web service interfaces in Drupal 8 Drupal 8 ships with the RESTful Web Services module which allows you to expose various API endpoints for interacting with your Drupal site. While the community is making a push for the JSON API module, I have found the core' RESTful module to be pretty useful when I have custom endpoints or need to implement Remote Procedure Calls (RPC) endpoints. However, using the module and enabling endpoints is a bit rough. So, let's cover that! Also note, this blog covers the content from the introduction of the Web Services chapter from the Drupal 8 Development Cookbook.

Pages