orbit-model VS deno-mixed-runtimes

I've been working in Developer Relations now going on 5 years and I've seen a lot of attempts to measure the activities of DevRel teams. There is often a lot of ambiguity about how best to measure the work that DevRel does. Do you utilize the AAARRRP model from Phil Leggetter, the Orbit Model from the Orbit team, the traditional sales funnel or something else?

The Orbit Model community framework, around which Orbit is built, is an interesting read too: https://github.com/orbit-love/orbit-model

Number of Orbit level 1 users

It was not long before Orbit became visible on our radar. It promised not only a useful platform to deepen understanding of the community. It put forth an entirely new conceptualization of community-building. In fact, the platform -- the product -- only came after the ideation and thoughtful work of crafting the Orbit Model. Deliberate systematized methodologies don't usually take precedence in emerging start-ups. This was something different.

What is community love? We’re still big fans of Orbit’s definition for it. Love is a member's level of engagement and investment in the community. Someone with high love is highly active and plays key roles in the community, like contributing, moderating, and organizing.

I would strongly recommend thinking about other activities that your community members may take that is not tracked in Orbit. For example, newsletter or blog subscriptions. You can use Zapier to integrate activities from other tools, like your subscribers—which is a pretty highly weighted activity in my book. If you didn't catch that weighted reference, head back to the Orbit Model docs.

[2] https://orbit.love/blog/why-orbit-is-better-than-funnel-for-...

"Characterizing the developer journey as a linear funnel doesn’t really tell the whole story, as it’s essentially scoped to awareness and conversation — the journey is much more complex. I think onboarding to the community itself, retaining over time, and advocating for others to join, is a huge part of the journey... In this world, you want to understand how folks are engaging with the community as well as with the company/product, with product metrics (activation, adoption, etc) existing as second-order effects of the community. The Orbit Model, versus the funnel, tries to tell this nonlinear and comprehensive story."

To understand what Orbit as a platform is, it's important to first understand what Orbit as a _model _ is. The Orbit Model is a framework for building high gravity communities. A high gravity community is one that excels at attracting and retaining members by providing an outstanding member experience.

Re: your question in the post title I'd say yes, report to marketing because in the end the person(s) work on content and events - both marketing activities. You should also treat this person more like a product marketer where the metrics aren't black and white like those of a growth marketer. If you want to assign metrics as goals for someone in this role, this may give you some ideas: https://github.com/orbit-love/orbit-model. I don't want to assign lead number to a DevRel person.

This all is may not be the optimal option for some organisations. The BBC has gone down this route and for more inspiration, McDonald pointed to resources Begin to explore the option of FWA suitability.

[00:00:00] I'm Simon MacDonald the head of developer experience at Begin. And this is my super out of date website.

However, that is not the end of the story. Since then, many services have improved on AWS Lambda's model in ways like ease of use and performance. The first notable FaaS provider was Vercel (ZEIT Now at the time), which was released in April of 2016 and was a lot simpler to use than Lambda. Another selling point was that it integrated well with Next.js, a React framework made by Vercel. Other, newer services also try to be a lot easier, like Begin, although Vercel is still the most popular in that group.

TLDR: tutorial for setting up webhook based serverless AWS apps with Begin. all without managing AWS projects, IAM roles, or connecting EventBridge to a series of Lambdas.

Instead, we'll make it even easier and deploy it to Begin.com. First, push the Arc project to a new GitHub repository. Then head to Begin.com (and make an account if needed) to create a new app.

Begin.com has a generous free tier, so users do not have to worry about costs. But for those on the paid tier, we will soon make this feature available to all users of Begin. We hope that AWS will build this into the platform in a more usable way. Until then, we hope to relieve some of the fear of unexpected bills. If you want to build scalable web apps with Begin sign up for a free account today.

In this post, we will progressively enhance our personal website template to add dark mode functionality. If you don't already have a website deployed via Begin follow our personal website tutorial to deploy the template in 5 minutes, then come back here and get ready to enhance.

To create a Begin account, simply click the Login button on the Begin home page, authorize it with GitHub, and pick a username. That's it!

The final step is to deploy this application on Begin. Begin is the easiest way to deploy your Architect projects to live AWS infrastructure. To do this, create a free Begin account by going to https://begin.com and using your GitHub account to log in. Create a new app and associate it with this repo. Begin will then create hooks to your repo and deploy the app to a staging environment on every git push.