![]() In the introduction, Jordan starts by listing the many benefits of using Cypress, such as its extensibility, its ease of use and its growing popularity. ![]() Moving on, we have another article on, this one coming from Aten Design Group’s Jordan Graham who wrote about testing a Drupal website with the open-source testing tool Cypress. Read more about programmatically creating fields He also showcases an example of leveraging bundle fields, the Acquia DAM module, where you need a remote asset ID for a DAM asset on the media entity, but it needs to only be available to media types used in the DAM integration. Matt first defines and differentiates between base fields and bundle fields before showing the step by step process of defining each of them, with the latter being more complex since bundle fields are available only to specific bundles for an entity type. ![]() In the next article, Matt Glaman shows how to create Drupal fields programmatically rather than through configuration, since the latter approach relies on nobody modifying the configuration and potentially making changes to your business logic. Read more about launching a Next-Drupal site on PantheonĬreating fields programmatically and not through field configuration After setting up the Drupal project, you need to add the Next.js for Pantheon module, install Next.js, create the Next.js site, and then finally update the Next.js URLs on the Drupal side of things. Pantheon is well suited for hosting decoupled websites and offers advantages such as cross-platform tooling and workflows, flexibility with hybrid architecture, and consolidated management for all websites.Ĭonnecting the Next.js front end to your Pantheon-based site is very straightforward. Next up, we have an article by Chapter Three’s John Faber which walks the reader through launching a Next-Drupal site on the Pantheon platform. Launching a Next-Drupal site on the Pantheon Platform. The current plan is for both to be included in core in the second half of the year. In combination with the more recent Project Browser initiative, which enables easy installation of modules without using the command line, Automatic Updates gives Drupal users an “app store” like experience. One of the first major changes was adopting the use of Composer for managing packages from Symfony, but this was less favored by non-technical users, which led Dries to first conceptualize the Automatic Updates initiative back in 2017. The next article from Dries focuses on composability in Drupal and how it has evolved since the first no-code update system, Update Manager, in version 7. The evolution of Drupal's composability: from the command line to the browser Read more about preserving the open web through Drupal This is especially strong in the latest version, Drupal 10, which brings numerous benefits to both the developer and editor experience. He opens with his thoughts on the shortcomings of proprietary software, contrasting that with “good software”, which cares about the end user and thus prioritizes things like privacy, accessibility and openness.ĭrupal is the perfect example of such a technology, largely because of its composable approach which allows both developers and non-technical users to create advanced digital experiences. This month’s selection features three excellent articles from Dries the first one we want to highlight is his piece on about Drupal’s role in preserving the open web. April brought us a whole bunch of great Drupal content and news – here are our team’s top picks.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |