I am often asked by people looking for work if I know of any one that is hiring.

I am also often asked by people who are hiring if I know of any Drupal developers looking for work.

The answer to both is usually "Yes". I seem to know lots of people in the Drupal community and am trusted enough by them to let me know if they are looking for a new job/contract (often in private so their current employer doesn't know).

Last week I sent contact details of two very good Drupal developers that I know personally to a recruiter. I know at least one of them is being interviewed this week. But then I had a brainwave! Why am I doing the work of a recruitment agency for free, especially when I know how much recruitment agencies charge for their services.

A new Drupal recruitment agency?

My solution? I am going to charge people who are hiring, just like a recruitment agency would, for my recommendations. Except, my cost is going to be about 90% cheaper than a recruitment agency. Why so cheap? The price I am charging is a very fair price for basically telling someone that someone else is available for work.

I am calling this service "Available Drupal Developers". If I was cool, I'd call it ADD or something and set up a website and a CRM, and get some merch and hoodies, and blah, blah, blah. But I'm not cool, so I am keeping it all in a spreadsheet for now and a landing page on this humble website.

How much does it cost?

I've a simple pricing model. If you hire a developer that I recommend, the cost will be €1,500 per developer. No deposit, no recurring charges, no "18% of their first year's salary", just a simple one-off fee of €1,500 (ex-VAT, if applicable). If you are a developer, there is no charge.

Is there a vetting process

I'm keeping this simple. I'm only prepared to recommend people who can pass this threshold:

1. I know you personally (have worked with you, worked on issues together on Drupal.org, met at conferences, etc) and/or
2. I can validate your work from open source sources (blog posts, presentations, Drupal, GitHub)

Take my money already, Mark

If you are looking to hire a Drupal developer, get in contact and I'll see if any of the 40 people I currently have on my list would suit you (that 40 will be significantly reduced soon as I make my way through vetting people).

I'm available for Drupal work

If you are a Drupal developer thinking of changing jobs, fill out this form and I'll see if I can recommend you to someone suitable.

Need LocalGov Drupal services? Give Big Blue Door a shout.

Meetings and Meet-ups

1. Merge Tuesday: Great meeting today discussing getting a stable release of LGD microsites released, and also our process for adding new features to LocalGov Drupal.
2. Government Design System meetup: This was my third time representing LocalGov Drupal at the Government Design System meetup. This time we talked about performance measurement - how do we measure the success of our design system.
3. Community Meetup: We had a very informative meetup this week, discussing the new Job Vacancies module as well as myself and Finn presenting our "Live Preview" work.
4. Tech Group Drop-in: As usual, a very lively chat. This week Netcall integrations and SSO were on the agenda.

Code Contributions

I created a LocalGov Live Preview module to work with the microsites platform, which took up all my time this week, and encouragingly got a great response at the community meet-up. 

I think this is going to be a game-changer for how councils and others put their microsites together. No more "make a change, click save, refresh page, rinse, repeat". Now you can see all the changes happening live.

Here's a video walkthrough of it:

Last year I made a module as a proof-of-concept for live previews for LocalGov Drupal Microsites. Today, I spent the day taking it out of "proof-of-concept" mode and getting it into shape as a fully functional module.

I'm pretty happy with the results so far. I'll keep refining it a bit more as the week goes on.

Here's a short intro to it.

Need LocalGov Drupal services? Give Big Blue Door a shout.

Meetings and Meet-ups

1. Merge Tuesday: Another productive meeting. I'm especially happy with the merge to localgov_paragraphs to add the new "Show all" accordions widget.
2. Content Group: We had a great chat about what people are enjoying about LGD - microsites, subsites extras, and replicate all came up. And a WHOLE LOTTA Love for Miro.
3. Tech Group Governance: Nice to get to this monthly meeting. Today we discussed stabilising microsites, preparing for Drupal 11, and the community fund.
4. Tech Group Drop-in: Lots (and lots and lots) of talking about maps, maps, and mapping.

Code Contributions

1. We're preparing for Drupal 11 support, so the week began with reviewing/approving PRs for some of the items that I maintain - LocalGov Sa11y, LocalGov Scarfolk, LocalGov Base, etc.
2. Most councils want a "Feedback form". Those small forms that say "was this page useful?" and ask you to give some details if it wasn't. Here's a PR to create that feature. Remind me to stop creating forms, they're tricker little things.
3. I love when we get accessibility issues submitted for LocalGov Drupal. It means when we fix them, we make the web better for everyone. Bisd posted one recently about our "Read more" for service status pages not being translatable. After a little bit of investigating, it turns out it was translatable, and we also have a corresponding aria-label to be more expressive for people using assitive technology.
4. The "move components to single-directory components" issue is moving along very nicely. Just one tiny comment or two from me to Christopher and then I think we're good to go.
5. We've been discussing our approach to checking if a region is empty before rendering it for the past few weeks. What we currently have might has an effect on caching (it's a long-running Drupal core issue too). But any solutions to it throw up other issues as well. I tried, and have nearly succedeeded, in a CSS-only answer to it, but I'm stumped on the if/else clauses for sidebars in the page.html.twig file. If you'd like to contribute to the conversation, please do.
6. Will mentioned that it might be helpful for editors to more clearly see what heading levels that have used in the wysiwyg. I put together a quick proof of concept to show how we could achieve this with just some simple CSS.
7. We have an open issue in the LocalGov Sa11y module to prevent sa11y from running on wysiwyg fields. After a bit of testing, it turns out it already does not run on ckeditor fields. It only runs on rendered content, not editing content, and only runs on the frontend, not while viewing an admin theme. And even testing it on the frontend by creating a comments field showed it was working as expected. We now no longer have this open issue.
8. Last week at the LocalGov Accessibility Meetup, Michael from Big Blue Door gave a really interesting talk about automated accessibility tools, which allow you to scan a page to automatically detect accessibility issues. One of the questions that came up was if you can scan more than one page at a time. I put together a demo repo of code to show how this can be done, then made a video to explain it, and a blog post too.

