Dropbucket.org - snippet repository for Drupal

I have been working with Drupal for a long time and over the years of practice I have accumulated a lot of snippets for solving various problems. During this time, where I just did not store these pieces of code: in notepad, in evernote, in gist, in the IDE (which were replaced like gloves). Whenever I needed to find a particular piece of code in order to reuse it, I either started tedious searches in the middle of all this digital pile or simply wrote the code first.

In the end, I got tired of all this and after a long and lengthy search for a convenient online storage for my snippets, and I went through oh how many solutions, it was decided to create my own, moreover, a strictly Drupal-oriented storage. Such a narrow focus is a tribute to the Drupal community, which until now has not had a similar project for itself.

So there was Dropbucket.org , which was launched a month ago and received a pretty good press in the western part of the Drupal community. To date, 800 Drupal developers from various corners of our planet (including, of course, Russia and Ukraine) have registered on the site.



Next, I will briefly talk about the main features of the project and that it ultimately gives Drupal to the developer.

So, Dropbucket ’s main idea is to create a place where you can save your own snippets by categorizing them according to Drupal themes and versions, and, if you wish, share your best practices with other developers.

Adding Snippets

My main desire was to make as simple a scheme for adding snippets as possible. The form for adding a snippet looks like this:



Here only two fields are required: the header and the code itself, the remaining fields are optional.

Each snippet can consist of several functional pieces added using the “Add another source code” button:



In case you do not want others to see your snippet, it can easily be made private:

Snippet page

On the snippet page you can get a “raw” version of the code or copy it directly to the clipboard:



One of the most popular features is cloning a snippet, when you can clone any snippet hosted on the service and edit it for yourself:



But that’s not all, snippet can be added to favorites, you can vote for it, leave comments and add it to your personal snippet lists.

Each revision of the code creates a separate revision; as a result, you can view previous revisions of the code:

Personal Snippet Lists

A week ago a new feature “Personal snippets lists” was added, which makes it possible to create lists from any snippets:



By clicking on the “Add to list” button:



A menu appears with the help of which all the necessary operations of adding to lists and creating lists are performed:



Such a function convenient for creating knowledge bases on a particular topic of Drupal programming and disseminating it, for example, among team members. Imagine a list of snippets for working with a database.

Snippet Search

Finding a suitable snippet among the blockages of the code is an important task. To solve it, I created a flexible filter that makes it possible to filter snippets by keywords, versions of Drupal, categories, and even by user name:



Each filter can be monitored by subscribing to it through an RSS reader. For example, a Djpal 7 Ajax snippet feed would look like this: dropbucket.org/rss.xml?keys=&field_category_tid=29&field_drupal_version_tid=4&name= . A handy feature for those who want to keep track of a particular category of codes.

Social profile

Each user receives a profile address of the form dropbucket.org/username , where you can see information about the developer, statistics, activity history and his Drupal Karma (well, how can it be without karma, huh?). For every right and wrong movement on the site you are credited with Drupal Karma, which in the future will serve to distribute all kinds of goodies.

Future

There are a lot of plans for the future, after the release of the service, I received a ton of ideas and suggestions, among which it is necessary to filter out the necessary, set priorities and move forward. Among the most likely improvements:

• Recycling the interface for categories of snippets, I'm not very happy with what it looks like now;
• Introduction of an API for integration with various IDEs;
• Ability to export custom snippets;
• Greater socialization and user engagement.

But the most important thing is that the minimum viable product is already there, it works, solves its main problem and people really like it.

Thank you for your attention and hope that the project will appeal to the Russian-speaking Drupal community, despite the fact that the interface is not in our native language.

Please leave suggestions and comments in the comments, your opinion is valuable to me.