Drupal

Agiledrop.com Blog: AGILEDROP: DrupalCon sessions about Front End

Planet Drupal - 14 June 2017 - 3:12am
Last time, we gathered together DrupalCon Baltimore sessions about Site Building. Before that, we explored the area of Drupal Showcase, Coding and Development, Project Management and Case Studies. And that was not our last stop. This time, we looked at sessions that were presented in the area of Front End. Atomic Design in Drupal 8: Isolating frontend workflow with Pattern Lab! by Anthony Simone from Elevated Third This session reviewed the basic principles of Pattern Lab and atomic design but focused on the practical implementation of Pattern Lab in the next Drupal project.   Back… READ MORE
Categories: Drupal

owl

New Drupal Modules - 13 June 2017 - 10:52pm

Integration with OWL Carousel. More details coming soon.

Categories: Drupal

Sudhanshu Gautam | Blog: GSoC 2017 | Week 2: Port Vote Up/Down

Planet Drupal - 13 June 2017 - 9:48pm
GSoC 2017 | Week 2: Port Vote Up/Down sudhanshu Wed, 06/14/2017 - 10:18
Categories: Drupal

David Corbacho: DrupalCon Front End Track

Planet Drupal - 13 June 2017 - 3:28pm

DrupalCon Dublin seems like it happened yesterday, but it's already 9 months ago.
This blog post is a summary of the Front end track.
Late but, anyway, I want to write it down for two reasons:

1) Express again my gratefulness to the great speakers we had on the front end track. Everyone gave their best and quality of the sessions were high. Yay! Do you know the frontend track was the most attended track in DrupalCon Dublin?

2) Motivate previous and new speakers to submit sessions for the upcoming DrupalCon Vienna (consider also the Horizons track)

As a frontend track chair, I thought that something I could do for the speakers was to immortalise the moment where our brilliant speakers were in the DrupalCon stage.
Here we go:

Improving the Responsive Web Design Process in 2016

Recorded session in Youtube / Session description

Cristina Chumillas did a great summary of best practices, and I enjoyed her demo how to achieve responsive images with Drupal 8.
Cristina is also the frontend track chair for DrupalCon Vienna and organizes Drupal Summer (29th of June, Barcelona)

Streamlined Front-end Development with Pattern Lab and Twig

Recorded session in Youtube / Session description

Adam Juran focused on explaining how Forum One are putting together Pattern Lab and Drupal 8, with Twig templates acting as a bridge between both systems. This has even more sense if you have different teams doing design and development, making boundaries clear. In this slide you can see a summary of the proposal.

Structure for Creativity

Recorded session in Youtube / Session description
The session was divided in two parts: Janne Bjørsted, UX designer explained how they structure the work and creative process when building products in their company. Then Mads Thines, frontend developer, went through his workflow / tools and useful coding tips.

Super Collaborative Design Processes for Teams

Recorded session in Youtube / Session description

Lewis Nyman talked about design process and gave tips and techniques for design workshops. Recommended the book Sprint, by Google Ventures folks.

Closing the Gaps: Prioritizing Accessibility in Custom Themes with Drupal 8

Recorded session in Youtube / Session description

Erin Marchak gave the 2nd best-rated Frontend session. Full of useful information about a11y, tips, demos and even the deliver of the session was outstanding (she made the effort to explain verbally the animated gifs to reach everyone). A true example of a high standard DrupalCon session.

Drupal 8 theming in depth

Recorded session in Youtube / Session description

Lauri gave a overview of advanced Twig patterns, and then hit one of the challenges when theming Drupal 8: how to build a component-based design system.
Lauri also introduced the plan of creating a new default theme in Drupal core, that will show / demo better the possibilities of creating beautiful websites with Drupal 8 in other session. This is part of the effort to improve the "out of the box" experience.

Design Principles for Minimum Viable Product

Recorded session in Youtube / Session description

Junaid Masoodi gave an overview of applying MVP to the design phase

21 things i learned with Twig & Drupal

Recorded session in Youtube / Session description

Morten Birch gave a condensed session full of tips and things that you might not now about Twig. He announced at the end of the session his new admin theme project, that later was named Eleven

Animate Your Site

Recorded session in Youtube / Session description

Nikhil and Vidit gave a session introducing animation principles, and then apply them to real world cases. I like how they introduced humor to the session to make it light-weight and more enjoyable.

Creating Layouts and Landing Pages for Drupal 8

Recorded session in Youtube / Session description

