Imagine you’ve got a module that defines a piece of content that can be rendered in multiple locations…in fact, you might not even know where your content will show. You just define it, then it could show up in a block, on a page, as content of a node, etc. With the magical power of the #attached FAPI property, you could attach your library to any piece of content (built as a renderable array), and bypass the drupal_add_* calls altogether like so:
A modification of the pinboard bookmarklet with enhancements that appeal to my fiddly nature.
_Title is cleaned of extraneous "SEO-junk" through heuristics based on page structure
_Description field is populated with the selected text, or pulled from description tags in page header
_Tags are added according to keyword rules setup by the user.
- Mixture – A rapid prototyping and static site generation tool for designers and developers
Mixture brings together a collection of awesome tools and best practices. It’s quick, no-fuss, super-powerful and works with your favourite editor.
- Moving Google Reader to Drupal Aggregator | David Norman
On March 12, 2013, Google announced the retirement of the Google Reader service on July 1, 2013. Fortunately, Drupal 7 has a module that can handle this situation included in core – the Aggregator module. Google’s Takeout service exports your list of feeds in OPML format and the Aggregator module can read it. I took some screenshots of my Reader export and import back into the deekayen.net aggregator.
- jQuery TourBus
Well, too bad for you! I wanted a simpler, less things-happen-automatically toolkit for making tours. If I need auto-advance/progress between ‘legs’ (get it, legs of the tour :)) I just need some callbacks where I can write my setTimeouts. If I want to highlight some elements, I just write some styles to do that and apply them appropriately. I much prefer this approach, maybe you do too 🙂