All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Seven months ago, Matthew Grasmick published an article describing how hard it is to install Drupal. His article included the following measurements for creating a new application on his local machine, across four different PHP frameworks:Platform Clicks Time Drupal 20+ 15:00+ Symfony 3 1:55 WordPress 7 7:51 Laravel 3 17:28
The results from Matthew's blog were clear: Drupal is too hard to install. It required more than 15 minutes and 20 clicks to create a simple site.
Seeing these results prompted me to launch a number of initiatives to improve the evaluator experience at DrupalCon Nashville. Here is the slide from my DrupalCon Nashville presentation:
A lot has happened between then and now:
- We improved the download page to improve the discovery experience on drupal.org
- We added an Evaluator Guide to Drupal.org
- We added a quick-start command to Drupal 8.6
- We added the Umami demo profile to Drupal 8.6
- We started working on a more modern administration experience (in progress)
You can see the result of that work in this video:
Thanks to this progress, here is the updated table:Platform Clicks Time Drupal 3 1:27 Symfony 3 1:55 WordPress 7 7:51 Laravel 3 17:28
Drupal now requires the least time and is tied for least clicks! You can now install Drupal in less than two minutes. Moreover, the Drupal site that gets created isn't an "empty canvas" anymore; it's a beautifully designed and fully functional application with demo content.
Copy-paste the following commands in a terminal window if you want to try it yourself:mkdir drupal && cd drupal && curl -sSL https://www.drupal.org/download-latest/tar.gz | tar -xz --strip-components=1 php core/scripts/drupal quick-start demo_umami />
For more detailed information on how we achieved these improvements, read Matthew's latest blog post: The New Drupal Evaluator Experience, by the numbers.
A big thank you to Matthew Grasmick (Acquia) for spearheading this initiative!
Integration Breadcrumb module with Context. This module allow dynamic
define custom breadcrumb for Drupal site.
"Our government actually does need to take a position with regard to our trade with China," Zelnick said this week. "China has been stealing our intellectual property for a really long time. Those things just have to change." ...
Cache tags are a game changer for your caching strategy in Drupal 8.Tags: acquia drupal planet
Project Paragraphs table it looks like module field collection table
- Shows table mode in new/edit
- view with table vertical or horizontal
- support display suite
Some features is in progress
- support field permission
- operation like field collection table (modify, delete, duplicate)
- support datatable
- support ajax
Checkout our latest video. We are building a 12 factor app with Drupal. This is part two in our series, building a 12 factor app. Today I’m talking about Factor Two: Dependency Management.Read more...
â€ We found with Destiny 2 â€ " and this is the case, I think, on any game â€ " that players donâ€ t want to be told when to stop playing.â€ ...
Block Sidekick provides an intuitive and interactive page authoring drag-an-drop experience for content authors and site administrators. With a sleek non-invasive dialog overlay containing all blocks available to the current page and in the current theme, users can drag a block from the Block Sidekick and place it into any region on the page.
Ready yourselves, fellow adventurers -- this year’s session and speaker lineup has been revealed! Over 60 sessions spanning the worlds of development, design, strategy, project management, technology communities and everything in between.
For two full days on Wednesday and Thursday, BADCamp offers world-class training from some of the best Drupal instructors — for far less than you will pay elsewhere, $20 for a full day session. There are only a few seats left in some of our classes, so sign up soon to reserve your spot! Register today!Sign-up for BADCamp Drupal Summits
Summits allow people in specific industries or with specific skills to dive deep into the issues that matter and collaborate freely. Registration is open and while attendance is free, signing up will ensure you receive summit specific information for the event.
If BADCamp itself was not enough, there are also other events you may want to participate in before the fun starts in Berkeley.
- What goes together with BADCamp better than Drupal Surfcamp? After a successful few days last summer in Ericeira, Portugal over the summer, Drupal Surfcamp is coming to Santa Cruz, California. What could be better? October 20-23.
- Our friends from the CiviCRM community are hold a Bay Area Meetup just before BADCamp starts, on Tuesday October 23rd. A good place to find out what CiviCRM is all about.
Would you have been willing to pay for your ticket? If so, then you can give back to the camp by purchasing an individual sponsorship at the level most comfortable for you. As our thanks, we will be handing out some awesome BADCamp swag as our thanks.
BADCamp is 100% volunteer driven and we need your hands! We need stout hearts to volunteer and help set up, tear down, give directions and so much more! If you are local and can help us, please contact Val at firstname.lastname@example.org or sign up on our Volunteer Form.Thanks to Our Sponsors
A BIG thanks Platform.sh, Pantheon & DDEV and all our sponsors. Without them this magical event wouldn’t be possible. Interested in sponsoring BADCamp? Contact email@example.com or firstname.lastname@example.org
Would you have been willing to pay for your ticket? If so, then you can give back to the camp by purchasing an individual sponsorship at the level most comfortable for you.
See you in Berkeley!
The marketing landscape is vastly different than it was when Drupal 7 was released in 2011. Since then, there has been a shift, placing the marketing team in the driver’s seat more often and almost always involved in the CMS decision. In this post, we’ll outline some of the ways you can up your SEO game with Drupal 8.Traditional SEO is dead.
No longer will well-placed keywords alone get you to the top of the SERP ranks. Content is still King in the world of marketing and it’s what helps you improve your SEO.
Every algorithm change Google has made has one thing in common: it aims to provide the best content based on what it "thinks" the user is trying to find. In other words, - what is the users intent. If you want your rankings to stick past the next update, don't try to cheat the system. Attract your prospects with informative, entertaining pieces that they can use to take action. And avoid no value posts that are keyword stuffed with your industry and the word "best" 100 times. Google can see through it and so can all of your users.
That said, there are a few other factors that are critical to keeping your rankings high that can’t be ignored including quick load times and mobile-friendliness. Drupal 8 is built with several of these factors in mind to help us make needed improvements quickly and effectively.Mobile First Mentality
Drupal 8 is created with responsive design capabilities built in, so you can begin to address any problems immediately. That’s not to say all of your responsive problems will be solved. Content editors will still need to think through their content and imagery, themers will still need to do configuration to establish things like breakpoints, etc. but Drupal 8 will set you on the right path, giving you and your team many of the tools you need.
You’ll also have the option to choose different images and content for desktop and mobile versions right from the WYSIWYG editor, making it easier to see the differences for every piece of content when you add it and before you publish. This means a solid visual of both versions in real-time for faster publishing and peace of mind knowing exactly what your users experience on any device.The Need for Speed
Drupal 8 also uses industry-leading caching technology to allow updated content to be served fresh to a client, while preserving the cache on content that hasn’t changed. So, after your visitors come to your website once, they won’t have to wait for all content to load each time, making load times much faster.
Another way Drupal 8 improves speed is through feature velocity. Because so much new functionality is built into Drupal 8 core, creating and publishing new dynamic content experiences is significantly faster than in Drupal 7. A blog post that features dynamically updated data, relevant to and powered by your content can be built in the UI in Drupal 8, something that in Drupal 7 would have taken custom development and several modules.
Responsive design is a must-have in today’s digital landscape and speeding up your website on both desktop and mobile is a surprisingly effective way to contribute to your SEO efforts. In short, if you’re marketing team is focused (as you should be) on top rankings, Drupal 8 provides many of the tools to make that happen.Accessibility = Key for Search
The release of D8 marked a big push toward improving web accessibility, including:
- Overall community commitment to accessibility
- Technical features for improved accessibility like controlled tab order and aural alerts
- All features conform with the World Wide Web Consortium (W3C) guidelines
This is important because, as we know, the relationship between web accessibility and SEO is closely intertwined.Drupal 8 SEO Modules
Here are some top Drupal 8 SEO Modules to use when optimizing your site.
- Pathauto - helps save you time from manually having to create URL path/aliases.
- Metatag - allows you to automatically provide structured metadata, aka "meta tags", about a website.
- Sitemap - provides a site map that gives visitors an overview of your site. It can also display the RSS feeds for all blogs and categories.
- Redirect - Almost every new site needs to incorporate 301 redirects for old page URLs. This gives site admins an easy interface for creating those redirects in Drupal.
- Google Analytics - This simple module allows site admins the ability to easily configure Google Analytics in Drupal.
- Easy Breadcrumbs - uses the current URL (path alias) and the current page's title to automatically extract the breadcrumb's segments and its respective links.
- SEO Checklist - uses best practices to check your website for proper search engine optimization. It eliminates guesswork by creating a functional to-do list of modules and tasks that remain.
Drupal’s content management system is perfectly structured for search optimization and its core features support many of the critical SEO elements. But, SEO is only part of the story. In the next post, we’ll explore some of the do’s and don’ts and things to keep in mind once you’re on Drupal 8.
Ubisoft showed off its in-development title HashCraft at Blockchain Gamer Connects San Francisco this year ...
GDC organizers are stillÂ accepting UXÂ Summit talk submissionsÂ -- but only until Friday, October 5th at 11:59 PM Pacific! ...
Website redesigns are a common occurrence in growing businesses, but many people get confused as to when they’re supposed to do one. Your website is a window for the world to get a look at your company. It’s a very important part of your business' marketing efforts. It’s critical to get the timing right.
While there’s certainly space between a redesign being a nice “want-to-have” and it being a “need-to-do,” here are some signs that will tell you when it’s time for a refresh.Mobile Unfriendliness
Over half of all internet traffic is now coming from a mobile device. If your website is not formatted effectively to be viewed and used on a wide variety of screen sizes, then the redesign should come much sooner rather than later. Having a design that makes the content illegible on a mobile device will send your user elsewhere.
Responsive layouts, navigation links that break up into big, tap-friendly menus, data plan-friendly image optimization, and other considerations for mobile users are what constitutes a mobile-friendly design. Google provides a Mobile-Friendly test tool you can use to check your own website.Mobile Versions or Responsive Design?
One approach to address this is to develop two versions of your website, one for mobile and the other for desktop users. The web server detects the device that your visitor is using and routes them to the correct version. The advantage of this system is that the mobile version can be optimized to be lightweight in data and speedy to load, specifically for mobile users. That means you can sideline any non-applicable considerations in your design. The biggest disadvantage is that you need to then maintain twice as many web pages: your mobile site and your desktop site.
We recommend responsive web design for our clients, instead. It's just more efficient.
Rather than developing both a desktop and a mobile version, you should have one website that will adjust its layout and navigation based on screen size. Skilled web developers can deliver fast websites to both platforms by optimizing and compressing images, using minified code (which means to strip out all unnecessary code), and other speed improvements.
By setting 'breakpoints' in the layouts, you can also have different layouts and navigation for different screen sizes. A giant drop down animated menu that looks great and is super useful on a desktop is gonna drive your mobile users bonkers.
Via breakpoints, you can set the navigation menu to collapse into a simpler menu with big finger-friendly buttons when it's served to someone on a phone.Unprofessional Design
Your website is the first impression your company makes on a user, and you want that impression to be a good one. Customers are qualifying companies as much as companies are qualifying customers. They use channels like social media, company websites, and online reputation platforms to see if the company is a good fit for their needs. Compare your website to that of your competitors. Have coworkers critique the website. Look at websites in your industry that you enjoy visiting. Does your website stack up?
Trends shift in web design, as they do in fashion - what looked great in the past can be jarring or cringe-inducing now. Showing up to a pitch meeting in dated business attire projects the impression that you either don’t care about or are ignorant of modern clothing trends. When a visitor lands on your website, dated design projects that same impression.
Web design can look unprofessional if its inconsistent with your brand. Your website needs to clearly call out your company's value statements to your visitors. Unappealing fonts, low-quality icons, slapdash layouts, and thoughtless color palettes confuse and build mistrust in your visitorsUser Experience and Design
Good design is about more than just the visuals of your website. It considers the users' needs and their experience while navigating and using your site.
Intuitive navigation needs to tell the user where they are, how they got there, how near their destination is, and how they get there. Thoughtful categorization of content complements your design. By grouping things in a way that makes sense to your visitor, you make it easy for them to solve their problems or satisfy their needs.High Bounce Rate
Bounce rate is a metric describing the percentage of your visitors that leave your website within moments of arriving from a search results page. Either they were sent away by a technical problem or something about your website compelled them to leave of their own volition. You can see your bounce rate in analytics suites, like Google Analytics, assuming you have the code installed.
If you DON’T have this software installed, you have no way of knowing how effective or ineffective your website is. Bounce rates are considered to be great if they're in the 20's to the 30's (percentage-wise) and acceptable in the 40's and mid-50's. Upper 50's and up, is considered to be a high bounce rate.
There are two important things to note here. First is that these classifications are generalizations across a broad swathe of industries. Websites in some industries have a lower bounce rate since their content is more engaging. Second is that you should only be worried about human visitors to your website when it comes to bounce rate.
In your web analytics software, it's important to filter out bots and crawlers from your data. Moz has a great explanation and guide to filter out bots from Google Analytics.
A high bounce rate means that your website is not serving its basic function in some fundamental way. This is a major problem that needs to be addressed as soon as possible. There are a number of reasons that visitors could be bouncing from your website, but some major ones are:Slow loading pages
When a visitor arrives on your site, they expect the content to load nearly instantly. High load times (or latency) could be caused by bloated code (an inexperienced developer used way more code to achieve a result that a more experienced developer could have done with less). It could also be due to an inefficient system of fetching and displaying content or it might simply be large images that aren't optimized for the web.
The longer the loading time, the greater the chance that your visitor is going to head back to the search results and try the next option. Since your site likely appeared in their search results because you offer something they were looking for, this means your visitors went to a competitor.Confusing Titles or Meta Descriptions
The page title (as denoted in your website by the tag) appears in search results. It's read by search engine robots and used to categorize your website in their indexes. Meta descriptions (which appear in tags) are brief summaries of the content of the page (By default, this will be filled with the first few lines of text if you leave it blank).
While search robots don't pay much attention to meta descriptions, visitors do. They read it and the title tag to decide if the answer to their problems lie on your page. If they arrive on your page and the content doesn't match the title or meta descriptions, they're really likely to head back and try another result.Technical Errors
For some visitors, they could land on your website and not find the content they're looking for. The URL they clicked on leads to a page that does not exist. There's no reason to stay, so the visitor heads back to the search results. Or they arrive and are redirected to a redirect in a permanent loop until they give up and try a different result.
Errors like 404 (Page not Found) or 301 (Permanent Redirect) loops are a very poor experience for the visitor and they can contribute to a high bounce rate.Frustrating Content Administrator Experience
Administrator experience is a term that describes the ease of use of the website for normal operations. Updating copy, adding new articles, adding products to an online store are some everyday tasks for your webmasters and content editors. They need to be straightforward and simple to accomplish. If you need a professional web developer to make content changes or updates, you’re in dire need of a redesign. A good solution might be switching to a content management system like Drupal or WordPress. They excel at making life easier for website administrators who are not developers. This is particularly true if you have multiple people adding content to the website.
One of the simplest ways to improve an administrator experience is to review permissions for each user and limit them based on needs. A content administrator can focus on just the tasks they need to accomplish, making it easier to familiarize themselves with the interface.
Drupal has pretty granular permission systems in place right out of the box, letting you choose what each user can do. WordPress' permissions are role-based, meaning you assign a person to a category (Administrator, Editor, Author, etc) and they inherit all the permissions of that role. WordPress can be extended with plugins to grant more permission setting ability.Outdated Code
Even the best website will eventually need to be refreshed. Web technology evolves and improves constantly. New versions of programming languages like PHP, Ruby on Rails, and Java (to name a few) are released in updates. Eventually, much older versions of software stop being regularly updated.
This is a problem. The outdated code is a big security weakness, making it one of the first targets for malicious hackers. When support ends for older versions of software, it becomes more difficult and more expensive to maintain that website (since any fixes and updates have to be custom development). This becomes even more of a problem when the outdated software has dependencies or other software that requires it.
A redesign can be a good opportunity to refresh all of the software at once, bringing your site’s code up to the latest versions in one fell swoop.Is it time to redesign your website?
Trends in web design, user experience, and digital marketing shift relatively rapidly. You can expect to redesign your website every 3-5 years if you want to stay current. For companies, this means that what visitors to your site will both expect and accept also changes. If your site doesn't meet the expectations of your customers, they'll leave. On the Internet, they're not starved for choice.
Send us a message if you'd like to talk about redesigning your website. We'd be happy to do a free site review!Name Company Email Phone Message Website Want news, tips, and exclusive content?
The journey from a visitor to the client doesn’t happen overnight nor over a single screen.
It is unfair on the part of organizations to assume that all readers will be using the same screen to consume their content.
In case organizations are working towards targeting various visitors it is important to have a durable and centralised content dissemination platform to serve digital content through various screens.
Therefore it is equally important that various mediums ensure a smoother journey and the backend - content repository - provides a seamless translation of information to various touchpoints.What is a Content Repository?
“A content repository is a database of (digital) content with an associated set of data management, search and access methods allowing various application-independent access to the content with the ability to store and modify content.”
The content repository acts as the storage engine for a larger application such as a CMS which adds a user interface on top of each of the repository's application user interface.
The proliferation of content across a variety of sources can create an enormous business challenge. As the unstructured content grows, organizations need to look for a flexible approach that supports interoperability with a wide array of popular systems and products.
A robust central content management repository should store a variety of content formats, facilitate read/write capabilities, control access.
Here are some of the features of a content repository:
- Efficient storage to integrate content
- Query and Search
- Import/export the content
- Editor accessibility for all the documents and the content.
- Records retention management systems
- Document capture systems and document-imaging (Complementary systems)
Difference between a Content Repository and CMS
A content management system manages the creation and modification of digital content and typically supports multiple users in a collaborative environment.
While a content repository disseminates the content to be shared between disparate websites, different kinds of devices or channels such as mobile phones, tablets, kiosks, Facebook or syndicated via an API.
A central content repository allows the content editors to edit content directly from the backend of one site. The content editors simply choose the topics that the content belongs to, and the sites subscribe to those topics and it is then available to all the connected sites automatically.
A Content Repository Workflow works like this:
Content creation of a topic happens on Site A.
- The content is shared via a central content repository.
- Site B is subscribed (sync rules) to receive updates whenever the content for the same topic is created.
- Site B, C, D receive the notification and pull in the content.
- If any user on site C searches for the new content published through site A, she will get it through the content repository.
Drupal 8 is well suited to act as a central content repository, as it has built-in support for REST web services, a serialisation component, and can be configured to work with publishing workflows and notifications.
Search web service such as Apache Solr or ElasticSearch can best provide a lookup service for each site. Rather than subscribing to a particular topic, content editors can simply search for the content they wish to import from.Application of Drupal as a Central Content Repository
- Content management
- Document management
- Digital asset management
- Records management
- Revision control
- Social collaboration
- Web content management
Content is not only the material you use to develop your CXM strategies—it’s also the interactions between customers and prospective customers have with you. Talking about the online customer experience, a CMS is part of the process of designing and supporting CX strategies.
Simply because it stores all the content you need to manage the experience. However, customer experience management is about more than the online channels.
In order to successfully manage the customer experience, the CMS needs to be able to quickly access and react to the elements of a customer interaction. Not just this, the elements should be accessible to the editors as well.
Managing every single version of the web pages is a heck of a job and ensuring that the content looks just the same is another fight.
Most, if not all, CMSs are designed to store content not just as HTML pages, but as individual components that can be easily reused across different web pages. Across various devices, mobile sites and apps, and social networks.
In this way, the content repositories can be leveraged to provide content as well.
Content integration is the key to a well-managed content repository. Managing the content by integrating it with all the other systems.
A central content repository also allows you to develop the support applications that have access to customer information easily, including information from CRM systems, traffic information, and the like.
Having it all accessible in a centralized content repository will help you identify, design, and refine your CX strategies quickly.Building a Central Content Repository for FarmJournal Media
For Farm Journal Media, OpenSense Labs have implemented a similar centralised content management system.
- Drupal 8
How Did It Work?
Express.js- node.js framework provided a library of many pre-built functions which were leveraged for the CCMS.
It allowed simultaneous access to multiple authors without compromising on speed. This could be done by leveraging its events loop based asynchronous task handling.
The interface to serve content was developed via MongoDB. The system triggered updates of content from CCMS to MongoDB asynchronously and in real time. This ensured the cron jobs do not overload the sites as the webhook request will be triggered only when required.
Due to this layered architecture, the overall content journey once the editor hits save, to consumer site was at max 3 seconds.
An increase in consumer sites, update count and pull requests do not affect the load on CCMS Drupal.
A special fail handler was built to sanity check between CCMS, Mongo and consumer sites. This ensured there was no duplicity and maintain an error log for missing articles during the journey it takes with an exact failure points reported.One of the sites of FarmJournal
How Did the CCMS Worked?
It allowed the team of editors to:
- Centrally manage the content through one platform
- Cross-publish articles on full networks of FarmJournal sites
- Use a simple site vs category mapping for automated syndication of articles.
- Have a centralised reporting to boost the editorial teams’ productivity & article publication pace.
A traditional website on Drupal allows content editors to add or edit content with a preview for the content as well. This is because a traditional CMS is tied (or coupled) to a front end (which is the case with Drupal).
Taking the front end out of the equation can bear its own challenges.
The front end is what a user sees when viewing an application, which, in Drupal’s primary case, is a website.
Content editors can view the content before it’s published using a wide array of tools such as inline editing or pre-published previews.
Available modules in Drupal allow for quick and relatively easy modification to how the data is displayed on the frontend. Developers aren’t always needed to make simple changes, which can be more efficient for both time and cost, possibly a huge benefit to using a coupled CMS.
Drupal 8 has a strong emphasis on providing many API services out of the box, and there is a strong push for the API-first approach.Headless CMS (the API-only approach)
With API-first Initiative at the forefront, Drupal 8.0 was shipped with a built-in REST API which spelt the beginning of Drupal’s transformation as an API-first platform.
A headless CMS often confused with a decoupled CMS is considered an API-only approach.
It provides a hub for the content sans any frontend.
The backend allows content editors to publish content distributing it automatically to any integrated application. Since there is no coupled frontend interface to immediately view the data applications such as Digital signage need be developed and integrated in order to access this content.
In such a scenario trialing and proofing content before publishing can be difficult. Another challenge is the layout which can be a limitation to the marketing teams.
The Drupal community has already taken steps towards making sure Drupal continues to be a relevant contender as either a coupled OR headless CMS.
Drupal distribution Open Y can be used to build such applications for a Digital Signage.
Drupal Distribution Contenta can be used as an API to connect the backend of Drupal with any application.Conclusion
Previously unstructured and inaccessible content comes alive in digital business applications that engage customers, automate business processes, enhance collaboration and govern and protect content throughout its lifecycle.
Content management services and solutions from OpenSense Labs support your digital transformation and help you build a cognitive business that is confident, efficient and competitive. Drop a mail at email@example.com banner blog image Content Repository Content Management System Drupal Drupal 8 Consumer Experience Digital Signage Contenta CMS Database Coupled CMS API-first Drupal Decoupled CMS Blog Type Articles Is it a good read ? On
This blog has been re-posted and edited with permission from Dries Buytaert's blog. Please leave your comments on the original post.
Since the launch of Drupal 8.0, we have successfully launched a new minor release on schedule every six months. I'm very proud of the community for this achievement. Prior to Drupal 8, most significant new features were only added in major releases like Drupal 6 or Drupal 7. Thanks to our new release cadence we now consistently and predictably ship great new features twice a year in minor releases (e.g. Drupal 8.6 comes with many new features).
However, only the most recent minor release has been actively supported for both bug fixes and security coverage. With the release of each new minor version, we gave a one-month window to upgrade to the new minor. In order to give site owners time to upgrade, we would not disclose security issues with the previous minor release during that one-month window.
Illustration of the security policy since the launch of Drupal 8.0 for minor releases, demonstrating that previous minor releases receive one month of security coverage. Source: Drupal.org issue #2909665: Extend security support to cover the previous minor version of Drupal and Drupal Europe DriesNote.
Over the past three years, we have learned that users find it challenging to update to the latest minor in one month. Drupal's minor updates can include dependency updates, internal API changes, or features being transitioned from contributed modules to core. It takes time for site owners to prepare and test these types of changes, and a window of one month to upgrade isn't always enough.
At DrupalCon Nashville we declared that we wanted to extend security coverage for minor releases. Throughout 2018, Drupal 8 release managers quietly conducted a trial. You may have noticed that we had several security releases against previous minor releases this year. This trial helped us understand the impact to the release process and learn what additional work remained ahead. You can read about the results of the trial at #2909665: Extend security support to cover the previous minor version of Drupal.
I'm pleased to share that the trial was a success! As a result, we have extended the security coverage of minor releases to six months. Instead of one month, site owners now have six months to upgrade between minor releases. It gives teams time to plan, prepare and test updates. Releases will have six months of normal bug fix support followed by six months of security coverage, for a total lifetime of one year. This is a huge win for Drupal site owners.
Illustration of the new security policy for minor releases, demonstrating that the security coverage for minor releases is extended to six months. Source: Drupal.org issue #2909665: Extend security support to cover the previous minor version of Drupal and the Drupal Europe DriesNote.
It's important to note that this new policy only applies to Drupal 8 core starting with Drupal 8.5, and only applies to security issues. Non-security bug fixes will still only be committed to the actively supported release.
While the new policy will provide extended security coverage for Drupal 8.5.x, site owners will need to update to an upcoming release of Drupal 8.5 to be correctly notified about their security coverage.Next steps
We still have some user experience issues we'd like to address around how site owners are alerted of a security update. We have not yet handled all of the potential edge cases, and we want to be very clear about the potential actions to take when updating.
We also know module developers may need to declare that a release of their project only works against specific versions of Drupal core. Resolving outstanding issues around semantic versioning support for contrib and module version dependency definitions will help developers of contributed projects better support this policy. If you'd like to get involved in the remaining work, the policy and roadmap issue on Drupal.org is a great place to find related issues and see what work is remaining.
This module allows you to edit existing file or image entities.
Updated a PDF file? An image? No problem with File Management!
This module is super alpha, active development will follow though!Important note 2
Don't use the module (yet) if you're making use of revisions.