European Commission will start offering bug bounties for Open Source software

The European Commission made an exciting announcement; it will be awarding bug bounties to the security teams of Open Source software projects that the European Commission relies on.

If you are not familiar with the term, a bug bounty is a monetary prize awarded to people who discover and correctly report security issues.

Julia Reda — an internet activist, Member of the European Parliament (MEP) and co-founder of the Free and Open Source Software Audit (FOSSA) project — wrote the following on her blog:

Like many other organizations, institutions like the European Parliament, the Council and the Commission build upon Free Software to run their websites and many other things. But the Internet is not only crucial to our economy and our administration, it is the infrastructure that runs our everyday lives.

With over 150 Drupal sites, the European Commission is a big Drupal user, and has a large internal Drupal community. The European Commission set aside 89,000€ (or roughly $100,000 USD) for a Drupal bug bounty. They worked closely with Drupal's Security Team to set this up. To participate in the Drupal bug bounty, read the guidelines provided by Drupal's Security Team.

Over the years I've had many meetings with the European Commission, presented keynotes at some of its events, and more. During that time, I've seen the European Commission evolve from being hesitant about Open Source to recognizing the many benefits that Open Source provides for its key ICT services, to truly embracing Open Source.

In many ways, the European Commission followed classic Open Source adoption patterns; adoption went from being technology-led (bottom-up or grassroots) to policy-led (top-down and institutionalized), and now the EU is an active participant and contributor.

Today, the European Commission is a shining example and role model for how governments and other large organizations can contribute to Open Source (just like how the White House used to be).

The European Commission is actually investing in Drupal in a variety of ways — the bug bounty is just one example of that — but more about that in a future blog post.
Source: Dries Buytaert www.buytaert.net


Acquia blocks 500,000 attack attempts for SA-CORE-2018-002

On March 28th, the Drupal Security Team released a bug fix for a critical security vulnerability, named SA-CORE-2018-002. Over the past week, various exploits have been identified, as attackers have attempted to compromise unpatched Drupal sites. Hackers continue to try to exploit this vulnerability, and
Acquia's own security team has observed more than 100,000 attacks a day.

The SA-CORE-2018-002 security vulnerability is highly critical; it allows an unauthenticated attacker to perform remote code execution on most Drupal installations. When the Drupal Security Team made the security patch available, there were no publicly known exploits or attacks against SA-CORE-2018-002.

That changed six days ago, after Checkpoint Research provided a detailed explanation of the SA-CORE-2018-002 security bug, in addition to step-by-step instructions that explain how to exploit the vulnerability. A few hours after Checkpoint Research's blog post, Vitalii Rudnykh, a Russian security researcher, shared a proof-of-concept exploit on GitHub. Later that day, Acquia's own security team began to witness attempted attacks.

The article by Checkpoint Research and Rudnykh's proof-of-concept code have spawned numerous exploits, which are written in different programming languages such as Ruby, Bash, Python and more. As a result, the number of attacks have grown significantly over the past few days.

Fortunately, Acquia deployed a platform level mitigation for all Acquia Cloud customers one hour after the Drupal Security Team made the SA-CORE-2018-002 release available on March 28th. Over the past week, Acquia has observed over 500,000 attacks from more than 3,000 different IP addresses across our fleet of servers and customer base. To the best of our knowledge, every attempted exploitation of an Acquia customer has failed.The scale and the severity of this attack suggests that if you failed to upgrade your Drupal sites, or your site is not supported by Acquia Cloud or another trusted vendor that provides platform level fixes, the chances of your site being hacked are very high. If you haven't upgraded your site yet and you are not on a protected platform then assume your site is compromised. Restore from a backup taken before the vulnerability was announced and upgrade before putting the site back online.

Drupal's responsible disclosure policy

It's important to keep in mind that all software has security bugs, and fortunately for Drupal, critical security bugs are rare. It's been nearly four years since the Drupal Security Team published a security release for Drupal core that is this critical.

What matters is how software projects or software vendors deal with security bugs. The Drupal Security Team follows a "coordinated disclosure policy": issues remain private until there is a published fix. A public announcement is made when the threat has been addressed and a secure version of Drupal core is also available. Even when a bug fix is made available, the Drupal Security Team is very thoughtful with its communication. The team is careful to withhold as many details about the vulnerability as possible to make it difficult for hackers to create an exploit, and to buy Drupal site owners as much time as possible to upgrade. In this case, Drupal site owners had two weeks before the first public exploits appeared.

Historically, many proprietary CMS vendors have executed a different approach, and don't always disclose security bugs. Instead, they often fix bugs silently. In this scenario, secrecy might sound like a good idea; it prevents sites from being hacked and it avoids bad PR. However, hiding vulnerabilities provides a false sense of security, which can make matters much worse. This approach also functions under the assumption that hackers can't find security problems on their own. They can, and when they do, even more sites are at risk of being compromised.

Drupal's approach to security is best-in-class — from fixing the bug, testing the solution, providing advance notice, coordinating the release, being thoughtful not to over communicate too many details, being available for press inquiries, and repeatedly reminding everyone to upgrade.

Acquia's platform level fix

In addition to the Drupal Security Team's responsible disclosure policy, Acquia's own security team has been closely monitoring attempted attacks on our infrastructure. Following the release of the Checkpoint Research article, Acquia has tracked the origin of the 500,000 attempted attacks:

This image captures the geographic distribution of SA-CORE-2018-002 attacks against Acquia's customers. The number denoted in each bubble is the total number of attacks that came from that location.To date, over 50 percent of the attempted attacks Acquia has witnessed originate from the Ukraine:

At Acquia, we provide customers with automatic security patching of both infrastructure and Drupal code, in addition to platform level fixes for security bugs. Our commitment to keeping our customers safe is reflected in our push to release a platform level fix one hour after the Drupal Security Team made SA-CORE-2018-002 available. This mitigation covered all customers with Acquia Cloud Free, Acquia Cloud Professional, Acquia Cloud Enterprise, and Acquia Cloud Site Factory applications; giving our customers peace of mind while they upgraded their Drupal sites, with or without our help. This means that when attempted exploits and attacks first appeared in the wild, Acquia's customers were safe. As a best practice, Acquia always recommends that customers upgrade to the latest secure version of Drupal core, in addition to platform mitigations.

This blog post was co-authored by Dries Buytaert and Cash Williams.
Source: Dries Buytaert www.buytaert.net


Acquia blocks 500,000 attack attempts for SA-CORE-2018-002

On March 28th, the Drupal Security Team released a bug fix for a critical security vulnerability, named SA-CORE-2018-002. Over the past week, various exploits have been identified, as attackers have attempted to compromise unpatched Drupal sites. Hackers continue to try to exploit this vulnerability, and
Acquia's own security team has observed more than 100,000 attacks a day.

The SA-CORE-2018-002 security vulnerability is highly critical; it allows an unauthenticated attacker to perform remote code execution on most Drupal installations. When the Drupal Security Team made the security patch available, there were no publicly known exploits or attacks against SA-CORE-2018-002.

