Decentral Digital Blog

News, facts, techniques, opinion and more.

WordPress 4.8 Beta 2

WordPress 4.8 Beta 2 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

For more information on what’s new in 4.8, check out the Beta 1 blog post. Since then, we’ve made over 50 changes in Beta 2.

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

Continue reading
402 Hits
0 Comments

WordPress 4.7.5 Security and Maintenance Release

WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

WordPress versions 4.7.4 and earlier are affected by six security issues:

Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing.Improper handling of post meta data values in the XML-RPC API. Reported by Sam Thomas.Lack of capability checks for post meta data in the XML-RPC API. Reported by Ben Bidner of the WordPress Security Team.A Cross Site Request Forgery (CRSF)  vulnerability was discovered in the filesystem credentials dialog. Reported by Yorick Koster.A cross-site scripting (XSS) vulnerability was discovered when attempting to upload very large files. Reported by Ronni Skansing.A cross-site scripting (XSS) vulnerability was discovered related to the Customizer. Reported by Weston Ruter of the WordPress Security Team.

Thank you to the reporters of these issues for practicing responsible disclosure.

In addition to the security issues above, WordPress 4.7.5 contains 3 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

Download WordPress 4.7.5 or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.7.5.

Continue reading
564 Hits
0 Comments

WordPress Now on HackerOne

WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially on HackerOne!

HackerOne is a platform for security researchers to securely and responsibly report vulnerabilities to our team. It provides tools that improve the quality and consistency of communication with reporters, and will reduce the time spent on responding to commonly reported issues. This frees our team to spend more time working on improving the security of WordPress.

The security team has been working on this project for quite some time. Nikolay Bachiyski started the team working on it just over a year ago. We ran it as a private program while we worked out our procedures and processes, and are excited to finally make it public.

With the announcement of the WordPress HackerOne program we are also introducing bug bounties. Bug bounties let us reward reporters for disclosing issues to us and helping us secure our products and infrastructure. We’ve already awarded more than $3,700 in bounties to seven different reporters! We are thankful to Automattic for paying the bounties on behalf of the WordPress project.

The program and bounties cover all our projects including WordPress, BuddyPress, bbPress, GlotPress, and WP-CLI as well as all of our sites including WordPress.org, bbPress.org, WordCamp.org, BuddyPress.org, and GlotPress.org.

Original linkOriginal author: Aaron D. Campbell
435 Hits
0 Comments

WordPress 4.8 Beta 1

We’re planning a smaller WP release early next month, bringing in three major enhancements:

An improved visual editor experience, with a new TinyMCE that allows you to navigate more intuitively in and out of inline elements like links. (Try it out to see, it’s hard to describe.)A revamp of the dashboard news widget to bring in nearby and upcoming events including meetups and WordCamps.Several new media widgets covering images, audio, and video, and an enhancement to the text widget to support visual editing.

The first beta of 4.8 is now available for testing. You can use the beta tester plugin (or just run trunk) to try the latest and greatest, and each of these areas could use a ton of testing. Our goals are to make editing posts with links more intuitive, make widgets easier for new users and more convenient for existing ones, and get many more people aware of and attending our community events.

Four point eight is hereSmall changes with a big punchBig ones come later

Original linkOriginal author: Matt Mullenweg
473 Hits
0 Comments

The Process for Evolving Community Governance

Discover > Plan > Build > Iterate

There comes a time when we must all recognize that what got us here won't get us there. Now is that time for Drupal. The governance models that were put in place to support the needs of the community years ago are no longer working as well as they should. The Drupal community has reached a level of maturity that requires greater clarity, integrity, and resilience.

An effort is underway to evolve Drupal’s community governance. The Drupal community is in the driver’s seat. The Drupal Association is helping navigate and get the community where it wants to go by providing the structure, support, and resources that are desperately needed to make progress. I, Whitney Hess, have been engaged to be a neutral facilitator of this process.

