Respect those who seek the truth, be wary of those who claim to have found it.
Congratulations to the Drupal community. Today, they released Drupal 8!
It has been an epic journey to get here. Back in March 2011, we sat in the audience at DrupalCon Chicago and listened to Dries' plans for Drupal 8. To get from Chicago to today has taken over 1770 days, 3000 contributors and 350,000 lines of code.
Drupal 8 is far larger, more powerful and more modern than anything Drupal has released before.
Where I am:
- Today [11/19/15] is the BIG day! Finally, Drupal 8 launches!
- I have co-planned a party at my local Drupal group here in Indianapolis.
- I just paid $12 for this giant, blue “8” balloon! [woot woot!]
- At that party I will be delivering a show-n-tell of the new Drupal 8 back end.
- I have shared/authored social media posts to push the BUZZ along.
- Drupal 7 work still keeps me busy and pays the bills.
Where I’m going
- Tomorrow and the day after [11/20/15 & 11/21/15] I will be delivering 2 separate, free, 4hr Drupal 8 trainings for the Drupal Association’s Global Training Days
- I’m happy to say I’m working on a D8 book for a major publisher! [more on that when allowed]
- I still have a DEEP desire to work further on my BackdropCMS site which, to date, has served as a playground for exploring functionality.
The longer road ahead, as I see it
I have already stated that I’m a huge fan of what BackdropCMS represents. I believe in the the market viability of BackdropCMS. As you can tell, I’m also very excited at what Drupal 8 represents in the evolution of the web as we know it. I plan on using both as needed.
How do I reconcile the two? It’s quite easy. I have long felt that Drupal 8 is moving “Up Market.” No matter how you define that, it is true on many levels. I have no problem with this. It’s a natural evolution and I agree with those who said was long long long long overdue. I tend to agree. HOWEVER… I’m already on the record as saying that some of the changes in Drupal 8 can, will, and already have cost us some marketshare. This is where I believe BackdropCMS is a highly effective tool for keeping these existing sites from migrating to WP or some proprietary platform. Many clients around the world are super happy with their D7 sites, and they will remain happy for some time to come. It is a matter of time before we start seeing D7 sites move off of D7. Some will head to D8. Many will not. I want to be at the intersection when they change roads!
A few words about the “Ownership Society”
I have also bloviated at length about how Drupal promotes an ownership society where a team of non-CompSci grads can make amazing websites with Drupal. I keep saying that Drupal 8 raises the bar to the point that many of the current satisfied D7 users will need to rely on vendors to do the things that they currently do themselves. Then along comes BackdropCMS. Bringing balance to The Force BackdropCMS will once again empower those who are thriving in the Ownership Society that is, at least to some degree, no longer there in Drupal 8.Drupal Planet
Today is a big day for Drupal, as Drupal 8.0.0 just got released a few hours ago. So since people from all over the world will be installing it today to build websites, I'll show you guys how to solve some unusual problems that you might encounter during the installation process. When you install it on your web server, you should be most likely just fine. However, you will undoubtedly encounter the following three problems if you decide to install it on a brand new installation of WampServer (current version: 2.5):
Drupal 8.0.0 Requirements ProblemTags: Drupal Planet
Drupal 8 launched today, and with it comes a host of enhancements that benefit all of us – clients and partners alike. We're particularly excited because we – alongside thousands of others – helped architect, build, and troubleshoot Drupal 8 through its entire development process. A number of those key core contributors are on the Palantir staff, too (huge thanks to Larry, Ken, Bec, Andrea, Robin, Greg, Kelsey, Joe, and Arthur, among others!).
In fact, Palantir team members have been deeply involved in Drupal 8’s development since its start, providing technical leadership for the Web Services and Context Core and Mobile initiatives, core development support, and sprint organization. We were also an anchor sponsor for the Drupal 8 Accelerate fund which raised over $250,000 for development work on Drupal 8 to get it to completion.
For our clients, this new version introduces hundreds of breakthrough features that will help you deliver the right experience and content for your users, regardless of their location or the device on which they are viewing your site (not to mention how your editors are publishing content).
- Mobile-first: Allows content authors to publish content on any device. The entire Drupal 8 user interface has been made responsive.
- Multichannel, Dynamic Content Delivery: Delivers content “as a service” to any site, device, native application, or emerging channel with RESTful APIs.
- Front-end Flexibility: Embraces client-side frameworks like Ember.js, Angular, and Backbone so front-end developers can get creative with experience delivery.
- Enhanced Usability: Offers a reimagined, easier-to-use authoring experience, with a new editor tool and streamlined in-line, in-context authoring.
- Translation and Globalization: Designed to support global digital strategies, Drupal 8 transforms content management localization.
- Faster Development: Introduces an object-oriented web development framework and includes built-in Symfony components, staged configuration management, and improved unit testing support.
- Faster Dynamic Content: Accelerates content delivery with dynamic caching for personalized, data-driven user experiences.
We've shared a great deal on Drupal 8 in the past with Larry "Crell" Garfield's D8FTW! blog series and subsequent world tour, other keynotes and presentations, and CEO Tiffany Farriss' keynote for Chicago-based Midcamp, not to mention our Founder and CEO George DeMet's recent post on what Drupal 8 means for sites of the future.
We truly look forward to sharing our vast Drupal 8 knowledge and expertise for our clients, and continuing to act as mentors and thought leaders in our Drupal development community.
For partners like Palantir, Drupal 8 provides us a powerful object-oriented, API-based architecture that enables us to do what we do best with custom PHP code, and makes it even easier for us to create code that makes Drupal play nice with countless PHP technologies and third-party integrations that so many of our clients rely on. We love this flexibility, and the fact that it modernizes the platform in a really important way.
Dries Buytaert, creator and project lead of Drupal and co-founder of Acquia says Drupal 8, “...provides a modern development framework, a reimagined user experience, and tools that empower builders to create digital experiences that are multilingual, mobile and highly personalized."
This is important for our clients since it enables them to meet their business goals more quickly. And we can use our strategy, design, and development expertise combined with our decade of Drupal experience to provide you and your audience a world-class, truly sustainable solution for years to come.Curious about Drupal 8, and what it means for your organization?
Get in touch today, and we'll be happy to provide even more reasons why this modern, open source solution is not only an incredibly compelling choice for you, but the right one.
Let's all raise our a glass to toast Drupal 8's release, and what it means for all of us. Cheers!
Wether you are enjoying the incredible Azure ecosystem, need to deploy on Windows due to business requirements or you have any other reason to deploy on Windows, the basic tool to run Drupal 8 on Windows with reasonable performance - the WIncache module - is already available.
- Distinct options in a views exposed filter: The Views Selective Filters Module
- Drupal: Fields or Properties (or something else)
- Drupal: Add new operators to views filters (such as contained in CSV) or how to override default view's handlers
- PHP 7 nightlies for Windows
- Calling .Net Framework and .Net Assemblies from PHP
- Bypassing Form Validations and Required Fields in Drupal: the BFV module.
- Drupal 8 Wincache Integration
- Only update changed fields or properties for an entity in Drupal
- Importing Excel data with PHP, OpenXML and SpreadsheetLight: a Drupal example
- Using Heatmaps to boost conversions: Heatmap.me Drupal integration
As we get ready for our Drupal 8 release party today, over here at Chapter Three, Drupal 8 is starting to feel a lot more like business as usual. We launched our first Drupal 8 production site on 4/11/2015. In the intervening 8 months, we've built a few other Drupal 8 projects, and our team has learned a whole lot about what it means to do continuous development on this new version of Drupal.
Rather than explaining what it does, see for yourself:
(That’s with 2 slow blocks that take 3 s to render. Only one is cacheable. Hence the page load takes ~6 s with cold caches, ~3 s with warm caches.)
- Fast anonymous user page loads: Page Cache — entire page is cached.
- Fast authenticated user page loads: BigPipe — majority of page including main content is cached (thanks to Dynamic Page Cache) and sent first, the rest is rendered later and streamed.
Go and enjoy the fastest Drupal yet!2
P.S.: none of this would have been possible without my employer Acquia, whom sponsored both my time and Fabian’s to make BigPipe a reality.
We were able to release it today because the code was ready: it was developed over the course of several months in a Drupal core issue and “just” moved into a module, with every commit matching a comment in the issue, to make it easier to understand how the code base got to this point. ↩
And please report any issues you encounter at d.o/project/issues/big_pipe — depending on how well BigPipe works in the real world during Drupal 8.0.x, we should be able to get it into Drupal 8.1.x core! ↩
We just released Drupal 8.0.0! Today really marks the beginning of a new era for Drupal. Over the course of almost five years, we've brought the work of more than 3,000 contributors together to make something that is more flexible, more innovative, more easy to use, and more scalable.
Drupal 8 has been a big transformation for our community. This particular reboot has taken one-third of Drupal's lifespan to complete. In the process we've learned that reinvention doesn't come easily or quickly. There are huge market forces happening around us, and we can't exactly look away. Mobile is moving our society to near-universal, global internet access. Most companies have begun to transform themselves digitally, leaving established business models and old business processes in the dust. Digital experience builders are turning to platforms that give them greater flexibility, better usability, better integrations, and faster innovation. The pace of change in the digital world has become dizzying. If we were to ignore these market forces, Drupal would be caught flat-footed and quickly become irrelevant.
But we didn't. I'm proud to see that we've responded to these market forces with Drupal 8, and delivered a robust, solid product that can be used to build next-generation websites, web applications and digital experiences. We've implemented a more modern development framework, reimagined the usability and authoring experience, and made technical improvements that will help us build for the multilingual, mobile and highly personalized experiences of the future. From how we model content and get content in and out the system, to how we build and assemble experiences on various devices, to how we scale that to millions and millions of pageviews -- it all got much better with Drupal 8.
I'm personally incredibly proud of this release. Drupal 8 is the result of years of hard work and innovation by thousands of people, with lots of attention to detail at every level. Congratulations to everyone who stepped up to contribute; this was only possible thanks to your persistence and tireless hard work. It took a lot of learning, our best thinking and our best people to create Drupal 8, and I'm very, very proud of what we have accomplished together.
For 15 years, I have believed that Open Source offers significant advantages to proprietary solutions through superior innovation. Today, I believe that more than ever. Drupal 8 is another key milestone in helping us win and doing what is best for an open web. Of course, our job is not done but now is the time to have fun and celebrate this monumental milestone. Tonight, we'll be hosting more than 200 parties around the world! (It's also my 37th birthday today and the release of Drupal 8 along with all those parties is pretty much the best present ever!)
Drupal 8, which we previously called "the most brilliantly amazing responsive accessible version of Drupal to be released so far", has just been released. This is major news for three reasons.
Ever since I started using Drupal I've wanted to share the knowledge I have gathered around Drupal. I did some screncasts a couple of years ago, in Swedish, and they were appreciated. Then, time disappeared, other projects ate my time. Since I teach the basics of Drupal at schools and more specialized educations for companies, I've never given up on the dream of continuing the screencasts in some way.
Earlier this year the company I work for, Kodamera, gave me green light to make screencasts about Drupal. My dream has come true! A website was put together to promote the episodes and so far I have made five screencasts on Drupal. My greatest challenge will be to do these screencasts in English, since it's only my second language. Though, growing up with Monty Python get straight A's in school when it came to learing English should help a litte.
Since a stable version of Drupal 8 has been released now, I'm planning a whole series of screencasts to cover the basics of Drupal, how to get to know the system. These are not meant for us who already know Drupal, instead they are meant to give newcomers and people who are curious of Drupal a good start. The first screencast - how to install MAMP and Drupal - was released earlier this week.
I also wrote a loooong blogpost on how to install MAMP: http://screencast.kodamera.se/drupal-introduction-and-installation
Hopefully I will do a good job recording these screencasts, and I will do my best to include some good jokes and something from Monty Python now and then. ("Nobody expects the Spanish inquistion!")
See you around!
Today marks the long awaited release of Drupal 8! Join Zivtech on Friday, November 20 from 6 to 9 pm for Drupal 8 Release Jawn: Drupal Release Party, Philly Style.
There will be cake. And beer. And more beer. It's Friday! RSVP here. If you're into social media, check out that #celebr8D8 hashtag to see all the D8 parties around the world.
The Mediacurrent team has been preparing for Drupal 8 since development first began in 2011. Four years of community-wide learning, contributing and developing have lead to this day: the official release of Drupal 8.0. It’s time to celebrate!
Drupal Art has always been special for me. Here was today’s work to celebrate the release of D8 Bahubali style. Bahubali is definitely one of the greatest movies Indian cinema has produced so far. If you haven’t had a chance to watch it yet, you should definitely consider doing it. The movie is available on Google Play Store with English Subtitles!
Later today, Drupal 8 will be released! At this time, good docs are of course crucial.
As the maintainer and de facto co-maintainer of several Drupal 8 core modules and subsystems, I spent the last several days making sure that the documentation is up-to-date for:
- the Text Editor module (editor)
- the CKEditor module (ckeditor)
- the Quick Edit module (quickedit)
- the Filter module (filter)
- the Cache system
- the Render system (specifically the render caching part)
- the Asset Library system
The following drupal.org handbook pages have been either received minor updates, received complete overhauls or were written from scratch:
P.S.: if you find anything unclear on those pages, ping me in #drupal-contribute — I want to make sure these docs are as clear and helpful as possible.
First, I'd like to congratulate all teams who worked hard to get to significant completeness of Drupal 8 translations, lead by the Ukrainian and Hungarian teams who are 100% complete and the Spanish team which is close to complete too. The French, Dutch, Danish, Finnish, Japanese and Romanian teams were also hard at work and are all over 70% translated. When you are installing Drupal, there is no special task to do to install in any of the supported languages, just select that on the first screen. The translations ready at that time will be downloaded and used.
Is it a problem at all though if a translation is not complete yet when you install? I don't think so. With prior Drupal core releases, there was a huge significance of complete translations at release time because whatever people used to install Drupal was used to create all their default configuration. Content types, fields, menus, input formats and so on. Even though we have the very handy Localization update module for Drupal 6 and 7, it could not help update configuration that was already created.
In Drupal 8 we solved that problem by applying built-in translation updates to the shipped configuration as well, so if your translation does not have complete coverage yet for the shipped views, fields, contact forms, tours, etc. those will be updated later on seamlessly. Drupal also of course supports making local changes to those which would not be overwritten later with translation updates. To take advantage of this feature (which is not enabled by default), either run a manual update at Administration > Reports > Available translation updates or turn on automated updates with cron at Administration > Configuration > Regional and language > User interface translation and sit back and enjoy your Drupal 8 continually improving with translation fixes automatically.News tags: D8MI newsDrupal planetSite news
In our search to develop a headless Drupal website, we stumbled across the XML sitemap. This is needed to inform search engines, like Google, about the organization of your site content and to submit content updates. As a result you will receive reports about indexed links, broken links, duplicate content and other errors on your Drupal website.
With this knowledge it is possible to implement optimizations and it let’s your Drupal website achieve a higher SEO score. You can post the XML sitemap in the Search console of Google (Tools for webmasters).
Generating a sitemap in Drupal is relatively easy with the XML sitemap module. This is a stable module that let’s you generate a sitemap relatively quickly.
But there is no such ready-to-use content in Node.js / Express JS. To put it in simple words, the content is loaded externally (from Drupal) and transferred to the client. But since the XML sitemap is essential for SEO, we searched for a way to implement it in Node.JS. Here’s how we pulled this off:1. Install the XML sitemap module in Drupal
With Drupal 8 just around the corner, every Drupal developer is in a nirvana of excitement and eagerness. Drupal keeps getting better and better every day and Drupal 8 will make website development and management a five-finger exercise, because this latest version of Drupal has included some amazing and potent Symfony components to serve the big businesses better.Drupal Development servicesDrupal DevelopmentDrupal 8Drupal Planet