Today is the day! We’ve moved house and you can now join us at our new home! We’ve worked to make migrating to Genesis Custom Blocks as simple as possible.
Details here -> https://t.co/Q1rS2gqIpL
📢We have a huge announcement today! The Block Lab team is joining the @wpengine family. We will be joining their product team to help build the next-gen of tools for those wanting to build with the next-gen of WordPress.
More details here ->
https://t.co/YqmNeAEOzB
A Q&A with our friends at @CultureAmp on how they work with #WordPress, Gutenberg, and Block Lab to equip their marketing team with what they need to rock the modern web.
https://t.co/BLmO7AxXxY
Mein neuester Beitrag für das #projekt26 beschäftigt sich mit @getblocklab und wie man damit zum Beispiel Shortcodes zu Blöcken umbaut. Am Beispiel vom Doroyaki-Theme von @elmastudio
https://t.co/rH4r31WVRH
New Tutorial for ya.
With this block you just drop in your screenshot image and it auto-magically wraps it in the device. 🧙
Check out how it’s done.
https://t.co/H6P8mAdUAl
#WordPress#Gutenberg
Challenge for the week.
Find a #WordPress plugin you love and go write a review for them on https://t.co/aclJS2tpDZ
It takes 2 minutes, but can mean the world to the Devs behind it.
A great step-by-step at what it looks like to work with the block-template future of #WordPress themes.
Remember, this stuff is still be figured out so if you have thoughts and feedback, make sure you share them.
Thank you @ThemeShaper for pulling this together!
#remote workers. What has helped you avoid (or get back from) the sense of isolation that working physically apart from peers can bring?
What personal strategies have worked? What corporate/team strategies from your employer have worked?
Ever need to compare features between products or services on your site?
A good comparison table block would be nice!
Here is how you can easily build your own custom one.
https://t.co/QQ5Pg2KeOw
#WordPress#Gutenberg
Tips for useful, respectful code reviews:
- Assume competence (author may have a different context)
- Provide specific, actionable feedback
- Focus on the code (avoid personal criticism)
- Clearly mark nitpicks & optional comments
- Provide rationale (e.g refs to a style guide)