With cutting-edge technology deepbase improves and automates business processes and strives to hit the sweet spot between engineering excellence and UX
We have some exceptional news today!
We are over the moon to announce the close of our $47M Series B financing, led by Mubadala Capital and HV Capital!
Read the article by @domangerer, our CEO and co-founder, about the financing. https://t.co/L2qDUDpSk0
I’ll be presenting @gitlab’s #vulnerability management tools in Zurich on the 27th of April. Looking forward to meeting you there 😍 It’s been soooo long since the last onsite #meetup. https://t.co/n9IMAK1pK1
Great news 🎉 We have been working on improving our deployment service lately.
Here are the results:
1. We can now handle 90x more concurrent deployments (yes, 90 times more)
2. Deployments are now up to 50% faster
3. Erroneous deployments are put in retry queue 😍
Coming soon: Core API for turning any Vue 3 component into a custom element.
Works with most Vue APIs including props, emits, and even provide/inject between nested Vue custom elements. Slots will render as native slot elements.
@storyblok helps developers and businesses around the world to shape a new web: more security, better #userexperience, leaner #apps, faster #performance. As an official solution partner, we're excited to enhance our clients' user experience with @storyblok's unique #headlessCMS.
We know how a CMS can become a make-or-break for content creation. 😏 That’s why we created our newly-launched marketing newsletter for editors & marketers with:
📣 Storyblok news
🛠 How-tos & updates
⌚️ Omnichannel & CMS insights
Stay tuned! ⤵️
https://t.co/P2UCPO6326
👩🚀 Ambassadors News 👨🏻🚀
Let us introduce you to @JulianDerungs a full-stack developer, creator of Nuxt Dynamic Components (https://t.co/39ueg63qfo) for Storyblok and an active member of our community.💪
We are happy & proud to have such a great & growing group of ambassadors.
Something that often catches people out is that (at least for now) Tailwind’s @apply feature cannot be used with certain class names, which is why it’s one of the lint rules we’re working on this week for the @code extension. Automatic quick fix included! 💡