This post is the home of my #BuildInPublic project. Because with my #BuildInPublic approach, I reward followers with earliest content previews.

In fact, I'm developing tiers of followers/subscribers here. As will become clear in the next few days.

Furthermore, I'm adopting a #BuildInPublic approach to all my websites. Because I want to create informal online learning environments that encourage learners to become coaches/mentors. Obviously, that will take time to onboard people and qualify objectives. But I have to start somewhere. And #BuildInPublic seems to me to be my best chance of finding like-minded collaborators.

I often rush into assessing new applications. Because I learn quicker by applying compared to reading. But one downside is that I frequently miss key features.

That's only a major drawback if I abandon the application where I can't see how it fits my project. And today I avoided that with serendipity. Because… 1. My application was a Chrome Extension 1. I wanted to test to see if was active and change webpage content accordingly 1. I found I could run the app without an extension - as fully described in the documentation that I skipped reading!

All of which is an idea for my next blog post. But the real point is I have established a process for starting ad-hoc Shrewd Learning projects "in the wild". Because normally, I start making notes somewhere. Then forgetting where I put them.

I think we all do that when we spot something interesting that might warrant future research. Now for my established subject areas, I always start annotating new topics within that subject area. So, I can prioritize it in my usual processes.

Today, I've extended this by tagging public notes with Shrewd Learning. So when I look at the Shrewd Learning Tag, I see all notes that present potential new learning topics. Which opens a great way to collaborate loosely with other people if I can establish some traction with Shrewd Learning.

For now, this is my reminder to do a personal blog entry based on this. More importantly, I should update this blog entry to reflect recent advances in Shrewd Learning and my other 2 online learning projects.

Remove space to ShrewdNotes

New 4 part blog series... - Introducing 📒ShrewdNotes. Members Notes in Progress. - How Keith Uses 📒ShrewdNotes - How You Can Use 📒ShrewdNotes - Why We Might Share 📒ShrewdNotes

Embedding Hypothesis in Websites and Platforms

Embedding Hypothesis To add Hypothesis to your website or platform, simply add the following line to the HTML source of your page:

From https://web.hypothes.is/help/embedding-hypothesis-in-websites-and-platforms/

Which continues with an example of Hypothes.is client configuration.

Is it the best to put private vs public in the Contact Page? Or should it be separate?

I think it is best to include it in the Contact Page. Because my perception is that it's all about contacting me. But I should do a poll on this.

Also, this isn't just a Gout issue, so it needs to be addressed in other subject sites. And as it is a fundamental part of successful collaboration, I will repeat it in Food and Learning.