Between thought and the real, there is no necessary or natural transition.
So recently we discovered http://data.virginia.gov/hhr and since we're looking to help people in Charlottesville I've added the data (thanks to feeds) and we added a couple of data mining points https://www.cvillecouncil.us/va-physicians (using open layers)for the maps and h
You know those lists on a web site that you see from time to time listing the currently Most Popular articles on the site? I have to admit that I click on them from time to time to understand what is popular and why. It's a clear case of herd reading. Well, Drupal has a new module to create a Most Popular list on your site based on the Chartbeat Analytics API and it's written by myself and Darryl Norris. It's available on Drupal.org.
The more we label things when building a website, the easier it is for a person who is blind and uses a screen reader to use our sites. These labels are known as the “accessible name properties” and they are baked into HTML.
These are not great commit messages; in fact, they are nearly worthless. A great commit message should tell the reader all they need to know about the what of the commit. They should only have to look at the actual diff of the commit to see how it was accomplished.Anatomy of a Great Commit Message
Think of a commit message like an email:
- It contains your contact information. You don't even have to do anything; you get this for free!
- It should have a subject: the shorter, one-line summary.
- A body: the detailed description.
All commit messages should abide by the following criteria:
- Begin with a one line summary. It should be capitalized and succinct (50 chars or less).
- This should be followed by a longer description, if necessary.
- The first two items should be separated by an empty line.
- All lines should be wrapped at approximately 72 characters.
- Reference an issue in your commits whenever possible. If using Github issues, you can reference them by using 'gh-80' for issue '#80'. If your commit completes the issue, you can use a number of terms to close the issue, such as: .Closes gh-80'.
- If you forget to reference the issue in your commit, and the commit has already been pushed, reference the commit's hash in a comment on the ticket.
Here is a model Git commit message:Capitalized, short (50 chars or less) summary. More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together. Further paragraphs come after blank lines. * Bullet points are okay, too. * Typically a hyphen or asterisk is used for the bullet, preceded by a single space, with blank lines in between, but conventions vary here. * Use a hanging indent. Closes gh-80.
The majority of your commit messages may be much simpler than the example above, but pick and choose the appropriate elements. Here is an example more common to the real world:Fix for editor dashboard showing incorrect date. * Fixed date calculation logic. * Added function docblock to comply with coding standards. * Refactored foreach loop, improving clarity. Closes gh-80.
With just a few small improvements to your commit messages, your fellow developers, and your future self will surely thank you!
ALDÍANews.com is a national news outlet offering fully bilingual content, equally accessible in both English and Spanish at the click of a toggle. The new site - which publishes news related to politics, business, culture, opinion, media, and technology - allows readers to quickly and easily choose the language in which they want to view a comprehensive array of content and features optimized for various devices through responsive design.
After evaluating AL DÍA’s content and traffic, we uncovered the untapped potential for a larger audience and advertising stream by repositioning this local news site as a national news platform. The new site implements a number of innovative elements that benefit viewers and advertisers alike, including lightning-fast browsing using AngularJS, a fully bilingual interface, and advertising that can be served to specific sections, topics, or geographies.Key modules/theme/distribution used: ServicesSimpleAdsTaxonomy menuViewsRadioactivityOrganizations involved: Eastern Standard
Mobile device usage is surging as people use them to read content, shop online, and find information on the go. Users are proven to be happier and more willing to spend time and money on your site when it loads fast and responds quickly to their actions. Adding performance to the ever-growing list of project responsibilities can seem daunting, but it doesn't have to be.
In this full-day training, we will address every step in the process of improving frontend performance: auditing a site for problems, creating an effective solution, testing sites to ensure that the work was successful, and implementing automation tools that prevent regressions from creeping back into the codebase. Additionally, we will offer tools and suggestions to help your organization adopt a culture of performance, boosting its visibility in discussions and allowing your team to expose performance problems earlier in the development cycle, long before launch.
Wait, $langcode? What the Heck?
If that was the most polite thought that crossed your mind when dealing with the Drupal 7 Field API, please read on.
No matter whether you build complex multilingual sites, or whether just hearing the words “Drupal” and “language” in the same sentence makes you want to hide in the darkest corner of your office, there are a few language-related notions that you really need to know to write Drupal 8 code that works properly. After all, language is an intrinsic property of textual content, and since Drupal is supposed to manage content, having to deal with language does not seem such a peregrine idea, does it?Speaking of Content
Historically, content in Drupal is a user-friendly way to refer to nodes. However, in Drupal 8, content has a broader meaning: it refers to any entity type which stores information usually meant to be experienced in some form by a certain set of site users.
Content entities, such as nodes, comments, terms, custom blocks, custom menu links, and users, are all examples of this kind of entity type. The other main category is Configuration entities: node types, views, fields, menus, and roles, are meant to store information mainly related to determining the site behavior. Note that this distinction may not always be so clear-cut, as in some cases the choice of picking one category or the other may be determined mainly by implementation details, as in the case of module-provided menu links.
To sum up, when in Drupal 8 we speak of content, most of the time we are referring to content entity types.Multilingual Content: A Bit of History
In Drupal 7, a new way of translating content was introduced by adding native multilingual support to the Field API. That allowed the ability to store multilingual values for any field attached to any entity type. But code that implements business logic needs to explicitly deal with field language, which implies a very poor developer experience (DX); i.e., this infamous field data structure:
In the third installment of REST Easy, our RESTful module tutorial series, we’ll take a look at how to filter your API endpoints for results, a great feature that brings in the power of Entity Field Query for your APIs.
In the first article on Drupal 8 module development we looked a bit at the routing aspect of this process. We’ve seen that creating pages with paths is now a matter of declaring routes that match up with controllers. The latter, as we’ve seen, can return a render array that gets interpreted into markup and displayed in the main content area of that page. However, did you know that under the hood, Drupal actually transforms that array into a Response object according to the dictates of Symfony’s HTTPKernelInterface?
In this article, I would like us to go deeper into the internals of Drupal 8 (and Symfony2) and look at what actually happens (and can happen) from the moment a request is made by a user to the one in which they see something returned in response. The example I mentioned above is just one direction this process can go in, and today we are also going to see other possibilities. The goal is to understand the flexibility of the system which in turn can help us build awesome applications.
Before going into it, I strongly recommend you check out this diagram which does an amazing job at synthesizing what is often referred to as the render pipeline. Though in my opinion it represents more than the name implies because the render system is only part of what’s depicted, albeit a big one.
Continue reading %From Request to Response: A Journey into Drupal 8 Internals%
This module is used to add class to the nodes based on the content type.
Once the module is enabled:
1. This module adds a fieldset named "Node type class" in node type form,
For eg: admin/structure/types/manage/article for "article" content type.
2. It adds the class(es) to the <body> tag of the node page.
Node class: This module adds class per node not per content type.
We recommend using Drupal as a content management system platform for our client projects for many reasons, not least of which is that it is a widely adopted, free, open source solution. Here are some of the strengths that we see our clients benefiting from when they use the Drupal content management system.
I have been searching for a way to make Drupal output cleaner, lighter, more semantic HTML since I started theming. We all know Drupal core, and it's many contrib modules have a tendency to inject a couple-two-tree divs in 'dere. I have tried many different ways, much to the chagrin of the developers I have worked with, most of them probably not worth the effort I put in. That is until now!
The goal of my approach here is to minimize the markup that Drupal puts out, and gain complete control over the what and the where of the markup. I can gain control of the fields using the Fences module; control over the templates in my theme; and gain even more control over the placement and what gets loaded using ctools Page Manager and Panels. I will step through each of this in detail below.
The HeadBar module will provide a header bar above the body of the page.
It is used to attract the viewer as the header bar will appear after some seconds as configured.
It is used to highlight any special thing in site like:
- New article
- Contact us
- Social media link
- Not only plain text but HTML tags can also be added.
- Color of the bar and mouse hover of the show icon can be configured.
- Delay-time of the bar can be controlled.
See README.txt file for more info.
This module is designed to be used with Chartbeat. If you do not have a Chartbeat account, it will not work. If you do have Chartbeat and you're looking to present the Most Popular URLs on your site, this module will do that for you. It will create a Chartbeat - Most Popular block that you can add to your site.
This module is a proof of concept. It needs work and should be used with caution. Once enabled, if a hostmaster user has permission to upload an SSH key, they will be given SSH access to the primary server_master server.
Provides a faster method to register for events.Please post bug reports and feature requests to the GitHub project. Dependencies
- Drupal 8 beta14
- RNG 8.x-1.0-alpha5