We are proposing a multi-phase approach to redesign Drupal’s community governance models, management, and decision-making practices: Discover > Plan > Build > Iterate. In this first phase, our goal is to gain a deeper understanding of the needs of the Drupal community. We are conducting this research through a variety of methods: one-on-one interviews with select individuals; mediated group discussions; surveys and feedback forms.

We held seven hour-long Community Discussions over three days of DrupalCon. There were 6-10 participants per session. Though every session had its own energy and topics varied, all discussions were fruitful and impactful. Many participants said they left feeling better than when they arrived.

While there was some discussion about recent events in the sessions, the focus quickly shifted to brainstorming ideas for how to improve Drupal’s community governance. As mediator, it is my role to help people articulate their needs, and to support the community in devising strategies to better get those needs met. Please read the meeting summaries if you would like to get a sense of what was discussed.

Continue reading
437 Hits
0 Comments

Call for a Team Leader & Assistant Team Leader - Joomla! User Experience Team

Call for a Team Leader & Assistant Team Leader - Joomla! User Experience Team Details Published: 04 May 2017

The Joomla! User Experience Team is looking for Joomla! Users with leadership and UX skills to lead and co-lead the team.

The purpose of the JUX is to improve the usability of The Joomla! Project through extensive research and user testing, and to make recommendations to the relevant teams based on findings. The UX team works closely with Joomla! Developers to shape the evolution (design and development) of the Joomla! CMS and the Joomla.org properties.

The goal of the team is to create an intuitive experience for our users. The UX Team is committed to improving the usability of the Joomla! Platform (admin interface, the default templates and the Joomla.org websites).

Team Leader MissionLead the UX team and manage the team membersCoordinate and delegate the responsibilities of the JUXOversee the day-to-day functions of the JUXFocus on motivating the JUX and maintain a comfortable and productive team environmentThis role is primarily administrative in nature. Due to the large number of projects and volunteers that JUX is overseeing, a time commitment of 10 hours per week is possible.Assistant Team Leader MissionAssist the leader in their missionReplace the leader in their mission during their absenceServe as a liaison with other teams to facilitate communication between sub-projects, the JUX team and the team leader.Ideal profile and qualifications for both rolesAre able to lead and delegate work to the teamsCan commit time to the project consistently (10 -15 hours per week for the team leader and 5-10 hours per week for the assistant leader) and have a flexible scheduleMust understand basic UX and processes; however, the work will not be UX in nature; instead it will be more administrativePossess excellent organisation, communication, leadership and collaborative skillsAre comfortable delegating to othersHave high standards of quality with strong attention to detailHave a flexible, friendly approach and a team oriented attitudeAre creative, conceptual and forward thinkingAre proactive, self-starting and motivatedAre empathetic, supportive and compassionateAre a Joomla! User and have knowledge in UXAre willing to travel for sprints and other Joomla! dev meetups.

If you would like to apply to these important roles, please fill out the JUX Team Application before May 30th, 2017.

Original linkOriginal author: Joomla!
625 Hits
0 Comments

Joomla! 3.7.0 Release Candidate 4

Because we are trying to make the difference between the last RC and the stable release as small as possible, we released today Joomla! 3.7.0 Release Candidate 4.

We invite our users to download and test the package in order to provide quality assurance for the forthcoming 3.7 release.This release candidate is intended to be the last development version before the release of Joomla! 3.7.0 stable planned on April 25th, 2017.

What is this release for?

This is a RELEASE CANDIDATE release, that should only be used on test sites and can't be upgraded.

Extension and template developers, it’s your last chance to prepare your extensions for the stable release of Joomla! 3.7.0, though there shouldn't be any backward compatibility issues. Users are encouraged to test the package for issues and to report them in the Joomla! CMS Issue Tracker.

When is the stable release due?

Joomla! 3.7 is planned to be released on April 25th 2017. Visit the Joomla! Developer site for the full roadmap.Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond our control.

Continue reading
613 Hits
0 Comments

Supporting the next evolution of Drupal's Community Governance

TL;DR: Both the community and Dries Buytaert, Project Lead, see a need to evolve Drupal community governance. The Drupal Association can help in a support role. We will start by hosting mediated community discussions so everyone around the world can participate, be heard and understood, and share their ideas. Creating a new governance model will take many months and will require an agile approach as we all feel our way through the proper steps. The Drupal Association will continue to find ways to support this process as we all move through it together.