That changed six days ago, after Checkpoint Research provided a detailed explanation of the SA-CORE-2018-002 security bug, in addition to step-by-step instructions that explain how to exploit the vulnerability. A few hours after Checkpoint Research's blog post, Vitalii Rudnykh, a Russian security researcher, shared a proof-of-concept exploit on GitHub. Later that day, Acquia's own security team began to witness attempted attacks.

The article by Checkpoint Research and Rudnykh's proof-of-concept code have spawned numerous exploits, which are written in different programming languages such as Ruby, Bash, Python and more. As a result, the number of attacks have grown significantly over the past few days.

Fortunately, Acquia deployed a platform level mitigation for all Acquia Cloud customers one hour after the Drupal Security Team made the SA-CORE-2018-002 release available on March 28th. Over the past week, Acquia has observed over 500,000 attacks from more than 3,000 different IP addresses across our fleet of servers and customer base. To the best of our knowledge, every attempted exploitation of an Acquia customer has failed.The scale and the severity of this attack suggests that if you failed to upgrade your Drupal sites, or your site is not supported by Acquia Cloud or another trusted vendor that provides platform level fixes, the chances of your site being hacked are very high. If you haven't upgraded your site yet and you are not on a protected platform then assume your site is compromised. Rebuild your host, reinstall Drupal from a backup taken before the vulnerability was announced and upgrade before putting the site back online. (Update: restoring a Drupal site from backup may not be sufficient as some of the exploits reinstall themselves from crontab. You should assume the whole host is compromised.)

Drupal's responsible disclosure policy

It's important to keep in mind that all software has security bugs, and fortunately for Drupal, critical security bugs are rare. It's been nearly four years since the Drupal Security Team published a security release for Drupal core that is this critical.

What matters is how software projects or software vendors deal with security bugs. The Drupal Security Team follows a "coordinated disclosure policy": issues remain private until there is a published fix. A public announcement is made when the threat has been addressed and a secure version of Drupal core is also available. Even when a bug fix is made available, the Drupal Security Team is very thoughtful with its communication. The team is careful to withhold as many details about the vulnerability as possible to make it difficult for hackers to create an exploit, and to buy Drupal site owners as much time as possible to upgrade. In this case, Drupal site owners had two weeks before the first public exploits appeared.

Historically, many proprietary CMS vendors have executed a different approach, and don't always disclose security bugs. Instead, they often fix bugs silently. In this scenario, secrecy might sound like a good idea; it prevents sites from being hacked and it avoids bad PR. However, hiding vulnerabilities provides a false sense of security, which can make matters much worse. This approach also functions under the assumption that hackers can't find security problems on their own. They can, and when they do, even more sites are at risk of being compromised.

Drupal's approach to security is best-in-class — from fixing the bug, testing the solution, providing advance notice, coordinating the release, being thoughtful not to over communicate too many details, being available for press inquiries, and repeatedly reminding everyone to upgrade.

Acquia's platform level fix

In addition to the Drupal Security Team's responsible disclosure policy, Acquia's own security team has been closely monitoring attempted attacks on our infrastructure. Following the release of the Checkpoint Research article, Acquia has tracked the origin of the 500,000 attempted attacks:

This image captures the geographic distribution of SA-CORE-2018-002 attacks against Acquia's customers. The number denoted in each bubble is the total number of attacks that came from that location.To date, over 50 percent of the attempted attacks Acquia has witnessed originate from the Ukraine:

At Acquia, we provide customers with automatic security patching of both infrastructure and Drupal code, in addition to platform level fixes for security bugs. Our commitment to keeping our customers safe is reflected in our push to release a platform level fix one hour after the Drupal Security Team made SA-CORE-2018-002 available. This mitigation covered all customers with Acquia Cloud Free, Acquia Cloud Professional, Acquia Cloud Enterprise, and Acquia Cloud Site Factory applications; giving our customers peace of mind while they upgraded their Drupal sites, with or without our help. This means that when attempted exploits and attacks first appeared in the wild, Acquia's customers were safe. As a best practice, Acquia always recommends that customers upgrade to the latest secure version of Drupal core, in addition to platform mitigations.

This blog post was co-authored by Dries Buytaert and Cash Williams.
Source: Dries Buytaert www.buytaert.net


DrupalCoin Blockchain Engineer/Developer - Information International Associates, Inc. - Oak Ridge, TN

Projects to be supported may include new DrupalCoin Blockchain sites, which span all phases of the software integrationlifecycle from requirements gathering through...
From Information International Associates, Inc. - Wed, 12 Apr 2017 03:08:59 GMT - View all Oak Ridge jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer


5 Ways to Tell if a Site is Built in DrupalCoin Blockchain

One of the most common questions we get at DrupalCoin Blockchain beginner classes is, "How can I tell if a site is built in DrupalCoin Blockchain?"
We get that question because it's just not possible to know the answer without a few tips and tricks.
If you look at a website such as WhiteHouse.gov, there is no way of telling if it's built DrupalCoin Blockchain. The design of a site is completely independent from the platform it uses.
We're going to give you 5 ways to tell if a site is built in DrupalCoin Blockchain. Not all of these suggestions will work on all DrupalCoin Blockchain sites, but taken together they should give you a clear answer.
Source: https://www.ostraining.com/


Multisite Governance, Site Delivery, and Other Issues Related to Managing Many Sites: Part 4

