we built it in Drupal 8. FFW made this decision because of our commitment to Drupal, since Drupal 8 represents an important next step in the evolution of digital experience delivery.
we built it in Drupal 8. FFW made this decision because of our commitment to Drupal, since Drupal 8 represents an important next step in the evolution of digital experience delivery.
A centralized place for tracking the porting status of contributed projects (modules, themes, distributions). This project consists of issues that show the D8 porting status of other projects. (Inception!) Check out this issue queue in a kanban board on ContribKanban.com (thanks, @mglaman!)
A centralized place for tracking the porting status of contributed projects (modules, themes, distributions). This project consists of issues that show the D8 porting status of other projects. (Inception!) Check out this issue queue in a kanban board on ContribKanban.com (thanks, @mglaman!)
This is a "meta" project that holds issues that represent the porting status various projects, and allows us to work as a unified Drupal community to combine our collective observational super powers into one data set that can be used by anyone considering building on Drupal 8. - See more at: https://dev.acquia.com/blog/announcing-the-drupal-8-contrib-porting-tracker-project-on-drupalorg/01/10/2015/6896#sthash.6uWSmSUc.dpuf
This is a "meta" project that holds issues that represent the porting status various projects, and allows us to work as a unified Drupal community to combine our collective observational super powers into one data set that can be used by anyone considering building on Drupal 8. - See more at: https://dev.acquia.com/blog/announcing-the-drupal-8-contrib-porting-tracker-project-on-drupalorg/01/10/2015/6896#sthash.6uWSmSUc.dpuf
Probably, each Drupal developer has been there: no good contrib resulted in custom solution (doesn’t matter if it’s a module, a theme or distribution). The problem here is that a lot of drupalista stop there. Let’s contribute After a couple of days, I decided to publish it on drupal.org! 1. Every contribution counts. 2. It's impossible to predict all the use cases. 3. A successful module must integrate with all the most popular Drupal contribs 4. Tests are essential for a happy life.
This is a simple module intends to help people use drupal to easily create valid xml podcast feed(s)for iTunes. As the only thing podcasters should worry about is making their podcast(s) and not messing with code. Features: site admin or permission given trusted users the ability to easily create podcast(s) with out having to touch a line of xml. Import old iTunes feed items for ease of drupal podcast migration. Create and manage new podcast items quickly reusing elements.
Drupal module to pull data from Instagram based on user or hashtag. Includes moderator settings, integrates with Drupal cron, and provides a block to display the latest photos. This module can provide you detailed control and configuration over embedding social feeds from Instagram in your site. Many services offer embedded HTML or Javascript snippets you can paste into blocks that will display feed content, but this module gives you control over how that content is themed, and also provides SEO benefits because it is directly served inside the page when search engines crawl your site.
Provides 'Masonry' style layouts as an option for rendering the contents of panel panes. Masonry rendering will re-pack panes in your panel to minimize vertical space and provide column-like appearance while the items are still in natural (horizontal) order on the page. With "Responsive" layouts happening everywhere, the Panels approach of locking everything into a grid can provide a bit of a dilemma, because your column count is pretty static. But the Panels approach of letting an editor drop elements into a page in certain zones still works well in some cases.