-------------

Over the last several weeks, the Drupal Association has been in listening mode — and we still are. We’re hearing community members say they need clarity and understanding, and that our community governance needs to change. As we process what we’re hearing, we want to find the best way to help the community address the issues being raised, within the boundaries of the Drupal Association charter.

The Drupal Association’s mission is to unite the global community to help build and promote the software. We do that in two very specific ways: DrupalCon and Drupal.org. We’re determining how best to meet the community’s needs as it relates to these two key community homes. In the near future, I will publish blogs with ideas on how we might address the various needs we are hearing.

Evolving Community Governance

There is one need that we hear loud and clear that we can address today: The community needs support to evolve community governance structures and processes. Both the community at large, and Dries Buytaert, Project Lead, have expressed this need, and we are glad to see this alignment.  

Continue reading
498 Hits
0 Comments

WordPress 4.7.4 Maintenance Release

After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release.

This release contains 47 maintenance fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API. For a full list of changes, consult the release notes and the list of changes.

Download WordPress 4.7.4 or visit Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.7.4.

Thanks to everyone who contributed to 4.7.4:Aaron Jorbin, Adam Silverstein, Andrea Fercia, Andrew Ozz, aussieguy123, Blobfolio, boldwater, Boone Gorges, Boro Sitnikovski, chesio, Curdin Krummenacher, Daniel Bachhuber, Darren Ethier (nerrad), David A. Kennedy, davidbenton, David Herrera, Dion Hulse, Dominik Schilling (ocean90), eclev91, Ella Van Dorpe, Gustave F. Gerhardt, ig_communitysites, James Nylen, Joe Dolson, John Blackbourn, karinedo, lukasbesch, maguiar, MatheusGimenez, Matthew Boynes, Matt Wiebe, Mayur Keshwani, Mel Choyce, Nick Halsey, Pascal Birchler, Peter Wilson, Piotr Delawski, Pratik Shrestha, programmin, Rachel Baker, sagarkbhatt, Sagar Prajapati, sboisvert, Scott Taylor, Sergey Biryukov, Stephen Edgar, Sybre Waaijer, Timmy Crawford, vortfu, and Weston Ruter.

Original linkOriginal author: Pascal Birchler
536 Hits
0 Comments

Drupal Core - Critical - Access Bypass - SA-CORE-2017-002

Advisory ID: DRUPAL-SA-CORE-2017-002Project: Drupal core Version: 8.xDate: 2017-April-19 CVEID: CVE-2017-6919Security risk: 17/25 ( Critical) AC:Basic/A:User/CI:All/II:All/E:Theoretical/TD:DefaultVulnerability: Access bypassDescription

This is a critical access bypass vulnerability. A site is only affected by this if all of the following conditions are met:

The site has the RESTful Web Services (rest) module enabled.The site allows PATCH requests.An attacker can get or register a user account on the site.

While we don't normally provide security releases for unsupported minor releases, given the potential severity of this issue, we have also provided an 8.2.x release to ensure that sites that have not had a chance to update to 8.3.0 can update safely.

CVE identifier(s) issuedCVE-2017-6919Versions affectedDrupal 8 prior to 8.2.8 and 8.3.1.Drupal 7.x is not affected.SolutionIf the site is running Drupal 8.2.7 or earlier, upgrade to 8.2.8.If the site is running Drupal 8.3.0, upgrade to 8.3.1.

Also see the Drupal core project page.

Reported bySamuel MortensonFixed byAlex Pott of the Drupal Security Teamxjm of the Drupal Security TeamLee Rowlands of the Drupal Security TeamWim LeersSascha GrossenbacherDaniel WehnerTobias StöcklerNathaniel Catchpole of the Drupal Security TeamCoordinated by The Drupal Security team Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Continue reading
575 Hits
0 Comments

What's new on Drupal.org? - March 2017

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.