Suzanne Dergacheva explained different approaches to the question every Drupal themer has. What tools to use to build the layout ? Panels, paragraphs, blocks? I appreciate that she explained the concepts with a realistic use case. In my opinion, a excellent example of a session with a good balance of introduction, theory, advanced concepts and demo.

React Front-end For Your Drupal 8 Back-end

Recorded session in Youtube / Session description

Bassam and Aliyah explained how you can integrate React and Drupal, conceptually and also giving details and explaining it with code snippets where the magic happens.

Automated browser testing with Nightwatch.js

Recorded session in Youtube / Session description
Vladimir flew all the way from Australia to explain why you should use Nightwatch.js for e2e testing. I was amazed how easy and painless can be.

Conclusion

I hope this summary gives you an idea of what session we are looking for in the frontend track.
Please, submit your session for Drupalcon Vienna. We care about the content, and that you have some previous experience as a speaker. It helps the track chairs to warranty the quality of sessions are high.
Check also DrupalCon Baltimore sessions for inspiration

Categories: Drupal

Telephone Type

New Drupal Modules - 13 June 2017 - 2:41pm

This is a module that extends the code telephone module by including the ability to select a type of telephone number (ie Cell, Work, Fax), and also validated the number. It uses libphonenumber-php library (port of google's libphonenumber library).

Categories: Drupal

Colorfield: Migrating SQL in Drupal 8 with Migrate Tools and Migrate Plus

Planet Drupal - 13 June 2017 - 1:21pm
Migrating SQL in Drupal 8 with Migrate Tools and Migrate Plus christophe Tue, 13/06/2017 - 22:21 Migrate API is awesome, and if you plan some custom migration, a few contributed modules does the heavy lifting for you. This article should be regarded as a list of steps to follow to achieve a simple migration from another SQL data source than Drupal. So we will not go in deep into the explanations of the Migrate theory, for this subject, refer to the documentation of the Migrate API. Also, we will finish with some debugging techniques and a first shot of a bash script for rerolling a migration from scratch in case of configuration change.
Categories: Drupal

Zivtech: 7 Server Metrics You Should be Monitoring on Your Drupal Site

Planet Drupal - 13 June 2017 - 12:07pm

Computers are finicky. As stable and reliable as we would like to believe they have become, the average server can cease to function for hundreds of different reasons. Some of the common problems that cause websites or services to crash can’t really be avoided. If you suddenly find your site suffering from a DDOS attack or a hardware failure, all you can do is react to the situation.
 
But there are many simple things that are totally preventable that can be addressed proactively to ensure optimal uptime. To keep an eye on the more preventable issues, setting up monitoring for your entire stack (both the server as well as the individual applications) is helpful. At Zivtech, we use a tool called Sensu to monitor potential issues on everything we host and run.
 
Sensu is a Ruby project that operates by running small scripts to determine the health of a particular application or server metric. The core project contains a number of such scripts called “checks.” It’s also very easy to write custom checks and they can be written in any language, thus allowing developers to easily monitor new services or applications. Sensu can also be run via a client server model and issue alerts to members of the team when things aren’t behaving properly.

Server checks

As a general place to start, you should set up basic health checks for the server itself. The following list gives you a good set of metrics to keep an eye on and why it is in your best interest to do so.

RAM What to check

Monitor the RAM usage of the server versus the total amount of RAM on the server.

Potential problem monitored

Running out of RAM indicates that the server is under severe load and application performance will almost certainly be noticeable to end users.

Read more
Categories: Drupal

Acquia Developer Center Blog: Learn Drupal 8 Online and Get Certified with this New Course

Planet Drupal - 13 June 2017 - 12:06pm

One of the questions we get most often is, "How do I prepare for the Acquia Certified Developer - D8 Exam?" Now we've got an answer: the Drupal 8 Developer Immersion Course w/ Certification Prep - an 8-week, instructor-led, project-based online course that covers all areas of Drupal 8 and prepares you to take the Acquia Certified Developer - D8 Exam.

Tags: acquia drupal planet
Categories: Drupal

Form Creator

New Drupal Modules - 13 June 2017 - 11:53am
Categories: Drupal

vactory_cross_content

New Drupal Modules - 13 June 2017 - 11:23am

in English :
This is module add the cross content features.
You can link each node with others nodes (from several content types).

en Français :
Ce module permet d'implémenter la fonctionnalité "contenu lié" ou "cross content".
Sur chaque noeud, vous pouvez remontez des teaser d'articles de différents types de contenu.

Categories: Drupal

Tameesh Biswas | Blog: GSoC17 : Client Side File Crypto : Week 2

Planet Drupal - 13 June 2017 - 10:50am
GSoC17 : Client Side File Crypto : Week 2

This blog post summarizes the second week of coding with Drupal in Google Summer of Code 2017 

tameeshb Tue, 06/13/2017 - 23:20 Tags GSoC Google Summer of Code 2017 Drupal Drupal Blog
Categories: Drupal

Drupal core announcements: Make a difference for D8 at the DrupalCamp Montréal sprints

Planet Drupal - 13 June 2017 - 10:18am
Start:  2017-06-15 (All day) - 2017-06-18 (All day) America/Toronto Organizers:  xjm Event type:  Sprint

DrupalCamp Montréal is coming up this Thursday to Sunday (June 15th to 18th), with great trainings, two days of sessions, and a dedicated sprint day on Sunday. The sprint gives you a great opportunity to get involved and make a difference for the things that affect Drupal and your projects. You don't need to be an expert, developer, or existing contributor to get involved. Here are three current focus areas that we'll collaborate on on this week!

Major issue triage

Major issue triage sprints have been held at many DrupalCons and camps recently and Montréal will continue these efforts. We want to fix the most important bugs in Drupal, but the first step to that is making sure bug reports are up to date and actionable. That is where major issue triage helps: identifying reports that should be critical, closing ones that are no longer relevant, downgrading ones that are actually less severe, and making sure relevant reports can move forward to a fix. Sometimes just asking questions for clarification on bug reports will move things ahead a lot. Still not convinced this sprint is for you? Read more in my blog post from earlier this year.

Make upgrade paths easier with @deprecated documentation

We made several changes in the release process with Drupal 8 to make Drupal upgrades easy forever. One of them is that we improve Drupal's APIs in scheduled six-month minor releases, but also leave the old ways of doing things in place and mark them as deprecated until Drupal 9. This huge shift for Drupal allows module maintainers to adapt to changes gradually, on their own schedule, instead of needing a massive push all at once on some later release date.

API deprecations are documented in change records on Drupal.org, and also marked directly in the code documentation. We started marking deprecated code almost two years ago as we were preparing to release Drupal 8.0.0, and we have been creating change record documentation since the release of Drupal 7. Unfortunately, we did not start to connect the two until recently, so it was not possible to read more about a certain change when you encountered a deprecated API. Help make these connections for an easier upgrade path for everyone.

Clearly define Drupal's public APIs

As we mentioned above, Drupal 8 has 6-month minor releases that improve APIs (as well as adding new features). In order to make this safe, clear, and maintainable, we defined what parts of Drupal's APIs are internal through a documented policy, but that is not very explicit for developers. Making this explicit in code documentation is more effective for anyone reading the code or developing with an IDE. By helping with this effort, you can learn a lot about Drupal 8 APIs and help with the upgrade path through documenting a better-defined API surface.

Also, help me help sprinters!

I'll be in the Montréal sprint room all four days of the camp to work with potential contributors and show them how to help with these tasks, but I could use some help myself. If you have experience with Drupal 8 (even a little) or have past experience sprinting on major triage or mentoring at Drupal events, please ping me. Helping others is an especially important way to contribute back. On that note, many thanks to camp organizers for making these sprints possible.

À jeudi! See you at the camp!

Thanks to Gábor Hojtsy for help with this post.

Categories: Drupal

Commerce Images (commerce_images)

New Drupal Modules - 13 June 2017 - 9:40am

Create an image management module for managing commerce product variation images easily. The module provides an easy-to-use interface that lets you select which images get displayed with which SKUs.

Categories: Drupal

Social Feed Aggregator

New Drupal Modules - 13 June 2017 - 9:12am

A Drupal 8 module that allows Facebook, Twitter and Instagram posts to be pulled into a Social Post content type, on a scheduled basis.

Categories: Drupal

View Mode Theme Tools

New Drupal Modules - 13 June 2017 - 8:36am

This module provides some front-end tools for node view mode display:

Categories: Drupal

CTools Datetime Context

New Drupal Modules - 13 June 2017 - 7:23am

By default CTools does not have support to create datetime context objects in page manager. This module brings functionality to bring datetime context in page manager.

It detects date types defined in site and provides conversion methods for each of the date types. So, datetime object can be displayed in various date time formats.

Categories: Drupal

IMCE Rename (D8)

New Drupal Modules - 13 June 2017 - 6:47am

Module adds functionality renaming images from user interface of the IMCE file browser.

Plans for the future

Adds functionality renaming folders.

Related module
Categories: Drupal

Sooper Drupal Themes: Drupal 8: My Experience Crossing The Chasm With SooperThemes

Planet Drupal - 13 June 2017 - 5:54am

Drupal 8 adoption has been very slow, and many people have been putting it off. Some even gave up on Drupal because of D8's (perceived) complexity, focussing their career or hobby on easier CMS software. The past 3 months I've been fully engaged in embracing Drupal 8 and moving my premium Drupal themes along with the supporting ecosystem of modules, installation profiles, and infrastructure to Drupal 8! Going forward we will develop and maintain our products on both Drupal 7 and Drupal 8. 

It's been an interesting but also difficult journey and I'm writing to tell other Drupal professionals (and hobbyists) about my experience. I divided this long read into several chapters so you can skip to whichever topics you care about most. If this topic is important to you, please do comment and share your thoughts and experience!

Theming: Easier and Better But Completely New

Drupal 8 uses a new templating system for theming called Twig. While skeptical at first about having to learn a new language, I've grown to like Twig a lot... but to be very frank I would have been totally OK with keeping PHPTemplate in Drupal 8. It's what I've been using for 10 years and it's what I know. My Drupal 7 theme is full of preprocessing, custom features, and integrations with certain modules, and it's all coded in PHP. The transition to Twig means there is a huge amount of work for me to not just convert templates but also re-architect all the logic and features in the theme. I'll say that Twig works great and has a bright future but I'll also say that I can empathize with all the Drupal themers who are unhappy about having to learn a whole new way of working.

Theme Settings

If you develop base themes or premium themes like I do I have some good news as well: Theme Settings are largely implemented the same way. For me this means that many hundreds of lines of FAPI code for the 200+ theme settings in my flagship Glazed Theme can be copied and pasted into the Drupal 8 codebase and 80% of the form generating code just works. Of course the code that reads the theme settings still has to be ported from PHPTemplate, preprocessing and custom PHP to use Twig and Drupal 8's APIs. 

Logic Inside Twig Templates

The most confusing thing when starting out with Twig was that all logic for printing classes happens right inside the Twig template. For years I've been telling people to use preprocess functions for any logic, whether it be if/else or some code to retrieve a field value. In Twig any logic related to printing template code (that includes classes and other attributes) goes right into the twig template. I'm not yet entirely happy about have a lot of logic in my template files. Then again I can also imagine that to the unitiated the Drupal 7 architecture with classes being added in preprocess, or process functions that can be in multiple locations could be even more confusing.

To show you what I mean here is an excerpt of my html.html.twig template:

{% set html_classes = [ theme.settings.sticky_footer and not theme.settings.boxed_layout ? 'html--glazed-sticky-footer', ] %} {% set body_classes = [ 'html', logged_in ? 'user-logged-in', not root_path ? 'path-frontpage' : 'path-' ~ root_path|clean_class, node_type ? 'page-node-type-' ~ node_type|clean_class, db_offline ? 'db-offline', theme.settings.navbar_position ? 'navbar-is-' ~ theme.settings.navbar_position, theme.has_glyphicons ? 'has-glyphicons', theme.settings.header_position ? 'body--glazed-header-side' : 'body--glazed-header-top', not theme.settings.header_position and not theme.settings.header_style == 'overlay' ? 'body--glazed-header-not-overlay', not theme.settings.header_position and not theme.settings.header_style == 'overlay' ? 'body--glazed-header-' ~ theme.settings.header_style, not theme.settings.header_position and not theme.settings.header_top_sticky and theme.settings.header_top_fixed ? 'body--glazed-header-fixed', ] %} <!DOCTYPE html> <html {{ html_attributes.addClass(html_classes) }}>   <head>     <head-placeholder token="{{ placeholder_token|raw }}">     <title>{{ head_title|safe_join(' | ') }}</title>     <css-placeholder token="{{ placeholder_token|raw }}">     <js-placeholder token="{{ placeholder_token|raw }}">   </head>   <body{{ attributes.addClass(body_classes) }}>{{>

Some templates, like my menu--main.html.twig template that is responsible for rendering dropdown menus contain more advanced logic, including a powerful Twig tool called a  macro. The ratio of markup to logic is so low in this template that it kind of seems to defeat the purpose of having a templating system. Then again, if I look at the equivalent of PHP code I've had to write in its D7 counterpart it's equally cumbersome.  

Despite my reservations about twig, looking back at the work I've done so far in porting my theme to Drupal 8 (it's about 75% done) I'm creating a more maintainable, better product. And that's what Drupal 8 is all about. There's some pain in migrating all your work but in return you get what I believe is a more solid and maintainable theme.

Site Building: Pretty much the same

For a CMS that was basically built differently from the ground up, the authoring and site building experience is surprisingly similar to Drupal 7. You're still going through the same steps and forms to create content types, taxonomies, views, nodes etc. This is because the idea of Drupal as a flexible and powerful CMS has remained the same. For Drupal 7 users who didn't do much coding before, not much will change when upgrading to Drupal 8. Without investing at all in learning new things you can hit the ground running and install a nice Drupal 8 theme or distribution and it's business as usual.

Module Development: Definitely harder

Building Drupal 8 modules is not rocket science. It's just that there is a lot to learn before you're fluent at it. New APIs, more complicated object oriented architecture, services and plugins. The learning curve is steeper and higher than ever. However, if you start small, read the docs, and copy code from the examples module it's doable. The learning process very much reminds me of my first experience building my very first Drupal (5.x) module.

This is why I decided that building our most complex Drupal 8 modules should be handled by experienced Drupal 8 experts and not me. While I started upgrading some tiny modules as well as our theme I contracted Ivan (Chi on d.o.) and Jay Friendly (Jaypan on d.o.) to build the SooperThemes Portfolio and Glazed Drag and Drop Builder modules... completely written from the ground up for Drupal 8's architecture. Without their help there's no way I would have upgraded these modules myself without first spending at least 2 months learning Object Oriented Programming and the inner workings of Drupal 8. If anyone is looking to consult about Drupal 8 upgrade work I can highly recommend both Ivan and Jay. Jay is currently writing a book on Drupal 8 development that is targeted at Drupal 7 veterans as well as completely new users.

Development has been in full swing for the past 2-3 months and it has been the most intense and sometimes stressful time in my years building SooperThemes products. All of our products are now almost finished but still being tested and refined. It has been a great learning experience but also a great lesson in technical debt and the reality of Drupal 8's complex architecture. For me personally with my background in theming, design, and marketing I feel intimidated by the complexity introduced by Drupal 8. Conversely I feel that my customers will have more easy to use, solid, reliable and performant website thanks to Drupal 8. Luckily for many of my customers the whole point of my products is that you can build and customize everything without coding, using our Drag and Drop tools and extensive theme settings. 

Plugins, Services, Controllers, and Schema Metadata

That is a list of some of the software architecture concepts I've had to get acquinted with in the short time of 2 months. I can't say that I've learned these concepts just yet. In Drupal 7 understanding the hook system and Forms API could really get you a long way building even very large Drupal websites. In Drupal 8 not so much.

Before I started feeling like I'm on a learning curve, I ran into a wall. Drupal 8 really demands you delve deeper into software architecture than before. It's hard but the beauty of the new system is that as you're learning Drupal you're also learning Symphony and proper Object Oriented Programming design patterns. Those who can make the neccesary investment of time and energy will come out of it with skills that are valuable beyond the Drupal ecosystem.

Installation Profiles: Similar But Better

Installation profiles are a critically important part of our business at SooperThemes. We don't just sell themes, we develop, support, and maintain all the Drupal code that brings our designs to life. For our customers this means they can download a turn-key installation profile that contains their selection of designs, features, and demo content.

For us this means we maintain a ton of configuration, demo content, and modules, and wrap it all into installation profiles. We even provide an interface to generate customized installation profiles and install them on your hosting fully automatically. My experience so far with Drupal 8 installation profiles has been great. 

Demo Content

A notable improvement is the great support for demo content in Drupal 8 with help of the Default Content module. In Drupal 7 the go-to module was UUID Features. Over the past years I've spent many hours fixing bugs, implementing file support, and patching up poor support for referenced entities and menu links in Drupal 7's UUID Features code. 

The Drupal 8 Default Content module is still in alpha and if you're doing a lot of default content work you still might need to hit the issue queue and download (or contribute) a little patch but this module already feels more stable than the UUID Features suite. D8 and Default Content also import content faster, allowing even the lowest of low-end hosting to install our bulkier demo installation profiles.

Configuration 

I've read that Features is still a thing in Drupal 8 but I've not yet found the need to try it out. Whereas previously we used Features to package all our CMS components into modules this is now done with Drupal core's configuration system. It's working well so far. Automatic exporting of configuration and dependencies into modules is done using drush, and we can now split optional and required configuration which is also great for components that include lots of views that add value but are not indispensable. I did experience some quirks with optional configuration not being installed during the profile's installation process even while dependencies were certainly met.  

Media: Work In Progress

It took many years for the Media module to have a stable (2.x) release in Drupal 7. Drupal 7 Media works great and  it handles drop-in file uploads, multi-file uploads and various media gallery browsing features excellently. In Drupal 8 great work is being done to bring Media features into core. I'm a big fan of the initiative but I'm also concerned about how to provide provide future proof media featurs in my installation profile right now. 

Drupal 8 Entity Browser

At the moment of writing this, the successor of the Media module is Entity Browser. The module File Entity Browser (it builds on top of Entity Browser module) will give you a media library popup browser similar to the D7 media module's browser. Installing this module requires 5 modules (dropzonejs, embed, entity_browser, entity_embed, and file_browser) and 3 external libraries: dropzoneimagesloaded, and masonry. Part of the Drupal 8 media initiative is to include features similar to what the File Browser module provides in core, but in a cleaner architecture with fewer dependencies.

A module similar to File Entity Browser is Media Entity Browser and the major difference is that it uses the more flexible Media entity as opposed to the file entity. What exactly this means and how all this will be upgraded to the new Drupal 8.4 core features, I'm not sure. Therefore I decided to launch my distribution and products without image re-usability on Drupal 8.3. To protect my customers against potentially needing complex upgrade processes I'll hold off on advanced Media management until Drupal 8.4 comes out. It's planned to come out late this summer and I'm looking forward to it. 

Improvements In Documentation

This is not really a Drupal 8 improvement as much as it is a Drupal.org improvement. The quality of documentation available to day is so much better than on the day Drupal 7 came out. The new documentation page design immediately gives more credibility to the content and the content is carefully curated and better written. Even though this is not really a feature of Drupal 8 it certainly is a great benefit to those starting to learn Drupal 8 today. 

I also want to give a shout out to Drupalize.me, who are giving away free subscriptions for their premium training videos to people who have contributed on Drupal.org. Terms and details.

My Prediction: Drupal 8.4 Will Bring Up The Numbers

I see Media features as the #1 core advantage of WordPress over Drupal. Other major weaknesses of Drupal are a leaner offering of themes and niche-specific tools like portfolio plugins, drag and drop building options, and other fancy add-ons. But those can be fixed by contrib projects and through premium themes. Media is a challenge that took too long to get right in Drupal 7. It was only several months ago the Drupal 7 Media module had it's first truly stable Drupal 7 release. Thanks to this development, we can now expect to see more niche-specific add-ons for the Media module as there is a stable API to build on top on. Next week I will blog about the release of such an add-on module that SooperThemes has co-sponsored and co-developed. 

If the Drupal 8 Media Initiative is executed according to plan Drupal 8.4 will bring features to that will appeal strongly to the masses of Drupal site builders who are unable or unwilling to create custom configurations for Entity Browser. Drupal 8's more rapid emergence of a stable Media API can awaken growth of Media contrib modules that make the lives of content creators and site builder easier.

SooperThemes Drupal 8: Upgrade Status

To those who are waiting: Please be patient as we're finishing up and fine-tuning. I meant to release a public beta of some products this week but I decided it's better to focus on finishing the components that are currently <90% done. I'll re-evaluate the possibility of public beta testing  next week, and the week thereafter.

SooperThemes Products Drupal  8 Upgrade Progress  %_of_total** Glazed Theme 75% Complete 25% Glazed Drag and Drop Builder 95% Complete 25% Sooperthemes Portfolio (replacement of D7 glazed_portfolio) 90% Complete (only missing hover effect designs) 15% Glazed GridStack 95% Complete  5% Glazed Helper 75% Complete (only missing Page Design tools) 7.5% Glazed Drupal CMS Distribution (drupal.org/project/cms) 95% Complete (finetuning, future-proofing) 10% Demo Content and Installation Profiles 0/15 Completed (pending completion of above) 5% Product infrastructure* 50% Complete 7.5%

* demo sites, trysooperthemes.com, automatic installation profile testing and provisioning, support forum, etc. The kind of stuff you don't think about before starting a big Drupal 8 upgrade project.

** Estimated proportion to the total amount of work of all items in the table

Categories: Drupal

Workflow Assignee

New Drupal Modules - 13 June 2017 - 4:56am
Categories: Drupal

Pages

Subscribe to As If Productions aggregator - Drupal