By Michael Ross
In Drupal 7, site administrators can utilize its core Toolbar module for speeding navigation. Drupal 8's equivalent improves upon it, sporting a more readable interface, with clear icons. Admin menu items are grouped into: "Manage" (encompassing the menu items of its predecessor, with "Modules" renamed to "Extend"), "Shortcuts", and a user menu for profile management and logging out. The toolbar is responsive to the device's screen width, switching to a vertical orientation for narrow displays — which can be forced by clicking the arrow button on the far right of the toolbar's (white) second level.
Figure 1. Drupal 8 admin toolbar vertical
Copyright © 2014 Michael J. Ross. All rights reserved.
Drupal users who want to build or customize displays or layouts, or simply build their own administrative areas will love Views from the Ground Up and now is your chance to attend this training at DrupalCon Amsterdam!
Views from the Ground Up consists of 8 real world (and useful) views that are created with an increasing level of complexity. By the end of this class, students will be able to take almost any views display currently being used in Drupal, and override it, to fit better to their particular admin style and needs.Meet the Trainer from the NorthCross Group
Chris Porter (netw3rker) has spoken at DrupalCon Barcelona, Munich, and San Francisco and has provided this training for the past four years to a variety of global clients, including Fortune 500 companies.Attend this Drupal Training
This training will be held on Monday, 29 September from 09:00-17:00 at the Amsterdam RAI during DrupalCon Amsterdam. The cost of attending this training is €400 and includes training materials, meals and coffee breaks. A DrupalCon ticket is not required to register to attend this event.
Our training courses are designed to be small enough to provide attendees plenty of one-on-one time with the instructor, but large enough that they are a good use of the instructor's time. Each training course must meet its minimum sign-up number by 5 September in order for the course to take place. You can help to ensure your training course takes place by registering before this date and reminding friends and colleagues to attend.
Modules Unraveled: 117 The Drupal Project Application Process with Jeremy Rasmussen - Modules Unraveled Podcast
It’s easier than you think to publish your module on Drupal.org. This is my experience going through the entire process. Sharing this experience I hope to convince you and others to do the same. Contributing back to the community that gives all of us so much, to many of us our livelihood.
When Doug first recommended that I talk to you about this, I wasn’t really thrilled. But, I took a look at your slides, and thought that it actually looked like really good information. So, what made you decide to put together a presentation on the project application process in the first place?
Finally published a module to help solve my own problem
My project that took me through this process is Display Suite Extra Layouts
Projects don’t have to be the 100% perfect solve for everyone, everywhere
It’s more about: Giving back, centralizing code, helping others make great projects too.
So what are the steps to getting a project reviewed and accepted?
Where to start and basically the entire guide to submitting a module
“Apply for permissions to create full projects” https://www.drupal.org/node/1011698
Some things to know
One time process
Reviews are primarily by your peers
Learns/reiterates code standards and best practices
Do your Research First
Check if your idea exists already
Combine efforts where you can
Volunteer as a co-maintainer where needed
Okay, let’s get down to the nitty-gritty. What are the technical steps you need to follow to get your project approved?
Setup Git Access
Learn some Git basics
Google is your friend
Github & Code School’s tutorial http://try.github.io
Setup your Git Access in your D.o profile
Basically just need to add an SSH key
Instructions here: https://www.drupal.org/node/1047190
With Git access setup you can now create sandboxes or “experimental” projects
Instructions here: https://www.drupal.org/node/1011196
Take advantage of these, having a commit history of changes is a good thing.
Use sandboxes to get your code “production ready”
The Checklist (Pre-Application)
Before starting the application make sure you run through the checklist
Setup Readme, Git Branches, well commented, etc...
Link to checklist: https://www.drupal.org/node/1587704
The process goes much much faster, many people skip it
PA Review Bonus
Part of the checklist asks you to run your sandbox through a bot.
Catches the majority of problems.
You can setup your own Review Bot
“Full Stop” - Took me a while to figure that out.
You get a review bonus when everything is fixed.
READ THE DIRECTIONS!
In the title include core version: [D7]
Write a Clear Descriptions… can be the same as your project/sandbox page
Clear descriptions help people understand better the purpose of your project
Provide links to your Sandbox, the Git clone command, and PA Review
When you are ready set the status to “Needs Review”
I noticed when I looked through your slides that you mentioned reviewing other projects as a part of this. Why is that needed?
Reviewing other projects
You must review at least 3 other people’s projects
Post a link to your reviews in your own project application
It’s just like trying a new module.
Download it, enable it, try it
Report back your findings… good, bad, and suggestions
I learned a lot from doing this
Now you wait.
Others will review your project and post feedback.
be prompt to fix issues
Once all is well someone should mark your project “Reviewed and Tested by the Community”
Then you wait for someone with the “Power” to grant you full project status
Once someone has approved your project, what’s involved with getting the official project page setup?
Into the Wild!
You can now create your project page
be mindful of your project URL, you can’t change it
Create a new release on your project page and in Git
Creating a release: https://www.drupal.org/node/1068944
Tag Nameing Convention: https://www.drupal.org/node/1015226
Will this cover D.O vs github for projects? Pros & cons of staying with current design vs migrating to github?
- Joshua Turton
What do you get when you combine a state-of-the-art open source content management system with a seemingly endless need for developers, an instructor passionate about developing Drupal talent with solid fundamentals and best practices (yours truly), six eager, geographically diverse students (pictured above - more on them in future blog posts), and a modern online classroom environment (the topic of this post)? If the content management system is Drupal, then the only answer is the online version of the Drupal Career Starter Program: Drupal Career Online.
This week marks the start of the first session of Drupal Career Online, an immersive 12-week online training program designed to take people passionate about technology and turn them into Drupal professionals. The curriculum is the result of continuous development and improvement over the past three years, and now features a dedicated web site, PDF handouts and reference documents for every lesson, weekly self-assessment quizzes, screencasts covering important concepts and a healthy dose of Drupal community involvement.
Drupal has long had a strong collaborative culture. We share modules, we share development tasks on core and modules, and we share infrastructure on Drupal.org. That's a critical part of the health of our community: Sharing is how Open Source works.
The broader PHP world, however, has long sucked at sharing. Every project is its own island; sharing code between projects has been difficult, and managing third party libraries a pain. Just about the only option was PEAR, but unless you had root access on every server you needed, and were running only a single application per server, it wasn't really useful.
That was then, this is now. Enter Composer, a PHP dependency management tool that works. Composer began life in late 2011 in the Symfony community but was deliberately built to be project-agnostic, and today is being used by thousands of projects large and small, including Drupal.Composer Basics
Composer consists of two parts. One is Packagist.org, which is a central clearinghouse of Composer-compatible packages. As of July 2013, Packagist offers over 13,000 packages, ranging from simple libraries to complete frameworks. The other part is Composer itself, a command line PHP application that is dead simple to install. By default, Composer will download packages from Packagist.org but you can also set up your own package server, or even just one-off Git repositories, to host Composer-capable code. All you need to make it work is a simple JSON file.
Let's start off with a trivial example. We’ll write a super-simple script that uses the Guzzle HTTP client (now bundled with Drupal 8). To start off, create your project folder. Inside it, create a directory called src. That's where we'll put all of our code. Now create a file called composer.json with the following contents:
The monthly Drupal core bug fix release window is scheduled for this Wednesday. However, there have been three releases (security releases as well as bug fix releases) in the last month and a half, and not as many changes have been committed to the development version since then as would normally warrant yet another new release.
A Drupal 7 bug fix release during the October release window is likely instead.
Upcoming release windows include:
- Wednesday, September 17 (security release window)
- Wednesday, October 1 (bug fix release window)