The Drupal Association team is gearing up for DrupalCon Baltimore. We're excited to see you there and we'll presenting a panel giving an update on our work since Dublin, and our plans for the coming months.

Drupal.org updatesProject application revamp

As we announced in mid-March, new contributors on Drupal.org can now create full projects and releases! Contributors no longer have to wait in the project application queue for a manual review before they are able to contribute projects.

This is a very significant change in the Drupal contribution landscape, and it's something we approached carefully and will continue to monitor over the coming months. Drupal has always had a reputation for a high quality code, and we want to make sure that reputation is preserved with good security signals, project quality signals, and continued incentives for peer code review.

That said, we're very excited to see how this change opens up Drupal to a wider audience of contributors.

Continue reading
413 Hits
0 Comments

Joomla! 3.7.0 Release Candidate 3

The Joomla! Project is pleased to announce the availability of Joomla! 3.7.0 Release Candidate 3. We invite our users to download and test the package in order to provide quality assurance for the forthcoming 3.7 release.This release candidate is intended to be the last development version before the release of Joomla! 3.7.0 stable planned on April 25th, 2017.

What is this release for?

This is a RELEASE CANDIDATE release, that should only be used on test sites and can't be upgraded.

Extension and template developers, it’s your last chance to prepare your extensions for the stable release of Joomla! 3.7.0, though there shouldn't be any backward compatibility issues. Users are encouraged to test the package for issues and to report them in the Joomla! CMS Issue Tracker.

When is the stable release due?

Joomla! 3.7 is planned to be released on April 25th 2017. Visit the Joomla! Developer site for the full roadmap.Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond our control.

Which bugs have been fixed in Joomla! 3.7?

A full list of issues resolved can be found on GitHub.

Continue reading
503 Hits
0 Comments

Drupal 8 core upcoming critical release PSA-2017-001

Advisory ID: DRUPAL-PSA-2017-001Project: Drupal core Version: 8.xDate: 2017-Apr-17Description

There will be a security release of Drupal 8.3.x and 8.2.x on April 19th 2017 between17:00 - 18:00 UTC that will fix a critical vulnerability. While we don't normally provide security releases for unsupported minor releases, given the potential severity, we will provide an 8.2.x release that includes the fix for sites which have not had a chance to update to 8.3.0. The Drupal Security Team urges you to reserve time for core updates at that time because exploits are expected to be developed within hours or days. Security release announcements will appear at the standard announcement locations.

This vulnerability does not affect all Drupal 8 sites; it only affects sites with certain configurations. It requires authenticated user access to exploit. The security release announcement on April 19th 2017 will make it clear which configurations are affected. If this vulnerability affects your site, you will need to update. Please set aside time on Wednesday to look into this update.

Neither the Security Team, nor Security Team members, nor any Drupal-related company are able to release any more information about this vulnerability until the announcement is made in accordance with our security policies and responsible disclosure best practices.

We provide pre-release warnings when we believe the security risk is high and the steps to exploit are scriptable.

Drupal 7 core is not affected by this issue.Contact and More Information

The Drupal security team can be reached at security at Drupal.org or via the contact form at https://www.drupal.org/contact.

Continue reading
382 Hits
0 Comments

Joomla! Automated Testing Team - Call for volunteers!

Details Published: 13 April 2017

The Joomla! Automated Testing Team is looking for new members!

The team is working on infrastructure and software tools to test the Joomla! CMS and its associated extensions. The tests include unit tests, browser-based system tests and JavaScript tests. Also infrastructure tools such as Docker to parallelize and achieve faster results. These tests are run for every pull request and commit on the Joomla! CMS.

We are currently working with the following technologies:

Codeception (System-Testing)Selenium (Browser Control)PHPUnitKarma (JavaScript Tests)Jasmine (JavaScript Tests)Docker (Infrastructure)Travis (Infrastructure)Jenkins (Infrastructure)AppVeyor (Infrastructure)Drone (Infrastructure)

There are multiple roles to fill, starting with test creation (separated into Unit-, JavaScript- and System-Tests), over architecture and setting up the infrastructure.