I've just started my own new agency. 

It's called The Confident, with a tagline "For those who demand the impossible". Yep, we're not afraid to take on extremely challenging projects and see them through to completion.

Starting off, we will have a hyper-focus on the Local Government market, specifically LocalGov Drupal. I see us as being complementary to the existing agencies in this space, offering 4 services:
 

1. Figuring out what a council wants for a new website or feature on an existing site.
2. Helping them source the best placed agency to work on this project.
3. Being a link between the council and this agency to ensure the project is a success.
4. Co-pitching with other agencies to win big contracts

If you think any of the above could be of interest to you, I'd love to have a chat.

As well as the above, we have a line of products that we plan on launching. The first of which will be coming next week. Stay tuned!

The Confident

Need LocalGov Drupal services? Give Big Blue Door a shout.

Meetings and Meet-ups

1. Merge Tuesday: Lots of talk this week about supporting Drupal 11 and what we need to do for our automated tests to work for it, while also supporting Drupal 10.
2. Accessibility Meetup: Michael from Big Blue Door gave a really interesting presentation on the tools he uses for checking the accessibility of their websites, notably Axe, Wave, and Lighthouse, as well as manual testing and keyboard navigation testing.
3. Tech Group Drop-in: We had two big juicy topics today, nice to get down and dirty with tricky stuff - media downloads and empty regions + caching.

Code Contributions