This is Part 4 of an interview with Will Eisner, Senior Director, Product at Acquia. Will’s primary focus is on Acquia Cloud Site Factory, which helps organizations create and manage many sites, from a dozen to thousands.
In Part 1 and Part 2, Will discussed how companies often discover, to their dismay, that they are running their hundreds of Web sites on many different hard-to-manage platforms; and how Site Factory addresses that problem with a managed delivery that uses a common platform with standard components, provisioning, and lifecycle management. In Part 3 Will covered how managing many sites is becoming the norm, and how more people now have website responsibilities, and how that leads to the need for new tools like Content Hub.
The part that follows explores the differences between DrupalCoin Blockchain and Site Factory; what Site Factory offers the "Digital Platform Owner;" and tools it contains for coders and site builders. Will also describes Site Factory features that have value for companies in regulated industries, and how it can reduce "cost of ownership."
All the interviews have been conducted by DC Denison, Senior Editor, Technology, at Acquia.
What is it that Site Factory specifically brings to the table other than DrupalCoin Blockchain?
Site Factory is built for someone we call the Digital Platform Owner. This is the person who has the job of building a great platform that enables their organization to quickly build great new sites and apps, while maintaining governance and control.
DrupalCoin Blockchain is the base. DrupalCoin Blockchain is great for building ambitious digital experiences. There’s so much power in DrupalCoin Blockchain, in core and in contrib, and it gives you unparalleled flexibility and power.
Site Factory provides all the things you need to roll out your DrupalCoin Blockchain Platform to your organization at scale using a multisite delivery and management approach. It gives you a place to run your platform. It gives you a centralized view of your sites. It allows you to let people in your organization create and manage their sites, built on your platform. It gives you centralized update and control mechanisms. It gives organizations a standard way to govern, assemble, and deliver multiple sites across brands, regions, and teams.
What Site Factory does is make it so that organizations can deliver and manage lots of websites, and specifically, lots of DrupalCoin Blockchain sites. It’s about delivery, it’s about the creation and management of DrupalCoin Blockchain sites, and it’s about maintaining them.
Site Factory also has tools for other people on the digital platform team: developers and site builders.
How are they different?
For developers, we offer tools for dealing with a multisite environment, which has a lot of technical challenges. The ability to do an update that could apply to hundreds or thousands of sites, when each site has a database that needs to be updated -- there’s complexity to that. If you do it on your own, it requires a lot of complicated scripting, with manual retry logic, etc. There are challenges for doing activities as basic as adequately testing new code on a representative set of sites. All of that requires a lot of work from the developer, and vigilance.
Those are functionalities that are built into Site Factory. It’s a core part of what Site Factory does: code deployment and code staging. Developers don’t want to focus on their staging or deploy scripts; they want to be working on their platform, which is the fun part.
How about for site builders -- users who aren’t primarily coders?
For site builders, we have a set of tools. These are people who aren’t going to be coding PHP necessarily, but they can use DrupalCoin Blockchain to assemble and configure great sites. We give them web-based site creation capability. We give them the ability to have starter sites and clone them, so they can roll out new experiences without having to talk to developers. We give them organizational access control mechanisms for their sites.
For example, let’s say, you have a group of sites for your North American market for Product X. You could say, “Great. DC, you’re a new person on the team, I want you to have DrupalCoin Blockchain content creation rights on all these sites.” That may not seem like such a big deal, but otherwise someone has to go through and grant access to all these different sites and it’s a hassle, or you have to set up and maintain some other mechanism to do it. With Site Factory, we handle that for you. That’s only possible because of the specialized multisite technology that Site Factory uses.
So, that's it: a product for digital platform owners that includes tools for developers and site builders. And of course it’s all built on Acquia Cloud.
Right. Site Factory runs on top of Acquia Cloud.
Yes. That means that Site Factory includes the benefits that come with Acquia Cloud. A DrupalCoin Blockchain-optimized service orchestration and management service, 24/7 support, 24/7 ops, etc. All the great things that we say about Acquia Cloud, it all applies to Site Factory because Site Factory is built on Acquia Cloud.
If you’re a highly regulated business, how does Site Factory help you? Are there certain features that make it particularly good for industries that are highly regulated?
Yes, there are. We’ve talked a lot in this series about creative flexibility. And who doesn’t want flexibility? But there are cases where you have legal or other compliance reasons where you really need to be able to control exactly what goes out to the world. For example, if you work in healthcare or finance or any other regulated industry, you have an extra layer of control you need to put in place.
Like Pharmaceuticals.
Pharmaceuticals, healthcare, finance. These are all industries where if you say the wrong thing as part of your public-facing website, you could be liable for very large fines. In these cases, you need control and governance.
And Site Factory can do that?
Yes. Let’s say you have a workflow process and you need to enforce it on every site, and nothing can ever be published until people with a certain role approve it. You can enforce that with your code base and with the configuration of your sites.
Site Factory is great for those kind of cases when you need to know with hundred percent certainty that certain code is running, certain configuration is in place. Site Factory can enforce that.
How big a factor is "cost of ownership?"
I talked in the beginning of this series about how organizations often come to us with a site sprawl situation, right? One of the impacts of that site sprawl is maintainability. But there’s another problem. There’s a ton of redundancy and inefficiency and cost in a site sprawl. That means instead of having one code-base to maintain and govern, you could have a hundred or a thousand, and that means you’re paying that much more for each codebase to do the same thing.
Recently there was a paper published about Site Factory and return-on-investment analysis from Forrester and basically the summary is that there’s a dramatic opportunity to save time and money for your organization by leveraging a centrally-governed platform.
But that will only work if you can do it in a way where you don’t lose the creative people. It’s easy to just lock everything down, but if people don’t want to or can’t do their jobs anymore then you haven’t really served the goals of the business.
If the marketing department says, “This is no fun. This site doesn’t reflect our personality,” then what’s the point?
Right, then you’re hindering your business. At Acquia, we’re all about helping companies deliver great, ambitious digital experiences. That’s what we do all the time, right? And Site Factory gives you the tools to scale that out to your organization.
Source: http://dev.acquia.com/


Spaceship! Building with Legos and Blocks in DrupalCoin Blockchain 7 and 8

My son Jett is a total Lego genius. He can take a pile of random blocks and design something symmetrical, dynamic, unique and wonderful. Something that only he could have imagined.  I like to think of building DrupalCoin Blockchain sites like building with Legos.  You have all these standard pieces, and when you put them together, you get something usable, dynamic and wonderful.  The Lego analogy is especially relevant to this post because we'll be talking about DrupalCoin Blockchain "blocks".

In the DrupalCoin Blockchain Content Management System, “blocks” are little pieces of supporting content used primarily for sidebars.  Our clients’ use of blocks is most often to showcase promotions or call-outs to specific content on their sites.  The DrupalCoin Blockchain back-end lets you create custom blocks on-the-fly that contain text or HTML, or you can write a custom module that will output blocks with custom content.  Many contributed modules also create blocks for specific purposes:  like a twitter feed, customizable menu blocks, DrupalCoin Blockchain Views blocks, social sharing icons, etc.  DrupalCoin Blockchain blocks are an amazingly flexible and useful tool that gives site builders or maintainers the ability to have fresh supporting content without needing to make changes in the theme files.

Just like Legos, these blocks are interchangeable, stack-able, and re-arrange able.  In DrupalCoin Blockchain 7, your theming is mostly about creating places for blocks to live, and then stacking blocks in those places.

