We've been working on a large WPML implementation lately with quite a few translated pieces of content. If you haven't used WPML before, you might not know that changing the contents of a page that's already been translated marks the other translations as out of date. This means WPML wants you to update them to reflect the content changes you made on the English page.
Alpha Particle is expanding and looking for a WordPress Developer who can tackle some of our production WordPress work. This means building custom themes (either completely from scratch or Child Themes) as well as plugins to fit our client's needs.
WordPress is a fantastic way to start learning to code. You rarely need to learn more than one new thing at a time in order to get building, and you can always find one new skill to learn (or improve) with each new project.
Deployment is the stage of the software development life cycle most likely to cause problems. Even if your deployment pipeline is perfectly set up, it's the stage of the development process where any bugs you didn't catch while building or during QA get shipped out to your end users. This might mean you need to roll back, or at the very least track down the problematic deploy at some point in the future.
the_field calls just the same as you always have. The code to register a block looks something like this:
The team behind the newly-formed non-profit The Snowball Project came to us with an idea. They wanted to build a web application that used peer-to-peer influence to encourage the unregistered to register, and the non-voting to vote. They knew what they wanted, but they needed a "virtual CTO" to help them make decisions and an engineering team to make those decisions happen. That's where Alpha Particle came in.
You may have heard that WordPress has a brand new block editor that completely transforms the writing and content management experience. However, there are plenty of sites that aren't ready to move their entire base of content over to the new editor. This could be because not all of their plugins are compatible with the new editor or their editorial team isn't ready to have a totally new editing experience.
Manually built metrics in Nova don't support the time-range dropdown that the Nova helper functions support, and the Nova helper functions don't handle
many<->many relationships well (at least not the way I needed).
I've been using the Block Editor since it was released in WordPress 5.0, but as I've been creating and updating more content, I've found one strange user interaction that I didn't know how to get around. When I move my mouse up to the top right of the screen, the Update/Publish button is very close to the Admin Bar, which has a hover state. For example, if I move my mouse just a couple pixels too far, I get the hover state for the logged in user rather than being able to click the Update button.