If you are interested in testing and want to work with latest testing technologies, please contact This email address is being protected from spambots. You need JavaScript enabled to view it. or find us in the "Testing & CI General Public Group" on Glip.

Original linkOriginal author: Yves
574 Hits
0 Comments

Joomla! 3.7.0 Release Candidate 2

The Joomla! Project is pleased to announce the availability of Joomla! 3.7.0 Release Candidate 2. We invite our users to download and test the package in order to provide quality assurance for the forthcoming 3.7 release.

What is this release for?

This is a RELEASE CANDIDATE release, that should only be used on test sites and can't be upgraded.

Extension and template developers are encouraged to prepare their extensions for the stable release of Joomla! 3.7, though there shouldn't be any backward compatibility issues. Users are encouraged to test the package for issues and to report them in the Joomla! CMS Issue Tracker.

When is the stable release due?

Joomla! 3.7 is planned to be released on April 25th 2017. Visit the Joomla! Developer site for the full roadmap.Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond our control.

Which bugs have been fixed in Joomla! 3.7?

A full list of issues resolved can be found on GitHub.

Continue reading
581 Hits
0 Comments

Technical Advisory Committee Update

In October of last year the Technical Advisory Committee was formed to evaluate options for the developer tools we use on Drupal.org. The TAC consists of Angie Byron, Moshe Weitzman, and Steve Francia, acting as advisors to Megan Sanicki, the Executive Director of the Drupal Association.

The TAC's mandate is to recommend a direction for the future of our tools on Drupal.org. Megan will evaluate this recommendation, make a decision, and prioritize that work in the development roadmap of the Drupal Association engineering team.

What is the motivation behind looking at our developer tools now?

Close followers of the Drupal project will have noticed a trend in the last several months. From Dries' announcement of easy upgrades forever, to the revamp of the project application process, to the discussion about making tools for site builders— there is a unifying theme: broadening the reach of Drupal.

This is the same motivation that underlies this evaluation of our developer tools, and defines the goals and constraints of this initiative:

Adopt a developer workflow that will be familiar to the millions of developers outside our communityPreserve those unique elements of how we collaborate that have made the Drupal project so successfulIf possible, leverage an expert partner who will help keeping our tooling up to date as open source collaboration tools continue to evolve

This means looking at a number of elements of the Drupal.org developer tool stack:

Continue reading
905 Hits
0 Comments

Drupal 8.3.0 is now available

Drupal 8.3.0, the third minor release of Drupal 8, is now available. With Drupal 8, we made significant changes in our release process, adopting semantic versioning and scheduled feature releases. This allows us to make extensive improvements to Drupal 8 in a timely fashion while still providing backwards compatibility.

Update: Drupal 8.3.1 is available and fixes a security vulnerability. You should update directly to 8.3.1 instead of 8.3.0.

What's new in Drupal 8.3.0?

This new version includes improvements to authoring experience, site administration, REST support, and a stable version of the BigPipe module. It also includes new experimental modules to abstract workflow functionality, to lay out content types differently (e.g. articles are two column vs. press releases are three column), and to provide a general layout API for contributed modules. Many smaller improvements for the experimental Content Moderation module are included as well. (Experimental modules are provided with Drupal core for testing purposes, but are not yet fully supported.)

Download Drupal 8.3.1

New and improved content authoring

Drupal 8.3 ships with the updated CKEditor 4.6, which contains a host of improvements, including better paste from Word, and a new default skin that better matches Drupal's Seven administration theme. We've also added the AutoGrow plugin, to better utilize larger screen sizes.

Continue reading
612 Hits
0 Comments

Working through the concerns of our community

This is a joint statement from project lead Dries Buytaert and Megan Sanicki, Drupal Association Executive Director.

Over the last week, the Drupal community has been in a debate over the various decisions made by us in relation to long-time Drupal developer Larry Garfield. As with any such decisions, and especially due to the circumstances of this one, there has been controversy, misinformation and rumors, as well as healthy conversation and debate. Many people feel hurt, worried, and confused. The fact that this matter became very public and divisive greatly saddens all of us involved, especially as we can see the pain it has caused many.

