These are the Naftiko platform updates, providing a way of communicating updates across the platform as work happens.
Hello Community
This is the coming out to the community update for the go-to-market documentation site.
This is the go-to-market site for Naftiko. It provides the entire blueprint for how Naftiko conducts marketing and evangelism. Like our market research, technology, and revenue site we don’t see any reason why we shouldn’t be doing all this work out in the open and sharing with the community as we progress–allowing others to learn from, join in, making the go-to-market motion a community thing.
I use the YAML for capabilities, channels, events, glossary, organizations, services, standards, stories, and use cases in this Docsy site hosted on GitHub to manage all the ideas and activities I am setting in motion on any given day. I use the issues for the repo as an inbox, submitting ideas as I move fast through a variety of conversations and content work. Feel free to jump and use anything here, as I continue to execute our GTM motion, automate a lot of what I do, and work to amplify Naftiko, but also the open-source stanards and tooling we are building on.
Setting Up YouTube, Apple, and Spotify Podcasts for Naftiko Capabilities
Setting up our media channels as I prepare for launching the Naftiko Capabilities podcast.
I spent a couple of hours setting up the minimum viable channels needed to support the Naftiko Podcast out of the gate. It was interesting to see the difference in user experience between YouTube, Apple, and Spotify. YouTube is definitely the most advanced. I like the Apple one because it is 100% configured by an RSS feed for the podcast, which has it’s ups and downs. Spotify was by far the worst experience, with the interface spinning wheel never stopping and every other API call failing behind the scenes.
It will be interesting to stand up a Naftiko capability to manage our podcast across just these three channels. I manage the RSS feed used to power apple via GitHub, but both YouTube and Spotify has an API, but as with any API the devil will be in the details. Spotify is cumbersome to manage, so I look forward to automating. Apple will be the easiest to automate because it is 100% YAML on GitHub, served up as an RSS feed to Apple.
There are services we can use to automate this stuff, but I’d rather define a Naftiko Capability to help us manage. I’d rather breakdown all of the APIs needed, and understand what all the details of each service is. Once I have the podcast running for a few weeks, and I get the capability defined for how I will be automating podcast management, I will explore some other channels we can syndicate to, as well as looking at what some of the aggregator services are doing when it comes to managing podcasts for users.
I will publish podcasts to these three channels on Tuesday and Thursddays each week. I am guessing after a couple of weeks of manually doing the Spotify work I will be willing to invest more in some automation. I feel like Apple is a minimum viable experience, which makes sense. I feel like Spotify is a textbook entry for enshittification and they just don’t care about experience. We’ll see, I’ll spend some time in there, and then get back to other platforms like SoundCloud, and we’ll see how I feel.
Hello World
This is the introductory post for the go-to-market documentation site.s
This is the go-to-market documentation site for Naftiko. It contains all of the stories, conversations, and channels we will be publishing to. It provides an ongoing snaprshot of our go-to-market function, providing a blueprint for me to follow when getting the word out about what we are building at Naftiko, and once we have a product to put in the hands of developers, we’ll already have this machine broken in.
Like the technology, market research, and revenue sites the goal is to define things early on and publish somewhere we can share with investors, analysts, and team members, as well as eventually the public. It should provide a one-stop for anyone curious about what is happening with the go-to-market motion, as well as all the information you need to get involved and begin contributing stories, participating in conversations, help get others involved, while I use as the daily playbook.