It’s a small developer-focused conference for architects, developers, and businesspeople who are involved in implementing decoupled Drupal architectures in their various lines of work.Anli de Jager Tue, 08/08/2017 - 08:45
This 2-day conference will create a platform for those involved in decoupled Drupal architectures to come together to share their knowledge and insights during a single track of sessions about decoupled architecture strategies, technology, and best practices. There will also be opportunities to contribute to the learning experience through the building of open-source projects in sprints.
Decoupled Drupal Sites not only bring exciting new technologies to us. They also require a new way of thinking around local development and hosting. At Amazee our speciality is Decoupling Drupal with React and GraphQL and we have multiple Decoupled Sites running, all with enabled Server-Side-Rendering, CDNs and Reverse Proxies included!
Our very own Michael "schnitzel" Schmid will, therefore, be hosting a session, ‘Your PHP and Nginx won't be enough to host and develop your decoupled site’ that will address some of these questions that will undoubtedly come up, for example:
How to develop Node locally with multiple Node versions, test CORS and Server-Side-Rendering locally and make overall sure that my Node App behaves locally the same as in production.
How do I deploy, test and host that on a server when using ServerSide Rendering of my Decoupled Site built in Node.
How to use a CDN to cache my GraphQL/REST/JsonAPI requests and also the Server-Side-Rendering response.
In this session, Michael will also show you how the power of Docker allows to develop Decoupled Drupal Sites with Node and Server-Side-Rendering with a breeze and also how to use the same Docker Tools to run them in staging and production. No Docker Knowledge required :)
For more conference updates, you can follow the action here.
(This article was cross-posted from Medium.)
Every few weeks I hear from a colleague who’s dealing with the tangles of editorial tools on a web CMS project. Inevitably, someone on their team suggests that things will be easier if users can’t enter HTML at all. “We’ll use Markdown,” they say. “It’s simple.”
On most projects, it’s a terrible idea — and I’m going to rant about it. If you don’t care about the nerdy details, though, here’s the long and short of it:
Markdown turns common “plaintext” formatting conventions like asterisks, indentation, and so on into HTML markup. If you need anything more complicated (say, an image with a caption or a link that opens in a new window), you need to mix markdown and raw HTML. Markdown is easy to remember for simple stuff (blockquotes, italics, headings, etc) but more complicated structures require extensions to the standard that are just as tweaky as HTML.
It was designed to mirror the ad-hoc conventions of ASCII-only channels like Usenet, email, and IRC. As creator John Gruber said in his original introduction of the project:The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions.
Markdown’s strength is that it speeds and simplifies the most common text formatting tasks, and does so in a way that looks correct even before the markup is transformed into visual formatting. Markdown accomplishes that by ruthlessly cutting most HTML structures — anything that can’t be turned into a fairly straightforward ASCII-ism is left behind. When it’s pushed beyond that role, things get just as ugly any error-prone as raw HTML: witness the horrors of Markdown Tables and CSS In Markdown.
In many ways, Markdown is less a markup language and more a way to hide basic formatting information in a plain text document. That’s great! I use Markdown for my Jekyll-powered blog. If your project’s body field needs are simple text formatting without complicated embedding, captioning, microformatting, etc? Markdown is probably going to work fine. But — and this is a big one — if that’s all you need, then using a WYSIWYG HTML editor will also work fine.
WYSIWYG editors aren’t a pain because they “hide the code” from content creators. They’re problematic because they’re often configured to give editors access to the full range of HTML’s features, rather than the specific structural elements they really need to do their jobs. I’ve written about this “vocabulary mismatch” problem before, but it’s worth coming back to.
When you decide to use Markdown, you aren’t just choosing markup that’s easier to read; you're choosing a specific restrictive vocabulary. If that vocabulary covers your editors’ real needs, and they’ll be using plaintext to write and revise stories during their editorial workflow, by all means: consider it!
But if what you really need is a way to reign in chaotic, crappy markup, invest the time in figuring out how it’s being used in your content, what design requirements are being foisted on your editors, and what transformations are necessary for real world usage. Modern WYSIWYG editors don’t have to be the “dreamweaver in a div” disasters they used to be — taking the time to configure them carefully can give your team a clean, streamlined semantic editor that doesn’t constrain them unnecessarily.
Photo by Lee Campbell
If you want an easy way to create engaging, content-driven websites for you and your customers, you should give Drupal 8 a try. And Drupal modules allow you to take things a step further and create highly customized functionality for your site.
In our new course, Code a Custom Drupal Module, Envato Tuts+ instructor Derek Jensen will get you up and running with modules in no time. You'll build a simple calculator module, and along the way you'll learn about creating routes, controllers, parameters, and more.
You can take our new course straight away with a subscription to Envato Elements. For a single low monthly fee, you get access not only to this course, but also to our growing library of over 1,000 video courses and industry-leading eBooks on Envato Tuts+.
Plus you now get unlimited downloads from the huge Envato Elements library of 200,000+ photos and 26,000+ design assets and templates. Create with unique fonts, photos, graphics and templates, and deliver better projects faster.
Looking for a shortcut? Try downloading some of the ready-made Drupal themes on Envato Market.
Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll investigate Style Guide, a module which gathers common elements in one place, allowing you to more efficiently determine which need to be styled.
Modal dialogs are incredibly useful on websites as they allow the user to do something without having to leave the web page they are on. Drupal 8 now has a Dialog API in core, which greatly reduces the amount of code you need to write to create a modal dialog. Dialogs in Drupal 8 leverage jQuery UI.
For a long time I’ve been compiling my Sass into a single CSS file - styles.css, but recently, with our component based design/frontend process and Drupal 8’s lovely Library system I’ve been wondering if the single file was still a good idea. Looking at the amount of unused CSS loading into any given page was a little bit painful.
Some Best Practices in Drupal 7's Optimization in Performance can be achieved..heykarthikwithu Sunday, 06 August 2017 - 22:09:58 - IST, Asia/Kolkata
The corners of Drupal 8 that aren't there are quickly dwindling, but there are still some that need to get worked out. While upgrading our internal issue tracker, we hit a new one -- getting a group context set via a URL alias, and generally keeping posts within a group.Drupal 8Drupal PlanetGroupPurlOpenAtriumModule Development
Client has a bunch of static landing pages that are mobile-friendly and need to remain that way.
But what is to be done about srcset? Read on, oh reader, for the solution.
First, I created a gulp build task which makes a bunch of different sizes.
Install dependencies like this:
npm install -D gulp-load-plugins gulp-responsive sharp
The task looks like this:
There're a lot of really complicated descriptions of srcset out there.
As a result, I thought srcset was more complicated than it actually is.
Here's the all-purpose srcset code I used in my static HTML. This covers 1x, 1.5x, 2x, and mobile optimization in a fine-grained way:
At DrupalCon Baltimore, Preston So and I came up with an idea for a new Drupal conference, specifically focused on decoupled architectures, aimed at helping establish best practices and seeding a discussion about where Drupal as a whole is heading. Just a few short months have passed since then, and I’m excited that our first edition of Decoupled Dev Days is right around the corner.
As a Developer, I would love to be called a “full-stack” Developer, whose job is not limited only to clean code & bug-free delivery, but also responsible to provide infrastructure, database, back-end code, front-end code and project management ;). I’m sure you won’t be interested in client call and daily stand up call, but this is a part of our work which helps in a successful product delivery as well as client satisfaction.
Recently, I have moved on from Linux to Windows. You can understand a pain of a Developer when it comes to change your machine from hands-on machine to all new environment machine. It’s all new world with reinstallation of supported tools, drivers, applications that suit to your machine.
As a Drupal Developer, I do deal with web servers. In…
Hey, everyone! Summer moves on — together with its lovely sunsets, yummy fruit and berries and so much more. This just inspires us to grab a basket and gather some fresh, ripe, and tasty... Drupal news for you! ;) You’ll see that July 2017 has been really very fruitful for Drupal, because the community has been creating great stuff with a special, summer inspiration. So discover the new releases of Drupal modules, take a glimpse at Drupal 8.4 as Drupal 8.3’s successor, and find some other nice surprises.Read more
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.Drupal.org updates Better Distribution packaging
Distributions are a cornerstone of Drupal, giving site-builders a head start by packaging together proven modules and themes from contrib to build a Drupal site to purpose. In July we spent some time improving the functionality for packaging distributions on Drupal.org, by updating Drupal.org's packaging system to use Drush 8. This resolves several issues:
- Distributions may now use features from version 8 of Drush.
- Package manifest details are now properly displayed for all distributions.
- Distributions no longer need to nest contrib projects.
We hope that these changes will help distribution maintainersreCAPTCHA
It's hard to believe that the new documentation system has been in use for almost a year. We've made a number of improvements after the initial release to improve usability for both contributors and maintainers of documentation, and to encourage project maintainers to migrate their docs. One piece of feedback we've heard several times is that the 'add content' links the sidebar of a documentation guide were too difficult to find. To make it easier for documentation contributors to add new sub-guides and pages, we've added a new page link to the 'Edit' menu of documentation guides.Webmasters and documentation moderators can administer all docs
Finding maintainers for the over 12,000 pages of documentation on Drupal.org continues to be a challenge, and so we've given all users with the Webmaster and Documentation Moderator role the ability to administer any documentation guide. This will expand the pool of users who can help to manage documentation and manage documentation maintainers. Good documentation for a project with Drupal's scale is a community-driven effort and we're incredibly thankful for all the volunteers who contribute.Any confirmed user may claim unmaintained documentation guides
We also now allow any unmaintained guide to be claimed by any confirmed user—automatically adding them as the maintainer for that guide. This should make it much easier for new contributors to take up the mantle of maintaining sections of documentation on Drupal.org.
Learn more about maintaining documentation by reading our content guidelines.For evaluators Updated industry page call to action
The Drupal.org industry pages are a new experiment for the Drupal Association this year, with a goal of reaching out to Drupal evaluators in specific markets. The success stories we showcase on these pages demonstrate the power of Drupal in these industries, but we also want these pages to be an opportunity to connect evaluators with experts who can help them achieve their goals with Drupal. To enhance our efforts to connect Drupal evaluators to experts in their industry - we've added an additional call to action at the top of the industry page to encourage evaluators to connect with experts.Front page case study promotion for supporting partners and top contributors
In July we laid the groundwork for promoting a second row of case studies on the Drupal.org home page. The second row will feature case studies from supporting partners and top Drupal contributors. These will not replace the existing row of case studies that are featured through the community process, but will supplement these case studies with additional stories from organizations that support the Drupal project through monetary and issue contribution. Watch for these new stories in the coming months.Digital tote for Vienna
For DrupalCon Vienna we're implementing a new digital tote bag to deliver benefits to DrupalCon attendees provided by our event sponsors. This digital totebag will feature content for attendees from our Diamond, Platinum, and Gold sponsors.
Speaking of DrupalCon Vienna - prices are about to go up by €50 + VAT - so make sure to register before early bird ends on Friday.Infrastructure Audit of monitoring and backups
One of the first steps our new infrastructure partner is undertaking is an audit of our monitoring and backup regime, to ensure that we are well-prepared for disaster recovery and mitigation. While our internal team (with the help of dedicated volunteers) has maintained these existing systems, the current system is something of a patchwork of several tools, and we're hopefully that we can consolidate our tools and process and make them more robust and efficient.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects. In particular we want to thank:
- Deeson - Renewing Premium Supporting Partner
- Bits Creative Agency - *NEW* Classic Supporting Partner
- Tag1 - *NEW* Signature Supporting Partner
- Pantheon - Renewing Premium Hosting Supporting Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.