1. Christopher had a really nice PR created for me to test on Monday morning. The PR would allow our accordion patterns to have more than one item open at a time and also add a toggle to 'Show all/Hide all' accordions. Each of these features can be turned on/off for individual accordion containers. Very nice.
2. Lee suggested that the LGD Dashboard I built a couple of weeks back should have a link for "Good first issue", so now it does.
3. We've had an issue for a while now about removing the 'Files' tab from the list of tabs you see on the admin/content page. A lot of content editors are clicking on it expecting that's where their "Files" are, which it is, except what they are actually looking for is their "Media" items. We had a PR to remove this tab altogether, but that will break existing sites, and some users might want to visit it. So. we now have a PR to set the "Files" tab to be a sub-item of the "Media" tab. That makes sense I think.
4. I had forgotten we had a module called "LocalGov Extra Layouts". Justine created it originally when she needed a 4-column layout, but we then added 4-column layout to the LocalGov Paragraphs module. The other layouts in the LocalGov Extra Layouts module are probably still useful to other councils - 33:66, 66:33, 2x2x2x2, etc. I did some work on these to close out an issue created by Andy saying the module had not been added to packagist (it is now, along with its own shiny composer.json file) - this was the issue that brought this module back to my eyes.
5. Then I did some work to tidy up the code - fix the package name, tidy up the CSS, remove the redundant template, etc.
6. LocalGov Extra Layouts had no release branch and no tests, so I created an issue to fix this and then a PR for it to use the shared workflows approach we have.
7. What module would be complete without a README.md? Well, here's a PR for LocalGov Extra Layouts to now have one.
8. Issue number 1 for the LocalGov Drupal Dashboard was to create a button that would copy the clone command for a repo to your clipboard. And now we have it.
9. Whilst there, I did a little clean up of the table layout and the general cards layout.
10. I had a good chat with Sarah from Blackburn with Darwen Borough Council and we think we've discovered a bug in the path alias settings for publications. I haven't got it fully uncovered yet, and I certainly don't have a fix for it yet, but I've some notes written up about it, and we'll get it solved from there.
11. Following that call, I put together a video to demonstrate the bug. Hopefully that will help us to get a fix for it quickly.
12. Zach posted a PR to link the SVGs on publication cover pages to their respective files. We got it reviewed and merged.

Need LocalGov Drupal services? Give Big Blue Door a shout.

Having spent most of last week's time working on the new LocalGov Drupal Dashboard, I had a bit of a backlog of issues, PR, notifications, etc on GitHub to read through, respond to, update. Not the most glamourous part of open source development, but you need to keep on top of the repos you are the maintainer for. And then ... a gem pops up. Christopher proposed a new module, built it, and put it on GitHub for us to review. The module is a jobs listings portal, something we probably should have built before now, but it's never too late.

Meetings and Meet-ups

1. Merge Tuesday: We spent most of the MT time reviewing the 13 PRs I opened for the $is_syncing issue that I spent half of Monday working on.
2. Tech Group Drop-in: This was a really juicy meeting this week, discussing Big Pipe/Cachability/Empty Regions/Supported CSS ... and some other items that were a little less taxing on the brain.

Code Contributions

1. We have much better tabbing order now for keyboard users when tabbing from the services menu toggle to the services menu. Now when you get to the last item and click tab, it will tab back to the main menu area. Previously it was tabbing to the main content area. Better accessibility is better for everyone.
2. Sticking with the theme of accessibility, Maria posted an issue demonstrating that headings in the footer regions were black on a dark grey background, failing contrast conformity for WCAG guidelines. So I created a PR to add variables for headings in footer regions, and we can then easily set these in our variables.css files for --color-pre-footer-heading, --color-footer-heading, and --color-post-footer-heading.
3. Sometimes reviewing PRs is fun, for example when you get a MEGA pull request to update the docs site from VuePress 1 to VuePress 2. Thanks to Lee for creating this PR, it's not one I was relishing creating. 🙂
4. Keelan opened an accessibility issue over a year ago where JAWS screenreader was reading out the decorative ">" symbol in our start buttons. We couldn't reliably reproduce/fix it at the time, but thanks to the nifty new CSS "alt text" property for the CSS "content" attribute, we now can. I created a PR for it, hopefully that's one more accessibility fix we'll have in our codebase soon.
5. We've had an issue pop up a few times recently with config being imported and install hooks being run at the same time causing issues. We figured out it's because we are not sufficiently checking to see if config is being imported before we do our manipulations. Stephen created an issue for this, and then I created 13 pull requests to fix the issue everywhere it might arise. This was quite boring, but necessary.
6. Erik posted a whopper of an issue, in great detail, showing some shortcomings we have in LocalGov base for trying to detect if a region is empty or not before we render it. We're using the same approach we created for the Umami theme in Drupal core, but no matter what you do something has to give - either we lose caching on some blocks, or we lose the ability to use Big Pipe on others, etc. I'm not sure exactly how we'll solve this, but I'm really looking forward to the conversation. Perhaps you can jump in to it too here.
7. I've been making some moves to try standardise some of our components. The first I've been tackling is our "Previous/Next" component. We use the same thing on blogs, step-by-steps, etc but have different templates for them all. I have a number of them now using the same template. Thanks to Christopher for creating a PR to add publications prev/next to the list, which I reviewed and merged.

