Features: A better way to package stuff in Drupal
2 likes2,437 views
Features is a Drupal module that enables configuration from the database, like content types, views, and contexts, to be packaged into modules called "Features". Features consist of generated code that can be version controlled and deployed between environments. Features allow changes to be managed like code instead of only in the database. When a Feature is enabled, all its dependencies are installed as well. If the Feature is later changed, it becomes overridden and the developer must choose whether to revert or update the code.
1 of 26
Downloaded 11 times
Ad
Recommended
WordPress development checklist
WordPress development checklistBinh Quan Duc This document outlines goals, roles, and checklists for developing a WordPress website with a focus on security, performance, and quality. The goals include highest security, safe deployment, high PageSpeed scores, control, backups/restorability, and quality proof. Roles include HTML/CSS developer, WordPress developer, and CM/DevOps. Checklists cover tasks for the HTML/CSS team like image optimization and the WordPress developer like using Docker, caching, and deployment best practices. The CM/DevOps checklist addresses asset compression, caching, backups, file permissions, and image optimization.
Improve your web dev workflow in Visual Studio
Improve your web dev workflow in Visual StudioDavid Paquette This document discusses different options for web development workflows in Visual Studio, including using runtime optimizations, Visual Studio plugins, and task runners. It provides examples of specific plugins and task runners like Bundler and Minifier, Web Compiler, Web Essentials, Gulp, and Bower. The document analyzes the pros and cons of each approach and recommends the best option depending on a project's complexity, build integration needs, and optimization goals.
002. Working with Webpack
002. Working with WebpackBinh Quan Duc Webpack is a module bundler that can bundle JavaScript files and their associated modules and dependencies. It provides features like dependency graph, aliasing, loaders to preprocess files, plugins to customize functionality, and code splitting to optimize bundles. Webpack can also be used to polyfill features and fetch resources. While powerful, Webpack can be difficult for beginners due to its complexity. The document provides an overview of Webpack's key features but is poorly formatted and hard to follow, especially for newcomers.
LESS is More (ChiHTML5 Meetup June 2016)
LESS is More (ChiHTML5 Meetup June 2016)Sara Laupp The document discusses CSS preprocessors like LESS and SASS. It explains that preprocessors allow you to write CSS in a more maintainable, programmatic way using features like variables, mixins, nested rules, and functions. These features make CSS code more organized, reusable, and reduce duplication. The document provides examples of how to use these features in LESS and recommends LESS for projects using Node.js and frameworks with built-in LESS support.
Site Building Checklist DrupalCamp Ottawa
Site Building Checklist DrupalCamp OttawaSuzanne Dergacheva A checklist for site builders: things to do after you've built out your content types and views and before you show the site to your client or deploy it on production. See the list at http://bit.ly/drupal-checklist.
A Smooth Transition to HTML5
A Smooth Transition to HTML5Chris Bannon How difficult is it to port Flex and Silverlight applications to HTML5? That is the question we hear every day at ComponentOne. Instead of speculating about it, we decided to sit down and try it. Today we will discuss the process and tools we used when doing so. The approach we took was to use the MVVM pattern (from Silverlight) when developing the HTML5/JavaScript version. By choosing this method we were able to port our data access and UI layers quite easily. Our developers were able to minimize the cost of learning new paradigms in this migration by reusing most of their knowledge. What we ended up with was nearly identical applications in Silverlight and HTML5. Come learn how you can smoothly transition to HTML5!
Bootstrapping angular js with bower grunt yeoman
Bootstrapping angular js with bower grunt yeomanMakarand Bhatambarekar The document discusses how to bootstrap Angular applications using Yeoman, Bower, and Grunt. It provides an overview of each tool, including that Yeoman generates project structure and templates, Bower manages frontend package dependencies, and Grunt automates tasks. The document then demonstrates setting up a sample project with these tools, installing dependencies, running development servers, and deploying the built code.
Single page application and Framework
Single page application and FrameworkChandrasekar G The document discusses single page applications (SPAs) and frameworks. It defines an SPA as a web app that loads a single HTML page and dynamically updates it as the user interacts. This provides a desktop-like experience within web pages. Frameworks help with development by providing libraries for routing, templates, controllers, models, views and more. They also include tools for linting, transpiling, bundling, preprocessing and more. The document examines different framework architectures like MVC, MVVM and MVP and notes that frameworks should have a small size, be straightforward and support the needs of the specific application.
Single Page Application (SPA) using AngularJS
Single Page Application (SPA) using AngularJSM R Rony Single Page Application (SPA) using angular js. Also have some relative sample codes.
if u need then just mail me at [email protected]
Single page App
Single page AppGaurav Gawande Web applications have evolved over time from traditional multi-page applications that required full page reloads to modern single-page applications (SPAs) that function more like desktop apps. SPAs are built with JavaScript frameworks on the client-side and use Ajax techniques to update parts of the page dynamically without reloading. This provides a more fluid user experience compared to older request-response models. SPAs can improve performance by reducing load times, transferring less data, distributing load to clients, and enabling easier caching compared to traditional server-side web apps.
Fork CMS
Fork CMSLester Lievens Fork CMS is a user-friendly content management system built on top of existing applications. It aims to make developers, designers, bosses, and clients happy. It uses a modular structure with pages, modules, templates, and themes. Key features include SEO, search, translations, forms, AJAX, cronjobs, caching, and core modules. The documentation is a work in progress. Users are encouraged to participate on GitHub, IRC, the forum, and the bug tracker.
A Gentle Introduction to Blazor
A Gentle Introduction to BlazorJose Javier Columbie What's behind the hype about Blazor? Is Javascript dead? Another Silverlight? If you are a .Net developer you will love Blazor: the new framework to build web/desktop and even mobile apps with C#. In this talk we will cover Blazor hosting models, Javascript Interop, Components, and a lot more.
Free Online SharePoint Framework Webinar
Free Online SharePoint Framework WebinarManoj Mittal Free Online Webinar @ SharePoint Framework Series Part-1
In this webinar, you can learn about SPFX development with different CDN options.
Lap Around ASP.NET MVC 5
Lap Around ASP.NET MVC 5Lohith Goudagere Nagaraj This document outlines an agenda for a presentation on new features in ASP.NET MVC 5 including Bootstrap, scaffolding, ASP.NET Identity, attribute routing, and authentication filters. The presentation provides demos of each new feature, with the goal of giving an overview of ASP.NET MVC 5 and how it can be used to build scalable, standards-based web applications.
Moving from PHP to a nodejs full stack CMS
Moving from PHP to a nodejs full stack CMSMake & Build This document discusses moving a content management system (CMS) from PHP to a Node.js full stack using the KeystoneJS framework. It describes how the author migrated an existing WordPress site to KeystoneJS in 2 weeks, improving performance by 200%. Key aspects covered include the KeystoneJS data models, controllers, views, and administration interface. It also outlines additional features like customizing the admin UI with React, adding themes, and deployment options.
Single page applications
Single page applicationsDiego Cardozo This document provides an overview of single page applications (SPAs), including their motivation, introduction, examples, architecture, advantages and disadvantages, tools, and a demo. SPAs aim to improve user experience by only loading necessary content instead of entire pages when navigating a site. This reduces load times compared to traditional multi-page applications. The document discusses tools like Knockout.js that can be used to build SPAs and notes that server-side code moves to exposing RESTful APIs while client-side code handles navigation and UI logic. It concludes with advertising a demo of an SPA built with John Papa's Hot Towel template to further illustrate SPA concepts.
Bundle Splitting in Volto
Bundle Splitting in VoltoPloneFoundation Nilesh Gulia, https://2020.ploneconf.org/speakers/nilesh-gulia
As an application scales, we need to make adjustments in Javascript bundle which gives a breathing space when it comes to loading massive client apps.
We cannot maintain a single javascript bundle as the application grows, it can hinder website performance in various cases.
A few different approaches we can take when it comes to bundle splitting JavaScript.
Dynamic code splitting: Dynamic code splitting adds the ability to point out the fields/components which we want to lazy-load i.e load on demand and split out in a separate bundle. This is opposite to statically load where we bundle out dependencies into a single file during build time.
This talk demonstrates how we recently inculcated and leveraged `loadable-components` into Volto core to load dynamic chunks while maintaining server side rendering.
https://2020.ploneconf.org/talks/bundle-splitting-in-volto
Codegen2021 blazor mobile
Codegen2021 blazor mobileJose Javier Columbie This document summarizes the evolution of Blazor and Xamarin Forms (now known as Maui) for building mobile, web, and desktop applications with C#. It discusses the differences between Blazor Server and Blazor WebAssembly models, how to create reusable components, access native features via JavaScript interop, and experimental support for building mobile apps using Blazor through Mobile Blazor Bindings. It also provides an overview of upcoming features in .NET 6 to improve the Blazor experience.
Rise of the responsive single page application
Rise of the responsive single page applicationOren Shatken The document discusses the rise of responsive single page applications. It defines responsive design as building websites that detect users' device and screen size and dynamically adjust the layout accordingly. It advocates for responsive design over separate mobile sites because it provides a better user experience across devices, improves SEO through a single URL structure, and streamlines development and maintenance with one codebase. The document also outlines best practices for developing responsive applications using technologies like AngularJS, Grunt, and Yeoman to automate testing and improve workflow efficiency.
ASP.NET 5 Overview
ASP.NET 5 OverviewShahed Chowdhuri This document discusses the future of web apps using ASP.NET 5.0 and .NET Core. It introduces .NET Core as a cross-platform version of .NET that can be deployed with apps. ASP.NET 5.0 unifies MVC, Web API, and Web Pages and allows editing code and seeing live updates in the browser. It also supports NuGet packages, task runners like Grunt and Gulp, and GitHub deployment.
Building great spa’s with angular js, asp.net mvc and webapi
Building great spa’s with angular js, asp.net mvc and webapiMaurice De Beijer [MVP] This document discusses building single page applications (SPAs) using AngularJS, ASP.NET MVC, and ASP.NET WebAPI. It introduces AngularJS as a powerful JavaScript framework for building SPAs and CRUD applications. It notes that while AngularJS makes applications easy to build, large JavaScript apps can be hard to maintain. It then introduces ASP.NET WebAPI for building RESTful APIs and ASP.NET MVC as a server-side framework. It argues that combining AngularJS, WebAPI and MVC takes the best of both worlds, allowing structure from MVC while offloading UI tasks to AngularJS for performance. The document contains code demos of each technology and how they can work
Host, deploy & scale Blazor Server Apps
Host, deploy & scale Blazor Server AppsJose Javier Columbie The document discusses hosting and scaling ASP.NET Core Blazor Server applications using SignalR and the Azure SignalR Service. It covers how SignalR enables real-time functionality using techniques like WebSockets, Server-Sent Events and long polling. It also discusses scaling options for SignalR like using sticky sessions, TCP connections and a Redis backplane. The Azure SignalR Service is presented as a scalable option with pricing information. A demo and bonus content on CircuitHandler are also mentioned.
Introduction To Single Page Application
Introduction To Single Page ApplicationKMS Technology This document provides an introduction to single page applications (SPAs). It begins with an overview of traditional websites, which have multiple pages and server-based rendering. The evolution section discusses how modern browsers, JavaScript, and HTML5 have enabled a more app-like user experience with SPAs. SPAs are defined as web apps that load a single HTML page and use AJAX and JavaScript for fluid interactions without page reloads. Benefits include faster loading and improved user experience. Challenges of SPAs include search engine optimization, initial slow loading, and maintaining browser history. The document concludes with a question and answer section.
What the heck are Features and why do I need them for my Drupal website?
What the heck are Features and why do I need them for my Drupal website?Bryan Mayjor Presented at the NETC 2012 conference
http://www.netc2012.org/conference/schedule/may-29-2012/session-5/30-what-the-heck-are-features
Shift Remote: JS - Javascript Build Tools: Past & Beyond - Shedrack Akintayo 
Shift Remote: JS - Javascript Build Tools: Past & Beyond - Shedrack Akintayo Shift Conference In this talk, I'd go through the Evolution of JavaScript build tools, their features of most javascript build tools and what we should be expecting in the future from build tools.
Single page application
Single page applicationArthur Fung This document discusses single page applications (SPAs) and provides an overview of what SPAs are and their advantages compared to traditional websites. It defines SPAs as web applications that fit on a single web page and provide a more desktop-like user experience through features like fluid page transitions without reloads. The document outlines how SPAs move more of the application logic to the client, fetch data on demand, and support features like back/forward buttons and offline use. Examples of SPAs include Gmail and merchant locators.
WordPress as a Headless CMS - Bronson Quick
WordPress as a Headless CMS - Bronson QuickWordCamp Sydney The WP REST API infrastructure was introduced in WordPress 4.4. The introduction of this infrastructure allows WordPress developers to now use WordPress as a headless CMS. A headless CMS has its frontend component (the head) stripped and removed from its backend, and what remains is a backend delivering content via an API. Some common use cases for headless CMS are as follows:
Serving data to other web applications
Mobile Apps
Websites and web apps built with MVC-style JavaScript frameworks
Developers can install the WP REST API plugin to expose endpoints for WordPress for posts, pages, media and users. Developers can also extend the WordPress core REST infrastructure to register their own endpoints for custom post types and WordPress options.
The WP REST API plugin will expose database content via JSON. This data can be used by developers to create sites using JavaScript frameworks such as React and also use the JSON data in mobile apps.
Bronson will explain and demonstrate how you can use WordPress and the WP REST API to create a website that uses React on the frontend and WordPress on the backend as a headless CMS.
Learn VBScript – Part 1 of 4
Learn VBScript – Part 1 of 4Srinimf-Slides This document provides an introduction to VBScript, including what it is, its usage, where it can be executed, and how to integrate VBScript code into HTML pages. VBScript is a scripting language designed to automate web page activities through the use of scripts. It requires an execution host like a web browser to run. Common uses of VBScript include form validation, animation effects, and displaying messages. VBScript code can be executed in Internet Explorer, Windows Script Host, IIS, Outlook Express, and the Windows Script Console. Code is inserted into HTML pages using <SCRIPT> tags and can be placed in the head or body section.
Drupal Presentation for CapitalCamp 2011: Features Driven Development
Drupal Presentation for CapitalCamp 2011: Features Driven DevelopmentMediacurrent This document provides an overview of feature driven development in Drupal. It discusses how features allow encapsulation of items like views, content types, and configurations to make deployment and version control easier. It provides instructions for creating basic features and exporting non-exportable items. Feature driven development is presented as creating a feature module for each content type along with related components. Examples of real world feature lists are shown to demonstrate how features are used to package common site elements.
Intro to Features Module on Drupal
Intro to Features Module on DrupalAidan Foster The document introduces the Drupal module "Features" which allows users to export common Drupal configurations like content types, views, and permissions into reusable modules. Features can be used to share configurations between projects, kickstart new projects, and improve collaboration workflows. It also discusses setting up Features and making a sample feature as a demonstration.
More Related Content
What's hot (20)
Single Page Application (SPA) using AngularJS
Single Page Application (SPA) using AngularJSM R Rony Single Page Application (SPA) using angular js. Also have some relative sample codes.
if u need then just mail me at [email protected]
Single page App
Single page AppGaurav Gawande Web applications have evolved over time from traditional multi-page applications that required full page reloads to modern single-page applications (SPAs) that function more like desktop apps. SPAs are built with JavaScript frameworks on the client-side and use Ajax techniques to update parts of the page dynamically without reloading. This provides a more fluid user experience compared to older request-response models. SPAs can improve performance by reducing load times, transferring less data, distributing load to clients, and enabling easier caching compared to traditional server-side web apps.
Fork CMS
Fork CMSLester Lievens Fork CMS is a user-friendly content management system built on top of existing applications. It aims to make developers, designers, bosses, and clients happy. It uses a modular structure with pages, modules, templates, and themes. Key features include SEO, search, translations, forms, AJAX, cronjobs, caching, and core modules. The documentation is a work in progress. Users are encouraged to participate on GitHub, IRC, the forum, and the bug tracker.
A Gentle Introduction to Blazor
A Gentle Introduction to BlazorJose Javier Columbie What's behind the hype about Blazor? Is Javascript dead? Another Silverlight? If you are a .Net developer you will love Blazor: the new framework to build web/desktop and even mobile apps with C#. In this talk we will cover Blazor hosting models, Javascript Interop, Components, and a lot more.
Free Online SharePoint Framework Webinar
Free Online SharePoint Framework WebinarManoj Mittal Free Online Webinar @ SharePoint Framework Series Part-1
In this webinar, you can learn about SPFX development with different CDN options.
Lap Around ASP.NET MVC 5
Lap Around ASP.NET MVC 5Lohith Goudagere Nagaraj This document outlines an agenda for a presentation on new features in ASP.NET MVC 5 including Bootstrap, scaffolding, ASP.NET Identity, attribute routing, and authentication filters. The presentation provides demos of each new feature, with the goal of giving an overview of ASP.NET MVC 5 and how it can be used to build scalable, standards-based web applications.
Moving from PHP to a nodejs full stack CMS
Moving from PHP to a nodejs full stack CMSMake & Build This document discusses moving a content management system (CMS) from PHP to a Node.js full stack using the KeystoneJS framework. It describes how the author migrated an existing WordPress site to KeystoneJS in 2 weeks, improving performance by 200%. Key aspects covered include the KeystoneJS data models, controllers, views, and administration interface. It also outlines additional features like customizing the admin UI with React, adding themes, and deployment options.
Single page applications
Single page applicationsDiego Cardozo This document provides an overview of single page applications (SPAs), including their motivation, introduction, examples, architecture, advantages and disadvantages, tools, and a demo. SPAs aim to improve user experience by only loading necessary content instead of entire pages when navigating a site. This reduces load times compared to traditional multi-page applications. The document discusses tools like Knockout.js that can be used to build SPAs and notes that server-side code moves to exposing RESTful APIs while client-side code handles navigation and UI logic. It concludes with advertising a demo of an SPA built with John Papa's Hot Towel template to further illustrate SPA concepts.
Bundle Splitting in Volto
Bundle Splitting in VoltoPloneFoundation Nilesh Gulia, https://2020.ploneconf.org/speakers/nilesh-gulia
As an application scales, we need to make adjustments in Javascript bundle which gives a breathing space when it comes to loading massive client apps.
We cannot maintain a single javascript bundle as the application grows, it can hinder website performance in various cases.
A few different approaches we can take when it comes to bundle splitting JavaScript.
Dynamic code splitting: Dynamic code splitting adds the ability to point out the fields/components which we want to lazy-load i.e load on demand and split out in a separate bundle. This is opposite to statically load where we bundle out dependencies into a single file during build time.
This talk demonstrates how we recently inculcated and leveraged `loadable-components` into Volto core to load dynamic chunks while maintaining server side rendering.
https://2020.ploneconf.org/talks/bundle-splitting-in-volto
Codegen2021 blazor mobile
Codegen2021 blazor mobileJose Javier Columbie This document summarizes the evolution of Blazor and Xamarin Forms (now known as Maui) for building mobile, web, and desktop applications with C#. It discusses the differences between Blazor Server and Blazor WebAssembly models, how to create reusable components, access native features via JavaScript interop, and experimental support for building mobile apps using Blazor through Mobile Blazor Bindings. It also provides an overview of upcoming features in .NET 6 to improve the Blazor experience.
Rise of the responsive single page application
Rise of the responsive single page applicationOren Shatken The document discusses the rise of responsive single page applications. It defines responsive design as building websites that detect users' device and screen size and dynamically adjust the layout accordingly. It advocates for responsive design over separate mobile sites because it provides a better user experience across devices, improves SEO through a single URL structure, and streamlines development and maintenance with one codebase. The document also outlines best practices for developing responsive applications using technologies like AngularJS, Grunt, and Yeoman to automate testing and improve workflow efficiency.
ASP.NET 5 Overview
ASP.NET 5 OverviewShahed Chowdhuri This document discusses the future of web apps using ASP.NET 5.0 and .NET Core. It introduces .NET Core as a cross-platform version of .NET that can be deployed with apps. ASP.NET 5.0 unifies MVC, Web API, and Web Pages and allows editing code and seeing live updates in the browser. It also supports NuGet packages, task runners like Grunt and Gulp, and GitHub deployment.
Building great spa’s with angular js, asp.net mvc and webapi
Building great spa’s with angular js, asp.net mvc and webapiMaurice De Beijer [MVP] This document discusses building single page applications (SPAs) using AngularJS, ASP.NET MVC, and ASP.NET WebAPI. It introduces AngularJS as a powerful JavaScript framework for building SPAs and CRUD applications. It notes that while AngularJS makes applications easy to build, large JavaScript apps can be hard to maintain. It then introduces ASP.NET WebAPI for building RESTful APIs and ASP.NET MVC as a server-side framework. It argues that combining AngularJS, WebAPI and MVC takes the best of both worlds, allowing structure from MVC while offloading UI tasks to AngularJS for performance. The document contains code demos of each technology and how they can work
Host, deploy & scale Blazor Server Apps
Host, deploy & scale Blazor Server AppsJose Javier Columbie The document discusses hosting and scaling ASP.NET Core Blazor Server applications using SignalR and the Azure SignalR Service. It covers how SignalR enables real-time functionality using techniques like WebSockets, Server-Sent Events and long polling. It also discusses scaling options for SignalR like using sticky sessions, TCP connections and a Redis backplane. The Azure SignalR Service is presented as a scalable option with pricing information. A demo and bonus content on CircuitHandler are also mentioned.
Introduction To Single Page Application
Introduction To Single Page ApplicationKMS Technology This document provides an introduction to single page applications (SPAs). It begins with an overview of traditional websites, which have multiple pages and server-based rendering. The evolution section discusses how modern browsers, JavaScript, and HTML5 have enabled a more app-like user experience with SPAs. SPAs are defined as web apps that load a single HTML page and use AJAX and JavaScript for fluid interactions without page reloads. Benefits include faster loading and improved user experience. Challenges of SPAs include search engine optimization, initial slow loading, and maintaining browser history. The document concludes with a question and answer section.
What the heck are Features and why do I need them for my Drupal website?
What the heck are Features and why do I need them for my Drupal website?Bryan Mayjor Presented at the NETC 2012 conference
http://www.netc2012.org/conference/schedule/may-29-2012/session-5/30-what-the-heck-are-features
Shift Remote: JS - Javascript Build Tools: Past & Beyond - Shedrack Akintayo
Shift Remote: JS - Javascript Build Tools: Past & Beyond - Shedrack Akintayo Shift Conference In this talk, I'd go through the Evolution of JavaScript build tools, their features of most javascript build tools and what we should be expecting in the future from build tools.
Single page application
Single page applicationArthur Fung This document discusses single page applications (SPAs) and provides an overview of what SPAs are and their advantages compared to traditional websites. It defines SPAs as web applications that fit on a single web page and provide a more desktop-like user experience through features like fluid page transitions without reloads. The document outlines how SPAs move more of the application logic to the client, fetch data on demand, and support features like back/forward buttons and offline use. Examples of SPAs include Gmail and merchant locators.
WordPress as a Headless CMS - Bronson Quick
WordPress as a Headless CMS - Bronson QuickWordCamp Sydney The WP REST API infrastructure was introduced in WordPress 4.4. The introduction of this infrastructure allows WordPress developers to now use WordPress as a headless CMS. A headless CMS has its frontend component (the head) stripped and removed from its backend, and what remains is a backend delivering content via an API. Some common use cases for headless CMS are as follows:
Serving data to other web applications
Mobile Apps
Websites and web apps built with MVC-style JavaScript frameworks
Developers can install the WP REST API plugin to expose endpoints for WordPress for posts, pages, media and users. Developers can also extend the WordPress core REST infrastructure to register their own endpoints for custom post types and WordPress options.
The WP REST API plugin will expose database content via JSON. This data can be used by developers to create sites using JavaScript frameworks such as React and also use the JSON data in mobile apps.
Bronson will explain and demonstrate how you can use WordPress and the WP REST API to create a website that uses React on the frontend and WordPress on the backend as a headless CMS.
Learn VBScript – Part 1 of 4
Learn VBScript – Part 1 of 4Srinimf-Slides This document provides an introduction to VBScript, including what it is, its usage, where it can be executed, and how to integrate VBScript code into HTML pages. VBScript is a scripting language designed to automate web page activities through the use of scripts. It requires an execution host like a web browser to run. Common uses of VBScript include form validation, animation effects, and displaying messages. VBScript code can be executed in Internet Explorer, Windows Script Host, IIS, Outlook Express, and the Windows Script Console. Code is inserted into HTML pages using <SCRIPT> tags and can be placed in the head or body section.
Similar to Features: A better way to package stuff in Drupal (20)
Drupal Presentation for CapitalCamp 2011: Features Driven Development
Drupal Presentation for CapitalCamp 2011: Features Driven DevelopmentMediacurrent This document provides an overview of feature driven development in Drupal. It discusses how features allow encapsulation of items like views, content types, and configurations to make deployment and version control easier. It provides instructions for creating basic features and exporting non-exportable items. Feature driven development is presented as creating a feature module for each content type along with related components. Examples of real world feature lists are shown to demonstrate how features are used to package common site elements.
Intro to Features Module on Drupal
Intro to Features Module on DrupalAidan Foster The document introduces the Drupal module "Features" which allows users to export common Drupal configurations like content types, views, and permissions into reusable modules. Features can be used to share configurations between projects, kickstart new projects, and improve collaboration workflows. It also discusses setting up Features and making a sample feature as a demonstration.
Features everywhere 
Features everywhere Mediacurrent This document discusses feature-driven development in Drupal using the Features module. It describes how Features allows encapsulating reusable parts of a Drupal site like content types, views, and configurations into modules that can then be exported, version controlled, and shared. It provides guidance on setting up Features and creating a new feature to extract components into a reusable feature module.
Building and Deployment of Drupal sites with Features and Context
Building and Deployment of Drupal sites with Features and ContextSvilen Sabev The document summarizes a presentation about building and deploying Drupal sites using the Features and Context modules. It discusses how Features allows developers to package configurations like content types, views, and permissions into reusable modules. Context allows managing different site sections or "contexts" through conditions and reactions. The presentation provides examples of using both modules and recommends best practices for organizing configurations in Features.
Gov features
Gov featuresJeff Miccolis This document discusses using Drupal Features to capture configuration settings as code modules. Features allows distinguishing configuration from content and storing configuration in version control. It improves multi-developer workflows by reducing errors and making changes transparent. Features exports things like content types, views, and files to modules that can be shared or updated between environments.
IBM Drupal Users Group Discussion on Managing and Deploying Configuration
IBM Drupal Users Group Discussion on Managing and Deploying ConfigurationDevelopment Seed Presentation to the IBM Drupal Users Group on improving configuration management in Drupal using the Features module and exportables. This is becoming a best practice for configuration management.
10 Reasons why you should be using features for your Drupal project
10 Reasons why you should be using features for your Drupal projectWunderkraut Slides from the DrupalCon presentation: http://cph2010.drupal.org/sessions/10-reasons-why-you-should-be-using-features-your-drupal-project#
Drupal Deployment
Drupal Deploymentq0rban The Features module allows Drupal configurations like content types, views, and fields to be exported into custom modules called "features". This addresses issues with storing configurations in the variable table or custom data stores. Features exports configurations to code, creates modules for that code, monitors for discrepancies between configurations and code, and provides tools to resolve those discrepancies. Features modules are custom modules that act as "glue code" to satisfy specific use cases.
Easy Drupal Project Deployment With Features Module & Drush
Easy Drupal Project Deployment With Features Module & DrushQArea This is a presentation for webinar QArea has held about Drupal deployment as well as Features and Drush modules (http://qarea.com/articles/qarea-webinars-drupal-hit-video). There are also many useful commands and tricks & tips any developer will be able of finding in it.
Using Features
Using FeaturesAlexandru Badiu The document discusses the Features module in Drupal, which allows users to package common site functionality like views, content types, and taxonomies into reusable modules. It describes how Features exports these site elements into code that can then be installed on other sites. This helps avoid manual exporting and importing of site elements between environments and allows functionality to be easily shared and updated across sites.
Git Going w/ Git
Git Going w/ GitheyMP This document provides an introduction to using Git and version control. It explains the basic concepts and workflow of Git, including initializing and committing to a local repository, pushing changes to a remote repository, and using branches for features and releases. It also discusses how to manage Drupal configuration changes using features in Git.
Drupal Features Module by New Tech Fusion presentation
Drupal Features Module by New Tech Fusion presentationNewTechFusion Cybertech Pvt Ltd Drupal Features is one of the best module for the smart drupal developers.
It gives alot of power to developers and save huge development efforts if some feature needs to be implemented again and again in different websites.
Features & Installation Profiles
Features & Installation ProfilesDavid Watson After providing a brief summary of common pitfalls in working with Drupal (included the dreaded Dev/Test/Prod problem), this presentation illustrates the usefulness of developing with Features and Installation Profiles to create fully revisioned sites capable of one-click deployment.
Features
FeaturesGokul Nk This document discusses using Features and related modules to manage configuration in Drupal. It summarizes some of the challenges with managing configuration in databases, and how Features allows moving configuration into code. Key points covered include:
1. Features allows exporting site configuration like content types, fields, and views into reusable modules that can be version controlled and shared.
2. This separates the configuration and code from the content data in the database, making deployment and staging easier without database changes.
3. The document discusses some challenges with using Features and recommends related modules like Features Extra, Features Plumber and Features Override to address issues like simultaneous editing and overriding dependencies.
Drupal: an Overview
Drupal: an OverviewMatt Weaver This document provides an overview of the open source content management system Drupal. It describes Drupal as a flexible CMS built on PHP and modular architecture. Core features include nodes, taxonomy, views, and themes. Key terms are defined such as modules, blocks, and users/roles. The document outlines some top Drupal modules, advantages of Drupal for libraries, potential obstacles, and resources for learning more.
Blisstering drupal module development ppt v1.2
Blisstering drupal module development ppt v1.2Anil Sagar 1. Implement hook_form() to define the form structure using Form API elements like #type, #title, etc.
2. Add validation and submission handlers to validate form data and process form submission.
3. In the validation handler, validate the form data and use drupal_set_message() to display errors.
4. In the submission handler, save the form values and use drupal_set_message() to display success messages.
This allows you to create a basic configuration form, validate the submitted data, and save the configuration values on successful validation using Drupal's Form
Hong Kong Drupal User Group - 2014 March 8th
Hong Kong Drupal User Group - 2014 March 8thWong Hoi Sing Edison What is Drupal?
Evaluate Drupal Project Online
Scalable & Modularized Architecture
Export Settings with Features
Revision Control with GIT
CapitalCamp Features
CapitalCamp FeaturesPhase2 The document discusses the Features module in Drupal, which allows site configuration to be exported from the database into code. Features separates site configuration from content and allows functionality to be packaged and reused across multiple sites. It also enables version control and easier deployment. The document provides examples of how to create, export, import, update, and revert features using the module and Drush commands. It discusses some common usage cases and debugging strategies for overridden features.
Introduction to Drupal Basics
Introduction to Drupal BasicsJuha Niemi This document provides an introduction to the basics of Drupal, an open source content management system (CMS). It describes Drupal's advantages over custom or other CMS platforms, including its modular architecture, security updates, and large community. It also summarizes key Drupal concepts like nodes, taxonomy, modules, themes, and essential modules like Views and CCK. The document concludes with best practices for Drupal usage, administration, and important resources.
Synapseindia drupal intro 0
Synapseindia drupal intro 0saritasingh19866 This document provides an introduction to using content management systems and Drupal specifically. It discusses what a CMS provides, common CMS options, advantages and disadvantages of Drupal, the types of sites it works well for, key Drupal terminology, and its directory structure. The document is intended to be used freely but attribution is appreciated.
Ad
Features: A better way to package stuff in Drupal
- 1. Features a better way to package stuff Rob Knight NWDUG February 2010
- 2. About me ‣ Drupal developer since version 4.6 ‣ Member of the Drupal Association - you should be too! ‣ Working in Manchester at PRWD
- 3. Intro ‣ Features is a Drupal module created by Development Seed ‣ It enables ‘Features’ to be created which package CCK types, Views, Contexts and more ‣ It moves configuration from the database to code
- 4. What is a Feature? ‣ A Feature is a special kind of module ‣ Features consist of generated code ‣ Features are created via the admin UI ‣ Features have version numbers
- 5. How a Drupal installation changes Version Level Changes control? Core Rarely Yes Contrib Regularly Yes Custom code Frequently Maybe Database Constantly No Problem: how to manage change in the database?
- 6. The difference Features make
- 7. Example: Packaging a blog Feature ‣ ‘Blog Post’ content type ‣ Some views ‣ A Context for displaying blocks
- 10. A context
- 11. The resulting blog Text Here we can see the blog content type, the context and the view in action
- 15. Feature contents
- 16. Generated code
- 17. Installing the Feature When the Feature is enabled, all module dependencies will be enabled too
- 18. Changes If any component of the feature is changed, the Feature is ‘overridden’. In this case, I’ve changed a View
- 19. Viewing a ‘diff’ I can now choose to revert the changes or update the Feature code
- 20. Version control ‣ Because Features are code, they can be managed like source code ‣ Updating a Feature is just like updating a module
- 21. Deployment ‣ Features are great for ‘additive’ changes ‣ Not so great for ‘destructive’ changes ‣ Complex changes between Feature versions are still tricky
- 22. Feature Servers ‣ Imagine running your own drupal.org-style module repository ‣ Supports “Available Updates” monitoring ‣ Powerful integration with drush and drush make
- 23. What features doesn’t do (yet) ‣ Taxonomy ‣ Node content and attachments ‣ Menus ‣ However, alternatives exist and more modules are integrating with Features
- 24. Pitfalls ‣ Many contrib modules as yet unsupported ‣ Features isn’t magic - it’s just a system for generating code ‣ Upgrades still need some manual intervention
- 26. Thanks for listening ‣ Features is maintained by Development Seed and is available at http://drupal.org/project/features ‣ My site & blog are at http://robknight.org.uk