First off, we want to apologize for not responding sooner. We had to take a pause to process the community’s reaction.  We also wanted to take the time to talk to community members to make sure all of the concerns were heard and understood. This was further complicated by the fact that we don't have a playbook for how to respond in unusual situations like this. We also want to acknowledge that our communication has not been as clear as it should be on this matter, and we are sorry for the added confusion.

We want to thank all of the community members who stepped in to help. Many spent days helping other community members by listening, hosting discussions to foster healthy, respectful conversations, and more. You have helped many people and your caring acts reminded us once again why we love to serve the community and why it is so special.

Over the last week, we talked to many people and read hundreds of posts in various channels. These are some of the things that we heard:

Continue reading
361 Hits
0 Comments

2017 Drupal Association at-large election winner announced

*/

The staff and board of the Drupal Association would like to congratulate our newest board member:

Ryan Szrama.

Thank you, Ryan, for stepping forward to serve the Drupal community. On behalf of the community I also want to thank the 13 candidates who put themselves out there in service of Drupal and nominated themselves. We are grateful that our community has so many brave and generous people willing to contribute this way.

Ryan's election to the board represents the sixth year of elections to a community-at-large seat on the Drupal Association board. Each year we've focused on improving the elections process, and this year was no different. We focused on two goals: 

Improve the user experience of participating in the elections process. We added more in-line help materials throughout the elections process.For candidates, we added information about the responsibilities of a board member to the nomination form, as well as a video message from the Executive Director.For voters we improved the elections navigation, and provided more educational materials about the IRV voting process.We implemented a drag and drop ballot, to make it easier for voters to rank candidates. Make it easier to get to know the candidates.We updated the candidate profile form, to ask more detailed questions to help voters get to know the candidates. Based on feedback from previous years, we eliminated the three virtual meet-the-candidates sessions, in favor of giving each candidate the option to post a statement-of-candidacy video.  In conjunction with the question and answer section on each candidate profile, we felt this gave the electorate the opportunity to get to know their candidates at their own pace and on their own terms. 

Our next steps will be to reach out to the candidates for their evaluation of the elections experience.

We also want to hear from the voters. Please tell us about your experience with the elections process in the comments below. Your feedback is important to us so that we can make the 2018 elections process even better. 

Continue reading
379 Hits
0 Comments

A Statement from the Executive Director

We understand that there is uncertainty and concern in the Drupal community about project founder, Dries Buytaert, asking Larry Garfield to leave the Drupal community, and about the Drupal Association removing Larry's DrupalCon sessions and ending his term as track chair.

We want to be clear that the decision to remove Larry's DrupalCon session and track chair role was not because of his private life or personal beliefs. The Drupal Association stands by our values of inclusivity. Our decision was based on confidential information conveyed in private by many sources. Due to the confidential nature of the situation we cannot and will not disclose any information that may harm any members of our community, including Larry.

This decision followed our established process. As the Executive Director, charged with safekeeping the goodwill of the organization, I made this decision after considering input from various sources including the Community Working Group (CWG) and Drupal Project Lead, Dries Buytaert. Upon Larry’s request for an appeal, the full board reviewed the situation, all the evidence, and statements provided by Larry. After reviewing the entirety of the information available (including information not in the public view) the decision was upheld.

In order to protect everyone involved we cannot comment more, and trust that the community will be understanding.  

We do see that there are many feelings and questions around this DrupalCon decision and we empathize with those community members. We will continue to monitor comments. We are listening.

Continue reading
382 Hits
0 Comments

What our clients are saying...

  • Exceptional

    Working with Decentral Digital has completely transformed my online brand. Now most of our leads come from our website...

  • Insightful

    Mike at Decentral Digital is knowledgeable, experienced and easy to work with. We are very pleased with our website.

  • Helpful

    Mike at Decentral Digital is professional, attentive and it always seemed like he cared about my business...

  • A Force

    My only regret was that I didn't find Decentral Digital sooner. The work and level of service has been fantastic...

Enough about us, let's talk about you!

DIGITAL
HAPPINESS