whilst traditional REST is the more popular approach for fetching data, it may not be the best in solving many of the problems of handling hierarchical data. In comes GraphQL, a database querying language built by Facebook, to solve the limitations of REST - which may include overfetching, under fetching, multiple round-trips, and versioning issues.
whilst traditional REST is the more popular approach for fetching data, it may not be the best in solving many of the problems of handling hierarchical data. In comes GraphQL, a database querying language built by Facebook, to solve the limitations of REST - which may include overfetching, under fetching, multiple round-trips, and versioning issues.
With the release of Drupal 8, the core blocks system is now a powerful publishing system for content in sidebars or landing pages. Blocks have types, fields, revisions and many other benefits now that they are full Entities. If you are a coder, you'll be happy to know that these block types can also be created and extended using OOP techniques.
If you still use Drupal 7, have no fear! The Drupal 8 Block improvements are largely a port of the Bean module (Block Entities Aren't Nodes).
With the release of Drupal 8, the core blocks system is now a powerful publishing system for content in sidebars or landing pages. Blocks have types, fields, revisions and many other benefits now that they are full Entities. If you are a coder, you'll be happy to know that these block types can also be created and extended using OOP techniques.
If you still use Drupal 7, have no fear! The Drupal 8 Block improvements are largely a port of the Bean module (Block Entities Aren't Nodes).
I've been writing a lot about what I believe is important for the future of Drupal, but now it is your turn. After every major release of Drupal I do a "product management survey" to get your ideas and data on what to focus on for future releases of Drupal (8.x/9).
The last time we had such a survey was after the release of Drupal 7, six months into the development of Drupal 8. I presented the results at DrupalCon London in 2011. The results informed the Drupal community at large, but were also the basis for defining initiatives for Drupal 8.
I've been writing a lot about what I believe is important for the future of Drupal, but now it is your turn. After every major release of Drupal I do a "product management survey" to get your ideas and data on what to focus on for future releases of Drupal (8.x/9).
The last time we had such a survey was after the release of Drupal 7, six months into the development of Drupal 8. I presented the results at DrupalCon London in 2011. The results informed the Drupal community at large, but were also the basis for defining initiatives for Drupal 8.
I've been writing a lot about what I believe is important for the future of Drupal, but now it is your turn. After every major release of Drupal I do a "product management survey" to get your ideas and data on what to focus on for future releases of Drupal (8.x/9).
The last time we had such a survey was after the release of Drupal 7, six months into the development of Drupal 8. I presented the results at DrupalCon London in 2011. The results informed the Drupal community at large, but were also the basis for defining initiatives for Drupal 8.