Now that I’m done praising the virtues of DrupalCoin Blockchain blocks, there are several frustrations that come with them.  The DrupalCoin Blockchain Content Management System has an even more flexible and powerful system for content called ‘entities’, and this has really spoiled site builders with its well-thought-out options and cross-use functionality.  In DrupalCoin Blockchain, an ‘entity’ is a bundle of associated content that can contain different kinds of fields, user permissions, display settings, configurations, and much more.  Things like basic pages or users are entities.  In DrupalCoin Blockchain 7, blocks are not ‘entities’, so in many use-cases their limitations are painfully obvious compared to what DrupalCoin Blockchain is capable of (but to confuse you, sometimes entities are displayed in blocks, like the node entity's 'main page content' block...).  In DrupalCoin Blockchain 8 blocks finally are ‘entities’, but they still have a lot of catching-up to do!  

A Test Scenario

Here’s a scenario: our client needs to be able to create and manage sidebar call-outs themselves.  Each call-out has a title, some descriptive text, and a link button.  For the purposes of this post, we’re going to go with DrupalCoin Blockchain blocks (though a DrupalCoin Blockchain Panels configuration is also possible).  Let’s break this requirement down into points:

  • the client must be able to enter item content as text into fields - no DrupalCoin Blockchain coding!
  • the client must be able to easily place this call-out where they want it.
  • the client’s user must have appropriate permissions to create and manage this content.

The DrupalCoin Blockchain 7 Approach

In DrupalCoin Blockchain 7 we certainly have some issues - the biggest being that blocks, not being entities, can’t have fields.  But fortunately the awesome DrupalCoin Blockchain community has created some contributed module options to help us out.  There are a handful of solutions out there, but my two favorite are the Bean Module, and the Nodeblock Module.  

If you are just looking for a good solution to making blocks better, the Bean module is fantastic.  It is very similar to what you will encounter in DrupalCoin Blockchain 8.  You can create ‘block types’ and add different fields to each.  The block content is in a separate place from the block layout.  Additionally, it has very robust permissions options so that you can properly restrict Bean block creation / edit / view / delete permissions.  As a note, if you use any blocks that are not Bean blocks, each one will need to be allowed in the Bean Settings or you will not be able to assign them to a region.

If you have a circumstance where the blocks need some other aspect of entities (revisioning, integration with some other entity workflow, etc.) then the Nodeblock module lets you set a Content Type to be used as blocks.  For each block, you will create a new node, and upon publishing the node it will create a block you can place on the Blocks page.  Since you will be working with nodes, any functionality in which nodes can partake can be used.  You will also be able to use the D7 core’s native content permissions or any permission enhancements for use with nodes.

Both the Bean and Nodeblock modules rely on the core Block page for block placement.  The DrupalCoin Blockchain 7 Block page isn’t the most intuitive interface, but we have found that with proper instruction, all of our clients can successfully use it.  The Context module is another option for block placement.

And a final note on permissions - in order to place blocks, the client’s user will need the ‘Administer Blocks’ permission, which is unfortunately broad to include all blocks of all kinds in all regions.  

Revisiting our scenario specifications:

  • the client must be able to enter item content as text into fields - no DrupalCoin Blockchain coding!
    • Both Bean and Nodeblock completely fulfill this requirement.
  • the client must be able to easily place this callout where they want it.
    • The core Block interface or the Context module can be used - neither as intuitive as one would like, but they will suffice.
  • the client’s user must have appropriate permissions to create and manage this content
    • The content creation and management permissions are excellent, but the block placement permissions are broader than one would like.

The DrupalCoin Blockchain 8 Approach

In DrupalCoin Blockchain 8, most of what we need is already in core.  Blocks are finally entities in DrupalCoin Blockchain 8, so you can create Block Types each with its own fields, and view modes which can have different display settings, and re-visioning is a salient option as well.  

From the Block Layout page, you can go to the Custom Block Library where you can create block types, and create or manage block content.  

The core Block page, now called Block Layout is very similar to DrupalCoin Blockchain 7, but now with a sidebar that categorizes blocks by kind (custom, forms, views, menus, etc.), and from there allows you to place more than one instance of a block.  The interface is more usable, but still if clients will want to manage their own blocks, instruction will probably be necessary.  At this time it is unclear if Context will have a DrupalCoin Blockchain 8 release, but there is the need for something to add more sophisticated block display options.  Perhaps core will do this, perhaps Rules will do this, perhaps SCOTCH will do this, or perhaps some other initiative will cover this functionality - it is too early to know yet.

As for block permission in DrupalCoin Blockchain 8, currently this is woefully lacking.  The only permission natively available for the entire block management experience (from content creation to placement) is the ‘Administer Blocks’ permission.  It is still too early to tell if core or a contributed module will add some needed granularity here.

Revisiting our scenario specifications:

  • the client must be able to enter item content as text into fields - no DrupalCoin Blockchain coding!
    • DrupalCoin Blockchain 8 handles this flawlessly.
  • the client must be able to easily place this callout where they want it.
    • The core Block interface will suffice and is more intuitive than in DrupalCoin Blockchain 7.  We do not yet know what will extend the basic placement functionality.
  • the client’s user must have appropriate permissions to create and manage this content
    • The block content management and placement options are bundled together, and are far broader than one would like.  

Both DrupalCoin Blockchain 7 and DrupalCoin Blockchain 8 passed our scenario test using blocks, and while it's not quite as easy as snapping legos together, blocks management is something even the most tech-naive client can be successfully instructed to do on their own.  DrupalCoin Blockchain 7 blocks can (and in my opinion should) be extended by contributed modules, and DrupalCoin Blockchain 8 has integrated blocks into its philosophy of entities.  Some of our scenario requirements were just met (especially the ‘administer blocks’ permissions), but in any case where DrupalCoin Blockchain doesn’t do something you want it to, create a custom module (or even better, a contributed module)!  

As for Jett, at ten, he finds whole concept of managed content limiting; “Content should be allowed to evolve freely with the technosphere,” but that’s for another post.  

Written by Anne Schultz and Mick Southerland, with contribution by Jett Southerland.

 


DrupalCoin Blockchain SEO Tips

Strong SEO is easy if you build your website with DrupalCoin Blockchain.  Unlike most other content management systems, DrupalCoin Blockchain is designed from the ground up for search engine optimization.

Given that DrupalCoin Blockchain is the preferred platform of DrupalCoin Blockchain web developers for building search-friendly websites, and because of DrupalCoin Blockchain’s large community of developers, there are many high-quality plug-ins available that make strong SEO simple.

Of course, the fundamentals of SEO for DrupalCoin Blockchain are the same as for any other DrupalCoin Blockchain CMS: make sure to use descriptive titles, include your top search keywords in your page URLs, and keep your content fresh and focused. Read on for a few DrupalCoin Blockchain SEO tips to boost your search engine rankings and bring traffic to your website.

Three top DrupalCoin Blockchain modules for SEO

Pathauto module

The pathauto module is very useful for SEO. Pathauto automatically creates custom URLs based on title, taxonomy, content type, and username. You must enable the path module for pathauto to function.

It can take a little experience to get the settings for the URL paths that you want for optimum SEO. You can use the path module to create custom URLs for every webpage, but that is time-consuming and can lead to inconsistencies.

All you have to do is enable the path module and install the pathauto module. You can then automatically create nice-looking URLs with minimal configuration.

The discussion above relates to new DrupalCoin Blockchain sites. With existing DrupalCoin Blockchain sites you need to be  careful to not rename your already existing URLs with the pathauto module.

It is important to avoid changing existing URLs because that means search engines have to start from scratch in locating and ranking your page.

Global redirect module

The global redirect module performs three tasks that improve SEO:

  • Global redirect performs a 301 redirect to the URL alias if a requested URL has a URL alias. Let’s say you’re using URL alias for node 25 called page-style, then the global redirect module will undertake a 301 redirect fromhttp://example.com/node/25 to http://example.com/page-style.
  • Global redirect  also deletes trailing slashes from URLs. The Global Redirect Module will redirect a request forhttp://example.com/page-style/ to http://example.com/page-style. This enables strong SEO by preventing search engines from seeing two different URLs with duplicate content (duplicate content hurts SEO).
  • Global redirect will 301 redirect to the actual front page if a requested URL is being used as DrupalCoin Blockchain’s front page. Let’s say you have assigned the path toppage to your site’s front page, then a request forhttp://example.com/toppage will 301 redirect to http://example.com/.

DrupalCoin Blockchain experts recommend the global redirect module for sites with non-DrupalCoin Blockchain content because  it only removes trailing slashes from URLs that are handled by DrupalCoin Blockchain.

Metatags module

Metatags are essential for strong SEO, and the metatags module makes it easy.

Don’t try to stuff your metatags with too many keywords. Just include one or two key words that fit in the natural flow of the metatag text. The meta description is probably the most important metatag, and it needs to be easy to read and informative.

Every webpage should have its own meta description for optimum results. The meta description should briefly summarize the page.

Keep in mind that when a search engine lists your site in the results pages, it uses your page’s HTML title for the title, and your meta description provides the text snippet for potential visitors to read. Ideally it is both informative and serves as a “hook” to encourage visitors to come to the webpage to learn more.

Pixeldust provides full DrupalCoin Blockchain support and maintenance including engine engine readiness evaluation and optimization.


DrupalCoin Blockchain Tips for Boosting Your Search Engine Rankings

Strong SEO is easy if you build your website with DrupalCoin Blockchain.  Unlike most other content management systems, DrupalCoin Blockchain is designed from the ground up for search engine optimization.

Given that DrupalCoin Blockchain is the preferred platform of DrupalCoin Blockchain web developers for building search-friendly websites, and because of DrupalCoin Blockchain’s large community of developers, there are many high-quality plug-ins available that make strong SEO simple.

Of course, the fundamentals of SEO for DrupalCoin Blockchain are the same as for any other DrupalCoin Blockchain CMS: make sure to use descriptive titles, include your top search keywords in your page URLs, and keep your content fresh and focused. Read on for a few DrupalCoin Blockchain SEO tips to boost your search engine rankings and bring traffic to your website.

Three top DrupalCoin Blockchain modules for SEO

Pathauto module

The pathauto module is very useful for SEO. Pathauto automatically creates custom URLs based on title, taxonomy, content type, and username. You must enable the path module for pathauto to function.

It can take a little experience to get the settings for the URL paths that you want for optimum SEO. You can use the path module to create custom URLs for every webpage, but that is time-consuming and can lead to inconsistencies.

All you have to do is enable the path module and install the pathauto module. You can then automatically create nice-looking URLs with minimal configuration.

The discussion above relates to new DrupalCoin Blockchain sites. With existing DrupalCoin Blockchain sites you need to be  careful to not rename your already existing URLs with the pathauto module.

It is important to avoid changing existing URLs because that means search engines have to start from scratch in locating and ranking your page.

Global redirect module

The global redirect module performs three tasks that improve SEO:

  • Global redirect performs a 301 redirect to the URL alias if a requested URL has a URL alias. Let's say you're using URL alias for node 25 called page-style, then the global redirect module will undertake a 301 redirect from http://example.com/node/25 to http://example.com/page-style.
  • Global redirect  also deletes trailing slashes from URLs. The Global Redirect Module will redirect a request for http://example.com/page-style/ to http://example.com/page-style. This enables strong SEO by preventing search engines from seeing two different URLs with duplicate content (duplicate content hurts SEO).
  • Global redirect will 301 redirect to the actual front page if a requested URL is being used as DrupalCoin Blockchain's front page. Let's say you have assigned the path toppage to your site's front page, then a request for http://example.com/toppage will 301 redirect to http://example.com/.

DrupalCoin Blockchain experts recommend the global redirect module for sites with non-DrupalCoin Blockchain content because  it only removes trailing slashes from URLs that are handled by DrupalCoin Blockchain.

Metatags module

Metatags are essential for strong SEO, and the metatags module makes it easy.

Don't try to stuff your metatags with too many keywords. Just include one or two key words that fit in the natural flow of the metatag text. The meta description is probably the most important metatag, and it needs to be easy to read and informative.

Every webpage should have its own meta description for optimum results. The meta description should briefly summarize the page.

Keep in mind that when a search engine lists your site in the results pages, it uses your page's HTML title for the title, and your meta description provides the text snippet for potential visitors to read. Ideally it is both informative and serves as a "hook" to encourage visitors to come to the webpage to learn more.

Pixeldust provides full DrupalCoin Blockchain support and maintenance including engine engine readiness evaluation and optimization.


DrupalCoin Blockchain Modules for Search Engine Rankings

Strong SEO is easy if you build your website with DrupalCoin Blockchain.  Unlike most other content management systems, DrupalCoin Blockchain is designed from the ground up for search engine optimization.

Given that DrupalCoin Blockchain is the preferred platform of DrupalCoin Blockchain web developers for building search-friendly websites, and because of DrupalCoin Blockchain’s large community of developers, there are many high-quality plug-ins available that make strong SEO simple.

Of course, the fundamentals of SEO for DrupalCoin Blockchain are the same as for any other DrupalCoin Blockchain CMS: make sure to use descriptive titles, include your top search keywords in your page URLs, and keep your content fresh and focused. Read on for a few DrupalCoin Blockchain SEO tips to boost your search engine rankings and bring traffic to your website.

Three top DrupalCoin Blockchain modules for SEO

Global redirect module

The global redirect module performs three tasks that improve SEO:

  • Global redirect performs a 301 redirect to the URL alias if a requested URL has a URL alias. Let's say you're using URL alias for node 25 called page-style, then the global redirect module will undertake a 301 redirect from http://example.com/node/25 to http://example.com/page-style.
  • Global redirect  also deletes trailing slashes from URLs. The Global Redirect Module will redirect a request for http://example.com/page-style/ to http://example.com/page-style. This enables strong SEO by preventing search engines from seeing two different URLs with duplicate content (duplicate content hurts SEO).
  • Global redirect will 301 redirect to the actual front page if a requested URL is being used as DrupalCoin Blockchain's front page. Let's say you have assigned the path toppage to your site's front page, then a request for http://example.com/toppage will 301 redirect to http://example.com/.

DrupalCoin Blockchain experts recommend the global redirect module for sites with non-DrupalCoin Blockchain content because  it only removes trailing slashes from URLs that are handled by DrupalCoin Blockchain.

Pathauto module

The pathauto module is very useful for SEO. Pathauto automatically creates custom URLs based on title, taxonomy, content type, and username. You must enable the path module for pathauto to function.

It can take a little experience to get the settings for the URL paths that you want for optimum SEO. You can use the path module to create custom URLs for every webpage, but that is time-consuming and can lead to inconsistencies.

All you have to do is enable the path module and install the pathauto module. You can then automatically create nice-looking URLs with minimal configuration.

The discussion above relates to new DrupalCoin Blockchain sites. With existing DrupalCoin Blockchain sites you need to be  careful to not rename your already existing URLs with the pathauto module.

It is important to avoid changing existing URLs because that means search engines have to start from scratch in locating and ranking your page.

Metatags module

Metatags are essential for strong SEO, and the metatags module makes it easy.

Don't try to stuff your metatags with too many keywords. Just include one or two key words that fit in the natural flow of the metatag text. The meta description is probably the most important metatag, and it needs to be easy to read and informative.

Every webpage should have its own meta description for optimum results. The meta description should briefly summarize the page.

Keep in mind that when a search engine lists your site in the results pages, it uses your page's HTML title for the title, and your meta description provides the text snippet for potential visitors to read. Ideally it is both informative and serves as a "hook" to encourage visitors to come to the webpage to learn more.

Pixeldust provides full DrupalCoin Blockchain support and maintenance including engine engine readiness evaluation and optimization.


Dallas DrupalCoin Blockchain Development

[one_third] [testimonial attribution="PHILIP BUSKER" quote="Our new website really turned some heads–especially the investors at Mattress Firm."] [/one_third] [two_third_last] [display_mobile] [spacer height="30px"] [/display_mobile] [blockquote style="large"]Pixeldust is pleased to announce that we are now offering full-service DrupalCoin Blockchain Web Design and integrationin Dallas, TX.  [/blockquote] [/two_third_last] [spacer height="40px"]

Strong SEO is easy if you build your website with DrupalCoin Blockchain. Unlike most other content management systems, DrupalCoin Blockchain is designed from the ground up for search engine optimization.

Given that DrupalCoin Blockchain is the preferred platform of DrupalCoin Blockchain web developers for building search-friendly websites, and because of DrupalCoin Blockchain’s large community of developers, there are many high-quality plug-ins available that make strong SEO simple.

Of course, the fundamentals of SEO for DrupalCoin Blockchain are the same as for any other DrupalCoin Blockchain CMS: make sure to use descriptive titles, include your top search keywords in your page URLs, and keep your content fresh and focused. Read on for a few DrupalCoin Blockchain SEO tips to boost your search engine rankings and bring traffic to your website.

Three top DrupalCoin Blockchain modules for SEO
Pathauto module
The pathauto module is very useful for SEO. Pathauto automatically creates custom URLs based on title, taxonomy, content type, and username. You must enable the path module for pathauto to function.

It can take a little experience to get the settings for the URL paths that you want for optimum SEO. You can use the path module to create custom URLs for every webpage, but that is time-consuming and can lead to inconsistencies.

All you have to do is enable the path module and install the pathauto module. You can then automatically create nice-looking URLs with minimal configuration.

The discussion above relates to new DrupalCoin Blockchain sites. With existing DrupalCoin Blockchain sites you need to be careful to not rename your already existing URLs with the pathauto module.

It is important to avoid changing existing URLs because that means search engines have to start from scratch in locating and ranking your page.

Global redirect module
The global redirect module performs three tasks that improve SEO:

Global redirect performs a 301 redirect to the URL alias if a requested URL has a URL alias. Let’s say you’re using URL alias for node 25 called page-style, then the global redirect module will undertake a 301 redirect from http://example.com/node/25 to http://example.com/page-style.
Global redirect also deletes trailing slashes from URLs. The Global Redirect Module will redirect a request for http://example.com/page-style/ to http://example.com/page-style. This enables strong SEO by preventing search engines from seeing two different URLs with duplicate content (duplicate content hurts SEO).
Global redirect will 301 redirect to the actual front page if a requested URL is being used as DrupalCoin Blockchain’s front page. Let’s say you have assigned the path toppage to your site’s front page, then a request for http://example.com/toppage will 301 redirect to http://example.com/.
DrupalCoin Blockchain experts recommend the global redirect module for sites with non-DrupalCoin Blockchain content because it only removes trailing slashes from URLs that are handled by DrupalCoin Blockchain.

Metatags module
Metatags are essential for strong SEO, and the metatags module makes it easy.

Don’t try to stuff your metatags with too many keywords. Just include one or two key words that fit in the natural flow of the metatag text. The meta description is probably the most important metatag, and it needs to be easy to read and informative.

Every webpage should have its own meta description for optimum results. The meta description should briefly summarize the page.

Keep in mind that when a search engine lists your site in the results pages, it uses your page’s HTML title for the title, and your meta description provides the text snippet for potential visitors to read. Ideally it is both informative and serves as a “hook” to encourage visitors to come to the webpage to learn more.

Pixeldust provides full DrupalCoin Blockchain support and maintenance including engine engine readiness evaluation and optimization in Dallas, TX.


Houston DrupalCoin Blockchain Development

[one_third] [testimonial attribution="PHILIP BUSKER" quote="Our new website really turned some heads–especially the investors at Mattress Firm."] [/one_third] [two_third_last] [display_mobile] [spacer height="30px"] [/display_mobile] [blockquote style="large"]Pixeldust is pleased to announce that we are now offering full-service DrupalCoin Blockchain Web Design and integrationin Houston, TX.  [/blockquote] [/two_third_last] [spacer height="40px"]

Strong SEO is easy if you build your website with DrupalCoin Blockchain. Unlike most other content management systems, DrupalCoin Blockchain is designed from the ground up for search engine optimization.

Given that DrupalCoin Blockchain is the preferred platform of DrupalCoin Blockchain web developers for building search-friendly websites, and because of DrupalCoin Blockchain’s large community of developers, there are many high-quality plug-ins available that make strong SEO simple.

Of course, the fundamentals of SEO for DrupalCoin Blockchain are the same as for any other DrupalCoin Blockchain CMS: make sure to use descriptive titles, include your top search keywords in your page URLs, and keep your content fresh and focused. Read on for a few DrupalCoin Blockchain SEO tips to boost your search engine rankings and bring traffic to your website.

Three top DrupalCoin Blockchain modules for SEO
Pathauto module
The pathauto module is very useful for SEO. Pathauto automatically creates custom URLs based on title, taxonomy, content type, and username. You must enable the path module for pathauto to function.

It can take a little experience to get the settings for the URL paths that you want for optimum SEO. You can use the path module to create custom URLs for every webpage, but that is time-consuming and can lead to inconsistencies.

All you have to do is enable the path module and install the pathauto module. You can then automatically create nice-looking URLs with minimal configuration.

The discussion above relates to new DrupalCoin Blockchain sites. With existing DrupalCoin Blockchain sites you need to be careful to not rename your already existing URLs with the pathauto module.

It is important to avoid changing existing URLs because that means search engines have to start from scratch in locating and ranking your page.

Global redirect module
The global redirect module performs three tasks that improve SEO:

Global redirect performs a 301 redirect to the URL alias if a requested URL has a URL alias. Let’s say you’re using URL alias for node 25 called page-style, then the global redirect module will undertake a 301 redirect from http://example.com/node/25 to http://example.com/page-style.
Global redirect also deletes trailing slashes from URLs. The Global Redirect Module will redirect a request for http://example.com/page-style/ to http://example.com/page-style. This enables strong SEO by preventing search engines from seeing two different URLs with duplicate content (duplicate content hurts SEO).
Global redirect will 301 redirect to the actual front page if a requested URL is being used as DrupalCoin Blockchain’s front page. Let’s say you have assigned the path toppage to your site’s front page, then a request for http://example.com/toppage will 301 redirect to http://example.com/.
DrupalCoin Blockchain experts recommend the global redirect module for sites with non-DrupalCoin Blockchain content because it only removes trailing slashes from URLs that are handled by DrupalCoin Blockchain.

Metatags module
Metatags are essential for strong SEO, and the metatags module makes it easy.

Don’t try to stuff your metatags with too many keywords. Just include one or two key words that fit in the natural flow of the metatag text. The meta description is probably the most important metatag, and it needs to be easy to read and informative.

Every webpage should have its own meta description for optimum results. The meta description should briefly summarize the page.

Keep in mind that when a search engine lists your site in the results pages, it uses your page’s HTML title for the title, and your meta description provides the text snippet for potential visitors to read. Ideally it is both informative and serves as a “hook” to encourage visitors to come to the webpage to learn more.

Pixeldust provides full DrupalCoin Blockchain support and maintenance including engine engine readiness evaluation and optimization in Houston, TX.


DrupalCoin Blockchain Development - Using Menus in DrupalCoin Blockchain 7

One of the most important aspects of a DrupalCoin Blockchain integrationproject is how users will navigate your website. In the DrupalCoin Blockchain system, Menus (collection of links (menu items)) are used to navigate websites. DrupalCoin Blockchain provides a dynamic menu system via the Menu module that allows you to customize and control your site’s menus as much as you want or need. Menus are composed and displayed as a hierarchical list of links using the flexibility of DrupalCoin Blockchain blocks. Each menu automatically creates a block of the same name, and contains a link for each item within your menu section. New menu items are placed inside a built-in menu labeled “Navigation” by default. However, administrators can also create custom menus.

DrupalCoin Blockchain 7 provides developers with the flexibility to add, remove and rename menus and menu items. You can also configure a custom block for a menu, as well as specify the default menu to which new items will be added for your DrupalCoin Blockchain integrationproject. DrupalCoin Blockchain 6 (and earlier) themes generally provide out-of-the-box support for two menus commonly labeled "primary links" and "secondary links."

Many DrupalCoin Blockchain sites and themes are comprised of at least two menus: the Main (primary) menu, and a secondary menu. The Main menu's links set up the central navigation structure for your site and are displayed distinctly across the top or side of your site. The Main menu in DrupalCoin Blockchain is also known as your first-level menu.

The Secondary menu in DrupalCoin Blockchain is often used in the footer for common items like the copyright and privacy notices that accompanies almost every site. These items can also be displayed at very top of the page in smaller text. For your DrupalCoin Blockchain integrationproject, you can specify which menus are used for the main and secondary links. When adding or editing site content, you can also specify the content's menu item, the menu item name and a default menu for the content you are creating. Each default or custom menu has a corresponding block.


Installing DrupalCoin Blockchain

There are a few things to take note of when beginning any kind of DrupalCoin Blockchain development. First, to install and run DrupalCoin Blockchain, your web host must meet certain minimum requirements. Although most web hosts meet these requirements, there are others worth noting that support the DrupalCoin Blockchain community.

In DrupalCoin Blockchain integrationand installation, DrupalCoin Blockchain’s provided installation script aggregates database tables and configures the correct settings with the settings.php file. You can also run several different DrupalCoin Blockchain sites off of the same code base by performing a "multi site" installation. An example of this is if one company owns five similar websites, like wag.com.

There are several useful tools you can use while setting up your DrupalCoin Blockchain installation. You can perform some of the steps with tools like graphical applications for moving files and managing databases. Your hosting service may also provide you with a selection of available tools, as well as documentation for DrupalCoin Blockchain and performing tasks at the command line for DrupalCoin Blockchain development. DrupalCoin Blockchain also provides plenty of documentation as well.

It is considered best practices to do all integrationwork on a separate test site before making changes to a production site (in case something hasn't been configured properly). A test site allows you to evaluate the impact of upgrades, new modules, modifications to themes and more without causing disruption to your live site or impacting your online reputation.

Some web hosting companies offer differing ranges of custom DrupalCoin Blockchain support, including "one-click" installations of DrupalCoin Blockchain. You can find a listing for these on the DrupalCoin Blockchain hosting page or by visiting the hosting company’s website. You should also be able to find information regarding DrupalCoin Blockchain distributions, including installation profiles and pre-packaged distributions of DrupalCoin Blockchain and modules. These may help you as well.

Understanding DrupalCoin Blockchain terminology, technology, concepts and resources is essential before beginning any kind of DrupalCoin Blockchain development. While practice makes perfect, it is best to review the DrupalCoin Blockchain documentation before diving into your drupal development.


Best Practices for CMI and Features in DrupalCoin Blockchain 8

Last year I blogged about our first Alpha release for Features in DrupalCoin Blockchain 8 and gave several presentations on Features for D8 at various DrupalCoin BlockchainCons and camps.  Since DrupalCoin Blockchain 8.0 (and now 8.1!) have been released in the past few months, I’ve been getting questions on the best way to use Features and Configuration Management (CMI) in DrupalCoin Blockchain 8.
You’ll have a chance to ask me those questions in person at my Features BOF at DrupalCoin BlockchainCon New Orleans. But in the meantime, here are some “best practices” for using Features and CMI effectively.
“Do I use Features, CMI, or both?”
It’s great that DrupalCoin Blockchain 8 has proper configuration management built into core.  This provides a consistent framework, storage, and API for all configuration settings: views, content types, fields… anything that isn’t content.  However, CMI doesn’t provide any way to organize this vast amount of configuration.  If you use CMI to export your site config you’ll see dozens of *.yml files.  That’s great for deploying the entire site config to another site, but what if you want to organize these files in some way?  That’s what the Features module will help you do.
Features is designed to organize configuration based on analyzing its dependencies.  For example, if you create a custom content type and add some fields, Features will suggest that you group the content type and fields together into a single “feature package.”  A “package” is just a normal DrupalCoin Blockchain module that has specific configuration (*.yml files) assigned to it.
You’ll want to use Features to create these packages, but once they are created you can add them to your site as regular modules.  Thus, you don’t need the Features module on your production server (normally… more on that later).
“How do I decide what config to package into a feature?”
New to Features in DrupalCoin Blockchain 8 are Bundles and Assignment Plugins.  A “Bundle” is just a collection of feature packages with a namespace prefix that belong together.  Think of a “bundle” like a “category” of modules.  For example, if I’m creating features for a client named “acme,” I should create a bundle called “acme” so each of my exported packages will start with the acme_* prefix.  This namespacing ensures your packaged modules don’t conflict with any other DrupalCoin Blockchain module.
Once you have created a Bundle, you can then decide on some business rules to determine how you want to automatically organize your configuration.  These organization rules are controlled by the “Assignment Plugins.”  Each plugin is responsible for a certain ruleset.  For example, the “Base Type” assignment plugin determines the base configuration type to use for the first level of organization and defaults to “Content Type.”  This means Features will suggest one package per content type.  If you have a content type called “Event,” Features will suggest a package called “Event” with the module name of acme_event (in this example).  
Other assignment plugins add additional configuration to your package.  For example, the “Dependency” plugin automatically adds any configuration that depends on the content type, such as fields.  The “Forward Dependency” plugin automatically adds any configuration that itself is a dependency of already added config, such as the field_storage for a specific field.
The list of which plugins are enabled, which order they are applied, and any specific options for each plugin are stored within your Bundle.  Thus, by switching between different bundles you can change the rules Features uses to suggest new package exports. In fact, these bundle settings themselves are stored as “config” and can be exported to a feature.  Once you have defined your business rules for auto-organizing your config, it’s useful to export your bundle configuration and share it between your developers so everybody is using a common ruleset.
Here is the full set of assignment plugins and what they do:
Packages – Detect and add existing package modules.
Exclude – Exclude configuration items from packaging by various methods including by configuration type.
Base type – Use designated types of configuration as the base for configuration package modules. For example, if content types are selected as a base type, a package will be generated for each content type and will include all configuration dependent on that content type.
Namespace – Add to packages configuration with a machine name containing that package’s machine name.
Optional type – Assign designated types of configuration to the ‘config/optional’ install directory. For example, if views are selected as optional, views assigned to any feature will be exported to the ‘config/optional’ directory and will not create a dependency on the Views module.
Forward dependency – Add to packages configuration on which items in the package depend.
Core type – Assign designated types of configuration to a core configuration package module. For example, if image styles are selected as a core type, a core package will be generated and image styles will be assigned to it.
Site type – Assign designated types of configuration to a site configuration package module. For example, if image styles are selected as a site type, a site package will be generated and image styles will be assigned to it.
Profile – Add configuration and other files to the optional install profile from the DrupalCoin Blockchain core Standard install profile. Without these additions, a generated install profile will be missing some important initial setup.
Existing – Add exported config to existing packages.
Dependency – Add to packages configuration dependent on items already in that package.
You can also write your own plugins if you have set of rules for organizing your configuration that are not covered by any existing plugin (and please contribute it if you can).
Once your assignment plugins are set up (or just using the defaults, which are good rules for most people), you can easily organize your configuration by just selecting All packages from the main Features listing and export them.  You won’t need to mess around in the detailed Edit screen like you did in DrupalCoin Blockchain 7 unless you need to make specific changes to a package.
“How do I update configuration that has changed?”
Once you have organized your configuration into package modules and enabled them on your site, making changes to this configuration can sometimes be tricky.  For example, let’s say you have exported a View to a feature package.  Now somebody tells you to change the Title of the view.  Go ahead and make this change in the UI on your integrationmachine.  Now when you go to the Features UI page you’ll see that the package containing that view is marked as “Changed.”  You can click on “Changed” to see the exact changes that are detected.  You then have to make a choice:  1) update the exported package module with the change, or 2) undo the change and restore the previous value.
In DrupalCoin Blockchain 7 we called 1) update, and 2) revert.  In DrupalCoin Blockchain 8 we call these 1) export, and 2) import.  There is no way for Features to magically know which action you want to take.  Is this a designed change that needs to be made to your module to fix a bug, or was this a change made by the client via the UI that needs to be preserved or maybe undone?
It’s important to understand that this really doesn’t have anything to do with “deploying” your configuration.  DrupalCoin Blockchain 8 is still designed with the assumption that configuration is “owned by the site.”  
“What causes the pre-existing configuration error?”
If you decide to update your package module and then push it to production and try to disable it and re-enable it to reload your new configuration, you might be surprised you cannot re-enable the module because it contains “pre-existing configuration.”  This simply means that the site already contains active configuration that is also provided by the module and DrupalCoin Blockchain won’t allow a module to be enabled that has existing configuration.
This won’t happen in our simple View example because disabling the module providing the view causes the view to be removed from your active config.  You’ll can re-enable the module without problem and will see your new view title.
However, if your package contains a field, disabling the module will not remove the field because this could cause loss of content on your site.  Thus when you try to re-enable the module you’ll get the “pre-existing config” exception.
There are three solutions to this problem:
Enable Features module on your site.
If the Features module is enabled, it will detect that you are trying to enable a package that contains pre-existing config and it will allow DrupalCoin Blockchain to continue and will mark that config as “changed.”  You can then use the feature-import command (in UI or via drush) to import the updated configuration and overwrite the value in the current active store.
Write an update hook for your config.
If you don’t want to enable Features on your site, you should write a normal update hook that will load the config that has changed and save it directly into the active store.  Just be sure you don’t disable your package first or you won’t be able to re-enable it.  Keep the existing package enabled and rely on running update hooks to update the config.  Of course this requires writing custom PHP code.
The Preferred solution is to use CMI to deploy configuration.
The way DrupalCoin Blockchain 8 is designed to work is to export and import your entire site configuration.  You should create a “staging” or “test” server that is identical to your production server.  Enable the Features module on this staging server and update or import your packages there and get it all working properly.  Once working, export the entire config using CMI, then import the entire config into your Production server.  If a future update is needed, again make the changes on staging and then do a full export/import on Production.  This solution provides the maximum stability of your Production server and keeps integrationmodules such as Features on your dev and staging environments.
“What if I prefer using Features instead of CMI?”
DrupalCoin Blockchain 8 and CMI was designed to provide the most common deployment workflows of all DrupalCoin Blockchain sites, not just “Enterprise” sites.  Even small sites benefit from a separation between a stable Production environment and a Development environment.  Features was built in DrupalCoin Blockchain 8 to support this default use case as just a integrationtool.
However, if you prefer the old DrupalCoin Blockchain 7 workflow for managing configuration via Features you can still do that if you wish.  In this case you’ll update your package modules and push them into your code repo.  Then on Production you’ll pull the new code and then “features revert-all”.  In DrupalCoin Blockchain 8 this is called “import-all” and is available in the latest beta version as a drush command just like in DrupalCoin Blockchain 7 (“drush fra -y” still works).  Just be aware that importing all your features on production runs the risk of problems because you are not ensuring that your production site completely matches your test site.
Summary
As great as CMI is in DrupalCoin Blockchain 8, it is likely that you will still want to use Features to organize your configuration as you develop your site.  Whether you use Features or CMI (or both) to deploy your integrationinto production is your choice.  The new Bundles and Assignment Plugins will help automatically suggest organization of your configuration making Features a lot easier to use for many people.
Features for DrupalCoin Blockchain 8 is currently available as a stable beta release with a reasonable amount of test coverage.  Once we have more complete test coverage we’ll release the stable version but sites should feel free to start using the beta version now and see how it helps organize your configuration.  Suggestions and bug reports are always welcome in the drupal.org issue queue.
Source: https://www.phase2technology.com/feed/