Today, the Newspapers & Magazine industry is turning towards digitization to cater for Millennial and Gen Z. The publishing industry is keen to choose Open Source Technologies such as Drupal as their CMS platform over other native applications. This blog shares with you Key Requirements of Digital Publishing and How Drupal could be a best choice for Digital Publishing Solutions through PPT. Leveraging on sophisticated features of Drupal 8 Publishers can now deliver right content to audience at right time on right device.
One question that's come up has been:
When should I define a service?
Recovering from surgery finally gave me time to update my last D6 site—a 7 year old private photo and media sharing site with nearly 10,000 nodes and 20+ GB of content—to Drupal 8. Drupal 8 has become a lot more mature lately, to the point where I'm comfortable building a site and not having the foundation rot out from beneath as large ecosystem shifts have mostly settled down.
One thing that I thought would have the simplest implementation actually took a little while to figure out. I needed to have users' full name display instead of their usernames throughout the site. For D6 (and for similar D7 use cases), the easiest way to do this was to enable the Realname module, configure it a tiny bit, and be done with it.
In Drupal 8, however, Realname doesn't yet have a full release (see this issue for progress), and the way usernames are generated has changed slightly (see change record hook_username_alter() changed to hook_user_format_name_alter()).
I recently read a report by Deloitte which stated that, by the end of 2016, fewer than 25% of information technology jobs in developed countries will be held by women. That’s quite bleak, especially for women and young girls who are thinking about starting and developing a career in IT.
That got me reading on the topic of “women in tech” a little more. It’s a well-known topic and a lot of people have suggested potential reasons for this gap: an unconscious gender bias brought about by tech being a “boy’s club”; very few female role models in the tech industry; but perhaps most interestingly, the concept of a “brogrammer” culture: competitive male developers who are in it to prove they’re the best in a macho, masculine way, shouldering anyone else to the sidelines.
I’m no stranger to the brogrammer culture: I’ve worked alongside men who behave this way, and it’s apparent when I attend developer events as well. But as an answer to the question “why don’t girls consider IT and STEM as career choices from a young age”, that might be too simplistic.
My interest in computers began as a child. I can’t remember a time when we didn’t have a computer in the house - my dad was, and is, a massive geek, and prided himself on being an early adopter of everything and anything. He encouraged me to tinker, explore and break things. Without a shadow of a doubt, my enthusiasm and interest stemmed from those years when he let me run loose on his PC (and invariably end up breaking something).
I was really lucky to attend a well-equipped primary school until I was 10, where we had IT lessons once a week, learning about how to use computers to solve real-world problems. My secondary school was an all-girls’ school, where we did our IT GCSE at the end of year 9 - two years early. Some of my peers even went on to do their A level IT while we were doing our GCSEs.
That said, my secondary school was in a rural location, and many of my peers seemed preprogrammed to believe they would move into well-known careers like teaching, childcare or even farming. Aspirations to move into STEM-related careers amongst my fellow students were few and far between, even though our teachers were constantly pushing us towards medicine, veterinary sciences, IT, mathematics and the like. The opportunities existed and our teachers were great at encouraging us to consider STEM as a career choice, but most students passed it over completely.
So, it begs the question: if these children knew there were career opportunities available in STEM, and they knew they were lucrative, well-paid jobs, why did they pass them over for other, more traditional options? Why are so few girls willing to choose a career in STEM?
This got me thinking about how STEM is portrayed as a career. My role as a web developer is all about logic-based problem solving: it’s critical thinking at its very finest. We should be demonstrating to kids how fun and rewarding it can be when you’re presented with a real world problem, and how you use computer programming in a logical way to arrive at a solution.
As an avid digital artist in my spare time, I feel we should expand to students of the arts, demonstrating how computer design can be a viable career alternative. So often schools pigeonhole artistry as “painting bowls of fruit on paper”, skimming over the awesome world of technology: there’s graphic design, animation, games design, music production and so much more. A career in IT doesn’t necessarily mean programming!
So often people choose careers because they feel fulfilled in them: teachers because they like teaching and nurturing kids; doctors because they like to care for others; historians because they enjoy history. With tech, it’s important to sell the story in a different way. We need to ditch the perception of “if you work with computers, you’re geeky and uncool”, and frame a career in tech as “a way to solve problems”, so that we can inspire inquisitive minds from an early age.
But what about when it comes to boys versus girls? What’s the solution for getting more girls into tech? Well, in my view everything I’ve said here applies to both boys and girls. I would have hated being singled out as a special case because I was “a girl who liked computers” - like some kind of unicorn!
I’m a staunch believer that if a person doesn’t like something, they simply won’t pursue it. If you show children - boys and girls alike - how technology can be enjoyed and fulfilling, without introducing gender roles, they’ll be more likely to consider tech as a career.
The key is to forget about gender, and start focusing on the exciting opportunities that choosing a career in STEM can bring about!
Sophie has a BSc (hons) in Web Design, and was the UK’s first female Drupal Grand Master (the highest recognition in Drupal development). Her talents have recently been recognised by The Drum who listed Sophie amongst their ‘50 under 30’ most influential women in tech, as well as by BIMA who included her in their Hot 100 list. She is a senior developer for Microserve and has worked on many of our most complex client projects.
Written by: Sophie Shanahan-Kluth, Senior Developer
Microserve is a Drupal Agency based in Bristol, UK. We specialise in Drupal Development, Drupal Site Audits and Health Checks, and Drupal Support and Maintenance. Contact us for for further information.
Get ready for the fourth part of our job check series: This time, Christian Flach explains what it’s like to work as a Community Manager, what he appreciates about his job and which challenges he has to face.
In Gizra, we run an unusual stack. Drupal, our bread and butter, serves as the backend and is complimented by Elm for the front end, and as of recently Yesod - a Haskell framework.
Before Yesod, we were running NodeJs as our proxy server for light tasks or real-time messages.
In this post I’m not going to try and present strong points on why you should adapt this stack, but rather share with you the unique path we are paving.Elm
Elm was my first dip into the functional programming (FP) world. I recommend starting from there. It’s way more gentle than Haskell, and it has, of course, one important advantage - it helps you build rock solid, crazily fast, joy-filling, web apps.
Maybe this post and video will get you excited as well.Gentle Intro to Haskell
A good way to start explaining what’s so special about Haskell is to dive directly into Haskell. While PHP is defined (by some) as a “productive” language, Haskell is often blamed (by some) as being an “academic language”. Both statements are probably wrong.
Often when mentioning Haskell, we talk about the compiler and the type system. They are truly marvelous tools. For the type system, I think the Elm post I lined above should be enough to get the hang of it. But I’d like to continue and reveal a bit more by highlighting mini examples on how Haskell makes us approach development tasks differently.Lists
Below are examples from the REPL (the interactive shell for Haskell)> [1, 2] ++ [3, 4] [1, 2, 3, 4]
What we have here are two lists of integers that are appended to each other. A list of integers is represented as [Int] in Haskell. The ++ is the operation that causes those two lists to be grouped into a single one.
Haskell comes with some handy shortcuts.
Do you want to kick ass in the digital environment? We thought so! Our cheeky monkeys have been helping clients do just that since 2008—longer than many digital agencies have been around.
Our work speaks for itself, but we really like it when our clients speak on our behalf. Recently their input was in large part responsible for helping us make a list of the top digital agencies in Canada, compiled by Clutch, a B2B market research firm based in Washington, D.C.
We earned our spot on Clutch’s “Leaders Matrix” based on our previous work, market presence, and most importantly, client reviews conducted by Clutch analysts. Below are a few comments from some of the people we’ve worked with:
As you can see we've put a fresh coat of paint on Drupal.org - but the changes run below the surface. This latest iteration of the front page brings the key concepts of our design system to the forefront: Clean, Modern, Technical.
This change also brings new editorial tools for Drupal.org content editors. The new home page provides us more flexibility with content and presentation, and so you'll see more frequent updates, more information about DrupalCon, and more editorial flexibility on the home page than you've seen in the past. These tools are also helping us to build cleaner, modern landing pages - like you've just seen with our Fall Membership Campaign.
We've previewed this work with several key members of the community and the board, and we want to say thank you to everyone who's given us their feedback on this first step for our new home page. We also want to give an extra special thank you to dyannenova for her contributions to this effort.
This is just the beginning - very soon we'll have a new visual look for the case studies that are featured on the home page, and then shortly after that we'll begin promoting solutions to Drupal evaluators in specific industries, like Higher Education, Media & Publishing, and Government.
If Drupal.org is the home of the community, than the front page is our front door. We want to welcome new users and evaluators of Drupal, highlight the project's strengths, and promote news and happenings from throughout the ecosystem.
We hope you like the changes, and we think you'll like the upcoming iterations even more. We'd love to hear your feedback!
Check out our video series on component-based theming in Drupal 8. […]
Drupal 8.1.10, a maintenance release which contains fixes for security vulnerabilities, is now available for download.
See the Drupal 8.1.10 release notes for further information.Download Drupal 8.1.10
Upgrading your existing Drupal 8 sites is strongly recommended. There are no new features nor non-security-related bug fixes in this release. For more information about the Drupal 8.x release series, consult the Drupal 8 overview.Security information
We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.
Drupal 8 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.Bug reports
This is the final security release for the 8.1.x series. Future maintenance releases will be made available in the 8.2.x series, according to our monthly release cycle.Change log
Drupal 8.1.10 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisories:
To fix the security problem, please upgrade to Drupal 8.1.10. (Sites testing the 8.2.x release should update to 8.2.0-rc2.)Update notes
See the 8.1.10 release notes for details on important changes in this release.
This is the final security release of the 8.1.x series. Sites should prepare to update to 8.2.0 following this release.Known issues
See the 8.1.10 release notes for known issues.
Two years ago, I started to be interested in API-first designs. I was asked during my annual review, “what kind of project would you like to be involved with, this next year?” My response: I want to develop projects from an API-first perspective.
Little did I know that I was about to embark on a series of projects that would teach me not only about decoupled Drupal, but also the subtleties of designing proper APIs to maximize performance and minimize roundtrips to the server.Embedding resources
I was lucky enough that the client that I was working with at the time—The Tonight Show with Jimmy Fallon—decided on a decoupled approach. I was involved in the Drupal HTTP API server implementation. The project went on to win an Emmy Award for Outstanding Interactive Program.
The idea of a content repository that could be accessed from anywhere via HTTP, and leverage all the cool technologies 2014 had to offer, was—if not revolutionary—forward-looking. I was amazed by the possibilities the approach opened. The ability to expose Drupal’s data to an external team that could work in parallel using the front-end technologies that they were proficient with meant work could begin immediately. Nevertheless, there were drawbacks to the approach. For instance, we observed a lot of round trips between the consumer of the data—the client—and the server.
As it turns out, The Tonight Show with Jimmy Fallon was only the first of several decoupled projects that I undertook in rapid succession. As a result, I authored version 2.x of the RESTful module to support the JSON API spec in Drupal 7. One of the strong points of this specification is resource embedding. Embedding resources—also called resource composition—is a technique where the response to a particular entity also contains the contents of the entities it is related to. Embedding resources for relationships is one of the most effective ways to reduce the number of round trips when dealing with REST servers. It’s based on the idea that the consumer requests the relationships that it wants embedded in the response. This same idea is used in many other specifications like GraphQL.
In JSON API, the consumer can interrogate the data with a single query, tracing relationships between objects and returning the desired data in one trip. Imagine searching for a great grandparent with a genealogy system that would only let you find the name of a single family member at a time versus a system that could return every ancestor going back three generations with a single request. To do so, the client appends an include parameter in the URL. For example:?include=relationship1,relationship2.nestedRelationship1
The response will include information about four entities:
- The entity being requested (the one that contains the relationships).
- The entity that relationship1 points to. This may be an entity reference field inside of the entity being requested.
- The entity that relationship2 points to.
- The entity that nestedRelationship1 points to. This may be an entity reference field inside of the entity that relationship2 is pointing to.
A single request from a consumer can return multiple entities. Note that for the same API different consumers may follow different embedding patterns, depending on the designs being implemented.
The landscape for JSON API and Drupal nowadays seems bright. Dries Buytaert, the product lead of the Drupal project, hopes to include the JSON API module in core. Moreover, there seems to be numerous articles about decoupling techniques for Drupal 8.
But does resource embedding offer a performance edge over multiple round-trip requests? Let’s quantitatively compare the two.Performance comparison
This performance comparison uses a clean Drupal installation with some automatically generated content. Bear in mind, performance analysis is tightly coupled to the content model and merits case-by-case study. Nevertheless, let’s analyze the response times to test our hypothesis: that resource embedding provides a performance improvement over traditional REST approaches.
Our test case will involve the creation of an article detail page that comes with the Standard Drupal profile. I also included the profile image of a commenter to make things a bit more complex.undefined
In Figure 1, I’ve visually indicated the “levels” of relationships between the article itself and each accompanying chunk of content necessary to compose the “page.” Using traditional REST, a particular consumer would need to make the following requests:
- Request the given article (node/2410).
- Once the article response comes back it will need to request, in parallel:
- The author of the article.
- The profile image of the author of the article.
- The image for the article.
- The first tag for the article.
- The second tag for the article.
- The first comment on the article.
- The author of the first comment on the article.
- The profile image of the author of the first comment of the article.
- The author of the first comment on the article.
- The second comment of the article.
- The author of the second comment of the article.
- The author of the article.
In contrast, using the JSON API module (or any other with resource composition), will only require a single request with the include query parameter set to?include=uid,uid.field_image,field_tags,comments,comments.uid,comments.uid.field_image
When the server gets such a request it will load all the requested entities and return them back in a single swoop. Thus, the front-end framework for your decoupled app gets all of its data requirements in a JSON document in a single request instead of many.
For simplicity I will assume that the overall response time of the REST-based approach will be the one with the longest path (four levels deep). Having four parallel requests that happen at the same time will not have a big impact on the final response time. In a more realistic performance analysis, we would take into account that having four parallel calls degrades the overall performance. Even in this handicapped scenario the resource embedding should have a better response time.
Once the request reaches the server, if the response to it is ready in the different caching layers, it takes the same effort to retrieve a big JSON document for the JSON API request than to retrieve a small JSON document for one of the REST requests. That indicates that the big effort is in bootstrapping Drupal to a point where it can serve a cached response. That is true for anonymous and authenticated traffic, via the Page Cache and Dynamic Page Cache core modules.undefined
The graphic above shows the response time for each approach. Both approaches are cached in the page cache, so there is a constant response time to bootstrap Drupal and grab the cache. For this example the response time for every request was ~7 ms every time.
It is obvious that the more complex the interconnections between your data are the greater the advantage of using JSON API's resource embedding. I believe that even though this example is extremely simple, we were able to cut response time by 75%.
If we now introduce latency between the consumer and the server, you can observe that the JSON API response still takes 75% less time. However, the total response time is degraded significantly. In the following chart, I have assumed an optimistic, and constant, transport time of 75 ms.undefined Conclusion
This article describes some sophisticated techniques that can dramatically improve the performance of our apps. There are some other challenges in decoupled systems that I did not mention here. If you are interested in those—and more!—please attend my session at DrupalCon Dublin Building Advanced Web Services With JSON API, or watch it later. I hope to prove that you can create more engaging products and services by using advanced web services. After all, when you are building digital experiences one of your primary goals you should be to make it enjoyable to the user. Shorter response times correlate to more successful user engagement. And successful engagements make for amazing digital experiences .
As we are ramping up to work on significant user improvements for Drupal 8.3, one of the key areas of progress could be with media management user interfaces and features. For that to happen, we need to agree on what we are going to work on and then have people to implement it. The Media in Drupal 8 Initiative plan is being formed and is open for feedback now if having better core media support is near and dear to your heart. Please review and post feedback on the plan.
If you'd like to get involved with the implementation, you are more than welcome! The media team meets every Wednesday at 2pm GMT on IRC in #drupal-media.
Without doubt, the greatest resource for information about Drupal frontend issues is the DrupalTwig Slack. There are over 300 of the world's most well known frontend Drupal developers - Wim Leers, MortenDK, Mark Drummond, David Hernandez, and more - offering and receiving help all day every day. It's very rare that someone asks a question and doesn't receive a reply with a solution within a few minutes, or at the very least a conversation about why the issue might be hard to solve.
Embedding videos can be a tricky thing to do when it comes to both the web and different CMS's. When it comes to embedding videos in the content section - the body of the page - The Video Filter module offers an easy and great solution.
Basically, you install the module, configure it for the different text formats you want to use it with and then simply add the videos in the body text with a kind of shortcode or shorthand thingamajig.
In this video I'll go through what you need to know and how to get the videos to show in your content.
The Video Filter module only works as a text filter, so if you're looking for a solution where you can create embedded videos from a field of its own in Drupal, perhaps Video Embed Field could offer such a solution. (I'm just talking about Video Filter in this screencast.)
If you're following along at home, you may have seen that we recently made the move to Pantheon hosting. Last week during our maintenance window, Joe and I worked through our migration checklist, and officially moved the site over to our new host. The process had a few hiccups, but we thought it would be interesting to take a look at what went into our migration process. Hopefully sharing what went into our planning process, as well as what is in our pipeline for improvements now that we're on Pantheon, will help you if you ever find yourself facing a similar project.
DrupalCon Dublin is just a week away!! With all the excitement surrounding the event we often forget to look at key things to expect out of this event. What should one learn out of DrupalCon Dublin? Is it only for Drupal developers or should CEOs, Managers and owners attend? What’s the use of attending an event on OPEN SOURCE TECHNOLOGY? Is it useful for growth of businesses as well?
DrupalConsole RC-1 is close, is really really close, as close as DrupalCon Dublin, less than a week at least thats our goal.Where are we?
We accomplish a lot of changes during the last two months, and this is an overview of the milestones completed for RC-1 release.
* Languages separated from the main project.
* Core commands and features to be shared across projects.
* Main repo.
* New global executable.
The next step is to fix modules with current DrupalConsole integrations once RC-1 is released, this means next week during DrupalCon.
This is the list of the known contributed commands providing commands, we have identified and we are planning to help update and fix to be RC-1 compatible.
- Drupal Commerce
- Configuration Split
- Scheduled Updates
If you know of another module(s) with contributes command please let us know by commenting on this post or on this issue https://github.com/hechoendrupal/DrupalConsole/issues/2728Are we done and ready for the stable ?
Not yet, we are close and we will continue working to complete the stable release and you help us complete it. This is how you can help.Are you a business owner?
As a business owner has your company already leveraged the advantages of Drupal Console?. Will Drupal Console play a significant role in your business plan for your immersion in Drupal 8?
You can contribute to complete the Goals for our 1.0.0 stable release by assigning 1 or more of your resources to work in office hours to complete the pending tasks.Are you an independent developer?
As an independent developer, you can help us by allocating some hours. We always have issues to resolve and none of them are rocket science!Are you going to DrupalCon?
Feel free to join us during the sprints, you can help us in several ways:
- Fix current modules with integrations.
- Fix bugs and improve the project.
- Write an integration for a contrib module.
- If you know how to write test for Drupal 8, we really need your help.
Do not miss the DrupalConsole sessions Enzo and I will be presenting
Do not miss the Community Keynote enzo will be presenting
We’re proudly sponsoring the Women in Drupal event at DrupalCon Dublin 2016. This prompted me to reflect on our own track record on employing and advancing women.
Of course our own house is in order. Right?
No, it is not.
Including our current hiring round, in our team of 40 people:
- 0% of our four most senior posts are held by women
- 10% of our full leadership team is made up of women
- 20% of our developers are women
- 30% of our overall team are women
I would describe our approach to creating a representative, safe and welcoming workplace that facilitates everyone being able to thrive as ‘well intentioned’.
No one in the team has raised any concerns about our approach.
I also haven’t spent much time ensuring that we understand how to address these complex issues. Or that we’re serious about rooting out the more insidious aspects of discrimination.
So - passive, ill-informed and well intentioned.
I’m a white male, in an industry dominated by white men and I’m the most senior person in the organisation. An organisation where the four most senior roles are held by white men.
In what scenario would a feeling of being ‘other’ likely occur for me? Let alone the reality that I have personally experienced discrimination?
So it’s impossible that it’s only women that we’re failing
By failing to engage with and acknowledge our bias, we’re not actively including all people across differences in sex, age, gender, race, sexual orientation or disability. I’m pretty sure therefore our recruitment process needs deeper thought.
Organisationally we’re likely to reveal our implicit bias through our lack of representation of some communities at a senior level - test yours here.
And the likelihood of that being a perpetuating factor for our failure to represent the wider community within the organisation seems high.
A lack of awareness of this bias is also likely to hurt our work - our UX, design and development practices all require empathy and different perspectives to deliver results.
And that means we’re not proactively developing a culture that ensures that everyone knows they’re welcome, that they will be respected as themselves, that they can thrive and belong here. How will they answer the question ‘Can someone like me be successful here?’
For example, our lack of diversity at a senior level means that we don’t interpret the signals the way that some people might about our recruitment proposition.
Aside from the fact this feels ethically wrong as a state of affairs, this every day passivity is harmful in terms of the following:
- Our ability to have a truly diverse workplace where everyone feels welcome
- Our ability to attract the widest range of potential candidates
- Our ability to progress people to a senior level
- Our performance as a company
Let’s start closer to home than the pipeline issue
The industry approach has been on occasion less than insightful: ‘if they don’t apply for our jobs, then we can’t hire them, so what can we do?’.
It’s a pipeline problem that’s not our fault, right?
This ignores the appalling discrimination that people have experienced in the industry. Which, for example, contributes to a shameful retention rate of women who have chosen tech as a career.
And if you can’t see people like you succeeding in the industry how attractive (or safe) would it feel as a career choice?
Of course it’s important and positive that the industry backs initiatives that help support poorly represented communities. But we shouldn’t ignore the inconvenient and more directly addressable truths closer to home.
Do we really need to hear what another white man thinks about equal representation in tech?
On the one hand, no. The tech industry is disproportionately full of our opinions on this topic already. But, as others have pointed out, under-represented communities can't fix this on their own - those in positions of power need to make a stand alongside them.
The target audience for this post is really other people in positions of privilege and power who, like me, somehow hadn’t woken up to the fact that being passive and ill-educated on this issue perpetuates it. That it may be painful and uncomfortable to acknowledge that you may have passively perpetuated discrimination within your organisation. That you might need to challenge your thinking.
If you disagree with a specific point is it OK to just disengage? Or could you take positive steps on the areas that do resonate?
How are Deeson going to do better?
I’m going to make it a standing issue on our leadership team’s agenda so that we can monitor progress and maintain an active discussion. We aren’t going to get better overnight.
We’re going to immediately:
- Begin annual salary audits to check for bias and rectify imbalances
- Report on our progress when we do our quarterly planning
- Implicit bias training for everyone
- Stop attending conferences that don’t have a credible Code of Conduct
- During hiring, take a more nuanced view on whether a developer has made open source contributions
- Stop participating in all male conference panels
- Improve our Careers page, including clarity on parental leave
- Stop asking for previous salary during hiring - it can perpetuate pay inequality
- Create dialogue and feedback channels within the company to offer better support
- Stay informed and signpost groups working in the industry
Can digital agencies and the Drupal community do better?
I think they can. I've worked in the UK's digital agency sector since 2001 and I've been involved with the Drupal community since 2007. The impression I get is that inequality is a problem across the board.
The Drupal community is at least doing its best to redress imbalances - there are initiatives that support poorly represented communities in STEM subjects through coding clubs, ambassadors and advocacy, for example. But is it enough, and is it working?
Digital agencies, perhaps because they're less in the public eye, are lagging behind in terms of these initiatives. As we've seen, CEOs, CTOs and founders are largely oblivious to their own white male privilege, and this needs to change.
So, how should this change come about, and what is your organisation doing to increase diversity?
I'd love to hear your opinions on this, whether you work in digital or you're a member of the Drupal community. Leave a comment below this piece, or tweet me at @timdeeson
Background and research
I couldn’t have written this post without the material I have referenced and for the wider reading that made me realise the extent of the issue. The material they have written has been written for no personal gain by people who have had negative personal experiences of the tech industry. They bear the disproportionate burden of both suffering the consequences of these issues and making significant efforts to improve the situation for others.
Thank you to Lisa Armstrong, our acting Marketing Director, for her support with the post and for our conversations that prompted me to realise that not everyone has the luxury of my ignorance. Her current experience as a startup founder in the fintech field has not always been positive.
Also, in order to develop something more likely to be helpful rather than harmful I approached Meri Williams. I took part in a training workshop she gave a few years ago, the depth of her expertise on managing people at work taught me lessons that I use every day. She turned down paid consultancy but generously offered to discuss writing this post with me pro-bono. What’s useful in this post is likely to be there through her leadership and the writing of others that I’ve mentioned. She has another workshop coming up soon.
And thank you to the team at Deeson for their thoughts and input.
For a recent website I worked on, the client wanted search results to be grouped by content type, and also wanted to control which content type results were displayed first, second, and third. While you can get most of the way there in terms of sorting search results using Views, if the desired order of the content types doesn't luckily correspond to some kind of alphabetical sorting of the content type's names, you'll need to do a little configuration and custom module work to make this happen.
I will walk you through how to do this using a vanilla...Read more
DrupalCon Dublin includes a full track of core conversations where you can learn about current topics in Drupal core development, and a week of sprints where you can participate in shaping Drupal's future.
Also be sure to watch Dries' keynote for ideas about Drupal's future!