Vincent van Scherpenseel

[Jason Fried @jasonfried]

As we finish up the all new HEY Calendar, I thought people might enjoy a peek behind the scenes of the project itself.

What you see in the tall screenshot below are two weeks worth of updates summarized by Jorge, the technical lead on the project. They appear below the Hill Chart snapshots of where the different scopes stand at the time of the update.

You can see movement of different scopes over the past week, as well as a new scope ("Support multiple accounts") that appeared on the "figuring things out" side.

These weekly written updates, along with the associated Hill Charts, tell us everything we need to know at a high level about how things are going, what's in play, and who's on what — all without status meetings or pulling a bunch of people off their work to report in about what they're doing.

The links link off to other projects, posts, or comments within Basecamp, and occasionally off to a PR on GitHub. The entire project is run, tracked, discussed, and presented in Basecamp. No Slack, Jira, Asana, Trello, Monday, or whatever — it's all in Basecamp. One tool, one place, one way.

I hope this was useful. Got questions? Post 'em here and I'll answer what I can.

[Vincent van Scherpenseel @vincent_io]

@PetrSigut @JoshWComeau I'd miss the incredibly powerful search in Gmail. Otherwise I would seriously consider Hey.

[Existential Comics (find me on bluesky) @existentialcoms]

I would like to issue a formal apology to the X community for implying that the Telsa Autopilot™ feature could be engage safely around pedestrians. According to industry experts Telsa's Autopilot is dangerous and unreliable, and I will do better in the future to express this.

[Vincent van Scherpenseel @vincent_io]

the beatles crossing abbey road on tatooine #dalle

[Vincent van Scherpenseel @vincent_io]

🙃 @amazon

[kelvin newman @kelvinnewman]

Wowser! Congrats all round!

[Conductor @Conductor]

Today, Conductor announces its acquisition of real-time website monitoring technology @contentking—a significant step forward on our path to shape the future of enterprise organic marketing. https://t.co/Tt6rmW0JzA

[Vincent van Scherpenseel @vincent_io]

@AndrejaCicak @Stevenvvessum @contentking Thanks so much @AndrejaCicak — we're super stoked about this! 🎉

[ContentKing @contentking]

BIG NEWS!

We’re thrilled to announce that ContentKing has been acquired by @Conductor, the #1 Organic Marketing platform!

By joining forces, we're transforming the search & organic marketing space, bringing even more value and driving even more SEO success for our customers.

[Vincent van Scherpenseel @vincent_io]

@badams @Stevenvvessum @contentking Thanks so much for the nice words @badams — We're incredibly proud of what our team has been able to achieve in just 7 years! Now the story continues together with @conductor! 🚀

[ContentKing @contentking]

You can also see when your robots.txt is visited by search engines in real time with our new log file analysis feature 🤖

Pretty cool, right?

[ContentKing @contentking]

Keep track of all robots.txt changes in real time with our expanded robots.txt monitoring!🎉

🔍Extensive change tracking
✔️HTTP headers for any robots.txt versions
📥Download full response
🤖Log file analysis for robots.txt

Check it out the improvements: https://t.co/v5CfsgVay7

[Aleyda Solis 🕊️ @aleyda]

Interesting to see how the MS bot crawls more often #LearningSEO that I have w/ the IndexNow plugin than Googlebot. Then my own site (without IndexNow integration) is visited more often by the Gbot 😁

Using @contentking bot monitoring via @Cloudflare integration

[Aleyda Solis 🕊️ @aleyda]

Unintended consequences of the #SEOFOMO chat today:

1) @dergal & @nickwilsdon agreeing (!) @contentking log file integration is 🔥

2) Always nice to hear @gfiorelli1's cat cute "Meow" 😺

3) @TwitterSpaces: sadly we had a few sound issues w/ bluetooth 😞 fix them pls! https://t.co/kMbs0zHBXb

[Vincent van Scherpenseel @vincent_io]

@JHTScherck @contentking Ha, don't worry about that! — I love it that when customers are so involved in what we build and share their feedback! That's how we all get better and better :)

[Vincent van Scherpenseel @vincent_io]

@JHTScherck @contentking We don't keep the token, and actually request customers to remove/expire the token from their CF account. We only need it to install the worker and that's it, but if you're OK with manual installing the worker you don't need the token at all :)

[Vincent van Scherpenseel @vincent_io]

@JHTScherck @contentking @contentking support will reach out to assist with installing the CF Worker manually. Looking forward to hearing how you like real-time LFA 🙂

[Vincent van Scherpenseel @vincent_io]

@JHTScherck @contentking The edit permission is on the token, and needed to install the worker. If that's a problem there's an easy way around it by installing the worker manually. Note that CF workers are "apps" that sit on the edge between client and origin: it's something different than CF logs.

[JH Scherck @JHTScherck]

Absolutely love being able to see exactly when our customers push our recommendations live via @contentking - I regret sleeping on the entire concept of marketing site monitoring and visibility. Can't wait to get some customers using Cloudflare set up to stream Googlebot logs.

[ContentKing @contentking]

You can now analyze your log files directly in ContentKing 🎉

Understand how search engines crawl your site with our new Log File Analysis feature!

See when search engines visit and how often — and as always, this is all in real time👏

Here’s how👇
https://t.co/zYWtENGQSB