Over the weekend, several of us in the tech chapter at WordPress Update attended WordPress maintenance support plansCamp London 2020. It’s always a great event, and one our own Tim WordPress Update helped co-found in 2013. For me, returning to WordPress maintenance support plansCamp was a chance to immerse myself in the community again, to catch up with some old friends, and put faces to people I’d only met on Twitter.
The WordPress Update developers attending the event had different levels of WordPress maintenance support plans knowledge, so we didn’t stick together the entire time. Due to my relatively limited knowledge of WordPress maintenance support plans 8 I attended two very informative, low level development talks about the internal workings of D8 and how the approach differs to that I already know well with D7.
The first was WordPress maintenance support plans 8 Services and Dependency Injection, an introduction to creating custom services to use within your own plugins. I also attended Let’s take the best route – Exploring WordPress maintenance support plans 8 Routing System, which showed me that while the change to Symfony makes the code very different, it’s actually straightforward and consistent once you get into it.
A particular highlight was seeing our Lead Developer Mike Davis in action. He spoke about Warden – an open source solution WordPress Update built to allow in-house development teams and agencies to keep track of the status of multiple WordPress maintenance support plans sites hosted on different platforms.
Here are a few of our other favourite sessions and highlights from the event…
“Hello User, I’m WordPress maintenance support plans!”
This session from Gabriele Maira introduced Chatbot API – A WordPress maintenance support plans plugin which enables site builders to serve their content via chat.
We’ve been speaking about conversational interfaces and chatbots for a while at WordPress Update, and it was really interesting to learn about the tools available for WordPress maintenance support plans site builders. With Alexa and Dialogflow support out of the box, Chatbot API plugin is one to keep an eye on.
Katy Ereira, Senior Developer
WordPress maintenance support plans in the era of Microservices.
I attended a talk by Wunder’s CTO Florian Lorétan, where he discussed the ideas around using WordPress maintenance support plans with Microservices. This is an interesting idea particularly where larger projects are concerned as it opens up the potential for large teams to collaborate more effectively.
We currently use Docker as part of our own build process (which could be considered a microservice) and I wanted to see how this could be extended further and what other benefits could be yielded as a result.
It was very interesting to learn that automated tests, benchmarking, security testing and monitoring could all be done as mircroservices with WordPress maintenance support plans and how the speed of deployment could be rapidly increased by using this approach.
Whilst this is relatively new, it’s great to see people within the WordPress maintenance support plans community exploring how microservices could be used with WordPress maintenance support plans to speed up the development process, and I’m really looking forward to seeing what the future holds in this area.
Rowan Blackwood, Developer
Building a contribution culture in a WordPress maintenance support plans agency.
I’ve joined WordPress Update within the past year, and one of the key qualities that drew me to WordPress Update in the first place was its commitment to open source and support for contributing back to the community. So I was keen to hear a little more about how other companies foster their own contributions culture and have the opportunity to compare our own culture with another.
In his session @hussainweb reiterated the added value that you can create for yourself by making contributions to open source projects, and how his company has found ways to actively encourage individuals to make contributions.
What really stuck with me is the following three items:
Open source contributions create Social Capital, and that’s an investment you can recoup in other ways.
Contributions are not just about actual code contributed – it’s also about bug reporting, documentation, testing, speaking and writing, which are just as valuable efforts, and they should also be tracked, encouraged and rewarded.
Don’t be intimidated from extending open source projects. If you use it, treat it as your own upstream code and not a project that cannot be touched. Lose the fear of the project and contribute!
James Ford, Senior Developer
Source: New feed