I had an issue today where Google Tag manager wasn't loading on a site for me on a Drupal site. I checked the settings over-and-over again, but couldn't see any issue.

Eventually I realised that we were missing the hostname. How did I miss this? Well, the hostname field had a placeholder which was exactly the value of the hostname needed, so it actually looked like it was filled in and the field value couldn't be changed (like a disabled field)

Here's an example of where placeholders can be a bad UX pattern. Maybe if the placeholder said "Add hostname here", it might be better. But again, it's not actually needed since the form label says "Hostname" and the description under the field tells me what I needed to do.

How did I find out that it was a placeholder and not an unchangeable value? When I tried to save the page after changing a different value, the page wouldn't save. Checking the browser's console told me "The invalid form control with name=‘hostname’ is not focusable."

Not a very helpful message but at least it inspired me to try to click on the field and then "Hey, presto!" the default value disappeared (since it was a placeholder, not a default value), allowing me to enter the hostname, save the form, and save the day!

I finished up last week with the HTML for the message being set in the navigation menu block, via a preprocess hook.

Ivan, another co-maintainer of the Umami profile, had a suggestion that we hook_preprocess_layout in stead, so I've updated the MR to do just that. 

While there I created a new library demo-profile-warning and am using that to style the warning message.

Hopefully that's enough to start moving that issue forward, so I can then get back to the original issue which started all this, removing toolbar and enabling navigation module in Umami.

As well as the above, Ivan also has a really interesting MR in development to use Web Components for rendering the status messages in Umami. I gave that a review, I think I'd love to use it, so am looking forward to it being completed and merged.

Need LocalGov Drupal services? Give Big Blue Door a shout.

Meetings and Meet-ups

1. Merge Tuesday: We had the usual people in attendance, and some interesting conversations about running tests against both LGD and microsites by default so things we fix in LGD don't break something in microsites.
2. Tech Group Drop-in: We spent most of the time on this call today discussing how to create Drupal modules for people who were somewhat new to Drupal and did a deep dive into creating a content type with paragraphs fields to create a "School term calendar". Not what I was expecting from the meeting, but very energising to be part of it.

Code Contributions

I have been doing some pretty hard-core contributing to LocalGov Drupal over the past few months, thanks to the kind sponsorship of Big Blue Door. This week I decided to go a little bit easier on myself and have some light-hearted fun with an idea I've been toying around with in my mind for a few weeks.

The idea is to build a dashboard type website to list all the repos for LocalGov Drupal. Then create a card item for each repo giving a link to the repo, it's issues, PRs, and other stats. As well as that, I'd like to be able to quickly filter out repos, or sort them by "most open PRs" and things like that.

I spent a day making a start on this and got pretty far. I'll try get to more of it in the coming weeks. You can view the code for it on GitHub and check out the live website.

Update: people in LGD land liked the idea a lot, so I spent another half a day adding some requested features, such as

• Show all items as a grid
• Show all items as a list
• Show all items as a table
• Add links to all approved PRs
• Add links to all non-approved PRs

I'm really happy with how it's come on so far. And there's a lot of chatter about new possibilities for it. Hopefully this will be the start of a cool new Dashboard initiative for us.

One thing that might arise in the future and cause a definite need for this dashboard is if we move all our code to Drupal.org. We won't have an "Organisation" like we have on GitHub so this dashboard will give us the central focus for trying to keep track of 70+ projects.