Preston So has been a web developer and designer since 2001, a creative professional since 2004, and a Drupal developer since 2007. As Director of Research and Innovation at Acquia, Preston leads Acquia Labs, the innovation lab featured in international press such as VentureBeat and ZDNet, and new open-source and research initiatives.
Previously, Preston managed the Entertainment Weekly website and led its development team at Time Inc. He also contributed to the Spark initiative in the Drupal project, co-founded the Southern Colorado Drupal User Group (est. 2008), and operated an award-winning freelance web and print design studio. While at university, Preston directed the most recent redesign of The Harvard Crimson's online edition, producing the first student-designed responsive college newspaper website in the Ivy League.
Preston has presented keynotes at conferences on three continents in multiple languages and speaks around the world about diverse topics such as decoupled Drupal, responsive design, front-end development, user experience, and open-source innovation.
Recent Blog posts
Though there was no DrupalCon Europe this year, the European Drupal community stepped up and organized their own conference, Drupal Europe, in Darmstadt, Germany last month. An incredibly successful gathering held in the Darmstadtium venue, a beautiful convention center in the center of this college town, Drupal Europe demonstrated the unique power that grassroots initiatives can have in our open-source community.
Experience Express in Lisbon: Forging the Future of Drupal Architectures and Initiatives at Drupal Developer Days
In Lisbon, steep slopes and sweeping vistas towering over placid waters and crowded ports characterize the topography of one of the most beautiful cities in Europe.
This year, the Portuguese capital played host to Drupal Developer Days, possibly the most important event for developers specializing in Drupal. Held at the University Institute of Lisbon, it was a conference not to be missed, with innumerable insights from Drupal core contributors and maintainers.
Experience Express in Utrecht: Conversational Design and Modern Front-end Approaches at Frontend United
With a uniquely diverse community of designers, developers, and everyone in between, Frontend United is one of the conferences I find I enjoy more and more each time I attend. And this time, in Utrecht, a wide range of designer- and developer-oriented content greeted attendees both within and well outside the Drupal universe.
Atop the Castle of Saint Barbara in Alicante, time sometimes seems to slow down, and words that once held grand meaning seem inadequate. I had a similar feeling both during and on the heels of DrupalCamp Spain, organized by the Spanish Drupal Association and held this year at Las Cigarreras cultural center in a seaside city that is one of the crown jewels of not only the Valencian Community but also of Spain.
As we saw in the previous post, core REST only allows for individual entities to be retrieved, and Views REST exports only permit the issuance of GET requests rather than unsafe methods as well. But application developers often need greater flexibility and control, such as the ability to fetch collections, sort and paginate them, and access related entities that are referenced.
In this column, we'll inspect JSON API, part of the surrounding contributed web services ecosystem that Drupal 8 relies on to provide even more extensive features relevant to application developers that include relationships and complex operations such as sorting and pagination.
When Phillies hats begin to dot the landscape and one of the most beautiful train stations in the country materializes around you, you know you're in Philadelphia, a city I can never seem to stop loving. After a brief hiatus, Drupaldelphia was in full swing this year, attracting developers, creatives, and businesspeople from all over Pennsylvania and surrounding states to a conference that is always full of pleasant surprises.
As we saw in a previous installment of Experience Express, because Drupal has a HAL-compliant REST API available out of the box with minimal configuration, you can easily provision an API that can immediately be employed to consume content entities and manipulate them from other applications. Now that we have successfully exposed content entities as REST resources, used Entity Access to govern permissions, and customized the formats and authentication mechanisms in use by the core REST API, it is now time to move into actually retrieving and manipulating that data.
Perhaps the most critical piece of any decoupled CMS architecture is the API layer which exposes data in the back end for consumption by other applications.