Acquia Labs has no illusions of making self-driving cars or shooting things into space like Google X, but the budding applied research arm of enterprise open-source Drupal provider Acquia does have designs on a slew of new applications for what it anticipates will be an increasingly browserless world.
Preston So, development manager at Acquia Labs and a 9-year veteran of the Drupal community, shared his vision for Acquia’s skunkworks-plus outfit at the company’s annual Engage event for customers held in Boston this week.
Anyone who knows me knows that I like to try new things — phones, gadgets, apps. Last week I downloaded the new Wix (closed, proprietary, non-open-sourced, non-GPL) mobile app. I’m always interested to see how others tackle the challenge of building and editing websites from a mobile device.
I started playing around with the editor, and felt… déjà vu. It was familiar. Like I had used it before.
Turns out I had. Because it’s WordPress.
So WordPress and Wix are fighting one another – and I'm not talking about them competing for customers. Instead, the two website building heavyweights are having a brawl via the blogosphere.
Attackers are aggressively attacking Joomla-based websites by exploiting two critical vulnerabilities patched last week.
The flaws allow the creation of accounts with elevated privileges on websites built with the popular Joomla content management system, even if account registration is disabled. They were patched in Joomla 3.6.4, released Tuesday.
Georgia's enterprise web platform runs on Drupal 7, which includes many accessibility features in its baseline code and structure. That makes it easier for any new site to build in accessibility from day one. This comes with the caveat that not all modules are accessible, and plenty can be coded and designed without accessibility in mind, meaning that just using Drupal does not make a site accessible to users with disabilities. That said, even in its original implementation with Drupal 7 in 2012, Georgia's web publishing platform was built to meet federal accessibility standards (Section 508, for those of you interested in the details).
From there, when the product team wanted to improve the platform's underlying code to meet the more modern WCAG 2.0 AA accessibility guidelines, they were working from a flexible and scalable base.
A day after being on the receiving end of allegations that it not only stole code from WordPress, it also failed to contribute back to the open-source community, Wix has responded, saying that the claims against it are baseless and that its do-it-yourself website building platform has been operating in good faith.
In an open letter to WordPress creator Matt Mullenweg, Wix chief executive and cofounder Avishai Abrahami answered every criticism leveled at his company. He admitted that Wix did use WordPress’ open source library for “a minor part of the application,” but claimed that every modification or improvement the team made was submitted back as open source. Mullenweg had said previously that Wix’s mobile app editor, which was released this month, was built using “stolen code.”
Recently, Automattic CEO Matt Mullenweg’s accused Wix of stealing source code from WordPress and using it in the company’s mobile app “without attribution, credit, or following the license”. Wix, deciding it was best not to let Mullenweg’s stipulations go unchallenged, has fired back with a double-barrelled, if wishy-washy, reply.
Matt Mullenweg’s letter garnered not one, but two responses from Wix: the first from CEO Avishai Abrahami and the second via the company’s lead engineer Tal Kol.
Matt Mullenweg, the creator of WordPress, is not happy with the editor used in the Wix mobile app, saying the web building service copied his platform. Wix.com's CEO Avishai Abrahami responds to Mullenweg's accusations.
Mullenweg said in his blog that Wix's mobile app seems familiar to him, it's like he had used it before. He said he has because it's WordPress.
"If I were being honest, I'd say that Wix copied WordPress without attribution, credit, or following the license," he said. "Wix has always borrowed liberally from WordPress - including their company name, which used to be Wixpress Ltd. - but this blatant rip-off and code theft is beyond anything I've seen before from a competitor."
Nasdaq Corporate Solutions, a business line of Nasdaq, Inc., is banking on the collective input from users of Drupal open-source web content management technology to empower its platform for IR websites.
Moodle is a very popular course-management system, equivalent to Blackboard, but entirely free and open source. This short YouTube video by Moodle expert Nellie Deutsch explains how you can install Moodle in your cPanel with Softaculous in under 2 minutes.
Dries Buytaert announced today that Nasdaq Corporate Solutions has selected Drupal 8 and will work with Acquia to create its Investor Relations Website Platform. In the words of Angela Byron, a.k.a "Webchick", "This is a big freakin' deal."
Drupal began as a forum for a few friends to monitor their shared Internet connection, which "was expensive and being spliced between them," according to Jared Whitehead's The rise of Drupal and the fall of closed source. Today, it's one of the most popular content management systems out there, competing with powerhouses like WordPress.
So, what has the Drupal community done to ensure continued competitiveness, usability, and overall sustainability? In this article, I'll walk you through Drupal's evolution chronologically, including key design decisions and feature upgrades. My sources include the History of Drupal: from Drop 1.0 to Drupal 8.0 slideshow by WebSolutions HR and Drupal's CHANGELOG.txt.
After years of development and competition, open source content management systems (CMS) have proliferated and are very powerful tools for building, deploying and managing web sites, blogs and more. You're probably familiar with some of the big names in this arena, including Drupal (which Ostatic is based on) and Joomla.
As we noted in this post, selecting a CMS to build around can be a complicated process, since the publishing tools provided are hardly the only issue. The good news is that free, sophisticated guides for evaluating CMS systems have flourished. There are even good options for trying open CMS systems online before you choose one. Here, in this newly updated post, you'll find some very good resources.
he first thing to pursue as you evaluate CMS systems to deploy, including the many free, good platforms, is an overview of what is available. CMSMatrix.org is a great site for plotting out side-by-side comparisons of what CMS systems have to offer. In fact, it lets you compare the features in over 1200 content management system products. Definitely take a look. This site also has a good overview of the options.
Content management systems are boring until you have to use one. You can install a little Drupal or WordPress, pick up some Squarespace, or just dump to Medium, the graveyard for posts about protein shakes and VC funding. But what if you could roll your own CMS? And what if you made it really cool?
That’s what Cory LaViska did. LaViska is the founder of SurrealCMS and has been making it easy to edit stuff on the web for nine years. Rather than build and sell an acceptable CMS, however, he took all of his best ideas and made a far better CMS. And he made it open source and called it Postleaf.
The biggest mistake is bigger than Drupal: They don't consider it at all. This isn't a platform thing, it's a problem that is endemic to the web. Big companies get dragged into accessibility via legal threats. Small companies don't even think about it. Just the act of raising accessibility as an issue, and asking your team to keep it in mind throughout the design and development process is a big deal. You have to start somewhere.
I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3.
A veteran of the web publishing and sports media industries, Jeff Diecks leads professional services and client delivery at Mediacurrent and is an active member of the Drupal community. Jeff also organizes events for his local Louisiana Drupal Users Group and Drupalcamp New Orleans.
I was able to catch up with Jeff ahead of DrupalCon New Orleans 2016, where he'll share insights on site building tools to solve common university needs.
Back in the day, I was working at a large nonprofit in the "webmaster's office" of the marketing department and was churning out custom PHP/MySQL forms like nobody's business. I finally got weary of that and starting hunting around the web for a better way. I found Drupal 6 and starting diving in on my own. Years later, after a career shift and a move, I discovered the Portland Drupal User Group and landed a job as a full-time Drupal developer. I continued to regularly attend the meetups in Portland, which I found to be a great source of community, friendships, and professional development. Eventually, I landed a job with Lullabot as a trainer creating content for Drupalize.Me. Now, I'm managing the Drupalize.Me content pipeline, creating Drupal 8 content, and am very much involved in the Portland Drupal community. I'm this year's coordinator, finding and scheduling speakers.