Thank You
We appreciate your inquiry. We'll be in contact soon.
In this series, Amber will show you how she gathered her wedding invitation responses on a Drupal site using Webform module. You'll learn how to:
Understanding the basics of Webform empowers you to create your own custom forms such as surveys, feedback forms or your very own RSVP form. Dive in and learn the basics of Webform.
In an earlier post, Kyle wrote a great introduction to the new configuration management system in Drupal 8. He demonstrated how end users can leverage this new system to easily migrate site configuration between environment, which helps eliminate the "did you remember to check the boxes in the right order?" problem for site builders everywhere. In this post, I take a look at configuration management from the perspective of a module developer. What do we need to write in our custom code to ensure that our configuration settings are easy to deploy?
In our podcast episode 34, Kyle is joined by Kevin Colligan, Sr. Director/Head of Digital Media for the GRAMMY Awards, and Nate Haug, Senior Drupal Architect at Lullabot, to discuss how GRAMMY.com is powered by Drupal.
This week we continue our learning series, Working with Media Module in Drupal 7. In these lessons, Addison explains the many considerations of managing media in a content management system, how you can use Drupal and the Media module to manage and display all kinds of media, and how you can utilize images in several different ways. If you've been wondering how to place images using a WYSIWYG editor or how to create a gallery, these are the lessons you've been waiting for.
Drupal is a Content Management System and most often when we think of content, we tend to think of the text-based content we type into into web forms and see as a blog, or an about us page. Digital media creators, however, also have to deal with sound clips, videos, and images. Those things need to be stored, retrieved and displayed just like text, and understanding the needs and processes around this will make working with them in our site a better experience.
In this lesson, we're going to look at the major needs for media asset management in Drupal with:
Note: This series is covering Media Module version 1.x. To learn about Media Module 2.x, check out our Using Drupal Chapter 4: Media Management series.
The history of working with media in Drupal is long and bumpy. The main goal of the Media module is to create a refined, centralized way of handling media on a Drupal site, and Media, version 1, is the main tool we'll be using to create our site. In this lesson we'll get an overview of the Media module and specifically take a look at:
Note: This series is covering Media Module version 1.x. To learn about Media Module 2.x, check out our Using Drupal Chapter 4: Media Management series.
Working with images can sound very straight-forward, but there are actually many, many ways that we use images on the web. You need to know what your use case is, and the right approach to meet those needs, to save yourself some headaches.
In this lesson, we're going to discuss the different ways we may need to use images and how to approach those with Drupal. We'll be discussing:
Note: This series is covering Media Module version 1.x. To learn about Media Module 2.x, check out our Using Drupal Chapter 4: Media Management series.
Forms are an essential part of any web application. They are the primary mechanism for collecting input from our users, and without them Drupal wouldn't be very useful. As such, they're also one of the first things people want to learn when they start learning Drupal. Forms are fundamental to creating Drupal modules, whether you're asking someone to leave a review of your video or giving an administrator the option to turn JavaScript aggregation off.
This overview will introduce you to Acquia's open cloud platform and this series of lessons that will show you how to best use it. If you do not already have a free Acquia Network account, you may obtain one from Acquia.
We appreciate your inquiry. We'll be in contact soon.
On January 14, 2014, Emma hosted a webinar. Although the recording is not available, we hope you find this follow up FAQ useful as a companion to her learning series PSD to Theme
A: We had originally planned to use Zen Grids for our framework, but our designer had already mocked up his designs with Susy. It would have been too time consuming to rebuild the working prototype with a different framework, so we decided to take the easy path and just switch our theme to use Susy. Note: prototyping is GREAT! This doesn't mean that you must use only one framework from start to finish. I just mean for our time line and resources, it was more efficient to stick with the same framework as the HTML prototype.
A: Every single framework has great qualities about it. You should choose the one which feels most natural to you and/or your support network knows and uses. (Having access to help is important!) If you're not sure where to start, I recommend picking a base theme first, and then learning how to use the framework which comes with that base theme. e.g. if you pick Zen, choose Zen Grids as your grid framework for rapid prototyping. Do your research and talk to your team. They may already have favorites.
A: I recommend having a text-based style guide which is separate from your theme (ideally your style guide would be built from your theme's files; but the technology is not ready yet). If you are using Sass, everyone working on the project must commit to all editing ONLY the Sass files (not the Sass and CSS files). There are lots of helper tools you can use to make building CSS from Sass a lot easier. We have a video series on Sass. If you're thinking about adopting Sass I highly recommend you watch the Sass and Compass video tutorials. There are ways you can include CSS edits in your theme, but this ends up being a headache to maintain long term. You're better to invest the time in getting everyone using Sass / Compass rather than spend the time later refactoring CSS files. (Unless you love refactoring based on git diff...whatever floats your boat!)
A: It's not that hard, promise! We cover installation instructions in the Install Compass video. If you prefer a GUI, we cover that too! You can watch the Install Scout video.
A: Front End Drupal (covers Drupal 6). Drupal User's Guide (covers Drupal 7).
A: Photoshop is the PERFECT tool for designers who think best with Photoshop. Some prefer pencil and paper to make their ideas....the IDEA CREATION tool is up to the designer. Photoshop is not always the best tool for mock-up approval with stakeholders as it does not allow you to prototype (or demonstrate) how components will behave in the context of one another. We liked working in components instead of pages. This way the designer could quickly mockup how a component looked in a specific context; rather than this is how an entire page worked at a width of 799pixels, 798 pixels, 797 pixels, 800 pixels, 801 pixels (you get the picture, right?). We need to think about the process though when choosing formats. Designers may do their best creative work in Photoshop, but then ... somehow ... we need to convert that to a theme. I think the best tool for this is a TEXT-based description of the components with screen shots (or little square images) of how that component looks in different contexts. i.e. how does this component look at each break point.
A: Basically, yes. Sass has some nifty math tricks which allow you to do math with different units (e.g. 20em - 12px). We have a video which discusses the differences of Sass vs LESS.
A: Components. Components. Components. Start with the Theming by Component video.
A: Yes. :-) Think of a component as a piece of furniture. It's anything you could pick up and move to a different location. Often there is a direct correlation with a Drupal site building technique: image style, view mode for a content type, a block, etc. You probably have a list of things you need to build for your client, which all get put into a wireframe and then a complete design. Maybe your complete design is an HTML prototype, maybe it's a static PSD file. There are LOTS of variables here, and not many hard rules. That's why I like to think of a component as "furniture" or "anything I can draw a box around" (as opposed to a wiggly shape). If you haven't already watched it, you'll want to watch the Theming by Component video.
A: The Sass and Compass learning series is about 2.5 hours. The PSD to Theme series is a little less than 3 hours. I think if you can spend a day watching these videos, you'll be ready!
A: CSS coding conventions and the massive theme system overhaul prompted by the Twig initiative. Don't get me wrong, Twig is pretty cool, but I'm most excited about the clean-up. I like things to be neat and tidy. :-)
A: Sass and Drupal are somewhat independent. Drupal doesn't really speak Sass if everything is working correctly, it uses rendered Sass (aka CSS). The PSD to Theme series has information on creating CSS stub files, and layout rules. The series works best if you watch it in order, so you might want to start at the beginning and at least watch the first few minutes of the videos which come earlier to have things in context.
A: Base themes are such a hot topic! There are two VERY LONG answers to this. One is a presentation that I did at Munich (Evaluating Base Themes); the other is a Drupalize.Me podcast that I was a guest on. Short answer: it depends.
A: Micah would say "yes"; Jesper would say "no". You can watch their DrupalCon presentations and decide for yourself. :-) Generally I agree with Jesper, but it does add an extra layer of headache going through and making Drupal do what you want...and it's a headache the client will rarely pay for.
A: reveal.js. You can get the code for this exact presentation in our GitHub project.
A: Get to the root of their concern by using the "5 Whys", and maybe show them a picture like this:
(http://wcetblog.files.wordpress.com/2013/12/overwhelmed-by-devices-by-l…)
A: Conversation and pattern libraries. I talk more about pattern libraries in the Theming by Component video.
A: I never do anything automated with cutting up images. Ever. I extract the assets I want from my design files. You can watch my video for this process in the Extract Design Assets video.
A: If you want to support the work Jonathan is doing, yes! If you just want the information, start with the free Drupal resources. The Drupal 8 CSS Coding Standards can be applied to Drupal 7 sites today.
A: I use Sublime Text in the videos as we find it to be the most accessible, cross-platform text editor. I use Vim for my normal development work.
We hope you found the webinar, and this FAQ, useful and hope you'll consider becoming a member of Drupalize.Me so that you can take advantage of our extended videos on Sass and Compass, and PSD to Theme. Our pricing plans are appropriate for individuals and organizations. Click here for more details.
This lesson describes how to drag-and-drop to deploy code and content using the Acquia Cloud UI.
Repeat steps 2 and 3 for the "Files" and "DB" boxes in the Dev column.
You may drag-and-drop these boxes (Code, Files, DB) in either direction: from Dev to Stage; or from Stage to Dev. If you would like to deploy your code to a live server, you will need to upgrade from the Acquia Free account. You can do this by clicking the link "Upgrade now" from the "Prod" column.
This is Step-5 of the Free Tier on-boarding process for Acquia Cloud.
To be able to use Search and Insight, you will need to connect your site to the Acquia Network. The video will walk you through this process and help you get connected to the network easily.
Your site should now be connected to the Acquia Network.
This is Step-4 of the Free Tier on-boarding process for Acquia Cloud.
If you already have a Drupal Web site, you can import it to Acquia Cloud using the following steps:
Note: This will only work for archives that are smaller than 500MB. If your site is larger than this, you will need to refer to Acquia Cloud's documentation.
This is Step-3 of the Free Tier on-boarding process for Acquia Cloud.
You can install one of several Drupal distributions from within the Cloud Network dashboard. Installing Drupal in this manner will remove a previously installed distribution. Assuming you want to create a new installation of Drupal, complete the following steps:
Once your site has been created, you may visit it by clicking on the link "visit" in the Dev environment tab. From here you will be able to complete the installation and log into your new site.
This is Step-2 of the Free Tier on-boarding process for Acquia Cloud.
The video will walk you through getting your code setup with Acquia Cloud. This lesson covers:
If you don't use Windows and TortoiseGit, or if you want a better overview of Git itself, we have an entire series on Git, which will show you how to install Git and use it from the command line, including doing a git clone command. Once you get things set up with Git, you can refer back to this video to see where you get the Acquia-specific Git information you need.
This is Step-1 of the Free Tier on-boarding process for Acquia Cloud.
After setting up Git, you may proceed in two directions: You can either Install Drupal Distro or if you already have an existing site, you can go ahead and import your site.
Every year Real Story Group (RSG) releases an updated snapshot of the web CMS market. Where will Drupal 8 be placed on the 2015 RSG snapshot?
Today we finally completed the migration to our new billing service! It's been a long road, and I'll leave the gorey details for another post. The short of it is that we moved to Recurly and account management is now easier for our members.
This week we have podcast episode 33. It's all about Global Sprint Days, coming up next weekend, on January 25-26, 2014. We talk about what sprints are, what's happening next weekend, and the why/how of getting involved. Go give it a listen, and then sign up for (or create) a local event!