Within a Drupal 8 website, there are usually a number of texts that the content manager must be able to manage but that are not real content items. We resolve this by making a user-friendly configuration form in the backend of Drupal 8, accessible to content managers. This allows us to make sure that all non-content is easy to manage, so that content managers do not have to dig through all kinds of screens in a technical backend to find the correct settings.
It took a while before I could write a new edition, I was just busy with the production of customer social intranet projects :) Here again with a brand new version, what struck me in module updates in the past month: 1. D8 Editor Advanced link
Previously we published 17 tips and trick for OpenLucius users which was well received by OpenLucius users, this sequel was inevitable. The use of standard features in OpenLucius is usually readily apparent, for example: adding groups, members, tasks, messages, files, folders and book pages. There are many useful functions in OpenLucius that make working in it more fun and easy, but are a little less obvious:
The use of basic functions in OpenLucius are pretty clear most of the time. Think of basics like: adding groups, members, tasks, messages, files, folders and book pages. But there are many useful functions in Drupal distro OpenLucius that make working in it more fun and easy, but those functions are a little less obvious for end-users. 17 tips and tricks to work faster, smarter and more efficient: Groups 1. Choose which apps are enabled by group: 2.
We updated OpenLucius, an open source work management system -contributed as a Drupal distribution. These are the 5 most important improvements: 1.Modern layout for folders and files The app ‘files’ takes care of central management of files and folders. Prevents messy document management on 'G-drives' and in email boxes.
Here’s what struck me last month about Drupal modules. This month I have chosen to focus on Drupal 8 as this is slowly becoming the go-to version - partly because many required modules have been migrated and grown up. 1. Require Login
The title is the abstract. The article is aimed at current reputable CMS web-based frameworks like Drupal, Wordpress, Joomla, Hippo, Rails, Django, etc. Why this blog post? Dries Buytaert creator of Drupal raised a simple, yet extensive question on twitter (‘@Dries’): “What could the Blockchain mean for a CMS like Drupal? #brainstorm” Let us analyse this question step by step. And then come to a surprising conclusion: it is much more interesting for Drupal to change the question.