- The Garmin Connect app will allow you to create a custom workout, but it does not allow you to share that workout with someone else. #
- Fortunately, there is a workaround for this using a Google Chrome web extension. #
- Steps to Export:#
- Download "Share Your Garmin Connect Workout" from the Chrome App Store#
- Visit the Garmin Connect web application.#
- Create a workout (Training & Planning → Workouts → Select "Create a Workout" → Follow the steps)#
- Once finished, save the workout and give it a name.#
- Click the download button (created by the extension)#
- Share the JSON file with whoever you'd like to share the workout with (e.g. attach to an email or FB post)#
- Steps to Import:#
- Visit the Garmin Connect web application (as above).#
- Go to Training & Planning → Workouts#
- Click "Import Workout"#
- Select the JSON workout file.#
- Voila!#
- Once you have the workout in Garmin Connect, it should be available to send to your watch/device.#
- On some web pages, enabling comments is a useful feature to gather feedback and engagement on content. (e.g. blog post, podcast episode, etc)#
- With Disqus, it appears that I can embed a comment section on any page with their free version without much limitation.#
- Users can comment with their Disqus account, or as a guest. #
- I even have some moderation capabilities. #
- Eventually, I'd like to have a more self-hosted solution for this — but right now that exceeds my capabilities, and this seems functional enough! #
- Next step: break the podcast episodes into individual pages with comments enabled on each.#
- If a podcast is not discoverable within the podcast player app, most apps will allow you to add it via the show's RSS feed.#
- The process for this varies by app, but in general look for "manually add show", "follow a show by URL", "Add RSS feed", etc.#
- Once you find it, select this option, then enter the URL of the RSS feed of the show into the field provided. Once you press enter, the show should begin to load into your library.#
- I've been working to create a personal website with basic web publishing capabilities as a custom, self-hosted project.#
- This weekend, I updated the index html, added a basic stylesheet, moved the web files to blockstorage, created audio and image directories, setup RSS feeds for two podcast experiments, with corresponding show pages.#
- Tana was waiting to release their AI feature suite until they found an implementation that could make use of the structured data already in Tana. The result is mindblowing.#
- Tana AI uses the OpenAI API Key to:#
- Return results from a prompt#
- Suggest data fields#
- Modify prompt templates#
- Adjust the AI parameters applied to a result. #
- They've documented the feature-set well, and the community has already released some great videos showcasing its power. #
- Tana AI Features#
- AI for Builders#
- Video: Andre Foeken - Tana AI Features - AI Enhanced Fields and more#
- Stoked on the potential of this! Things are moving fast ⚡️ #
- What I like:#
- His website is totally self-hosted and follows his “Tech Independence” principles.#
- He writes everything in HTML, in Vim.#
- He has a “Now” page (he coined the custom)#
- He has a vast collection of his personal “Book Notes”#
- His articles are super simple, focusing on the ideas. #
- URLs are domain/title — great.#
- He includes some headshots for use.#
- He has a ?feed of his Tweets. (How?)#
- He has a “Tools I use” page#
- He has a basic podcast with episodes and RSS feed link right on his site.#
- The podcast pages are awesome: audio, transcript, image, comments section. #
- He has a list of all of the podcasts on which he has been guest (with mp3 file downloads) #
- On his articles and posts, he has an integrated comments section#
- Really, this is exactly what I am looking for in a personal website! #
- I would just add a date-based blog, and adjust the style somewhat.#
- I wonder if he has blogged about the creation of his website… I would LOVE a step-by-step on how to follow his footprints on this. #
- On his most recent Tim Ferriss Podcast appearance, he seemed very passionate about empowering people to create self-hosted personal websites. So a how-to on this seems like a logical product to publish. Perhaps if he hasn't published the making of his site, he would be interested in doing so.#
- One of my challenges with this blog format is the writing experience in Drummer. It feels a bit clunky (that's very likely because I haven't figured out the keyboard commands and navigation shortcuts). It's very different from other outliners that I am used to.#
- Using the list of OPML-compatible apps, I discovered a few alternatives that might work well#
- Bike #
- Workflowy #
- Maybe a bit much for my purposes#
- 250 bullets/mo on the free version might suffice; $5/mo for the Pro if needed#
- iOS version#
- Good links support.#
- OmniOutliner#
- None of the above options seem to have support for OPML-attributes, which is unfortunate. I was hoping for an easier way to add things like "flbulletedlist", "urlimage", etc.#
- Test successful!#
- Fields in Tana are quite powerful. #
- You can create a set of default fields for Supertags, and they will automatically be suggested below the node as soon as the Supertag is assigned.#
- The problem: They are distracting! #
- Structured data is great; but sometimes you just want to focus on the text. #
- For Fields to feel really good for me in Tana, they need some enhancements around visibility. The following might help:#
- Ability to adjust the default show/hide preferences for a field for each Instance of that field.#
- e.g. I may want "Area" to be "show when empty" on a project, but "always hide" on another Supertag.#
- Ability to quickly toggle the visibility of all fields on a node. #
- i.e. collapse them, without collapsing the sub-node contents.#
- This should be assignable to a keyboard shortcut (which is easy to do as long as its in the Command Line.#
- Ability to adjust the show/hide default for a particular session. Like adjusting light/dark mode.#
- When I'm writing-focused, for example, I want to be able to enter a "hide all fields, unless I toggle them on for a node" mode. #
- In summary:#
- Adjust default show/hide for each instance of a field (on different supertags).#
- Ability to toggle the collapse status of fields per node.#
- Ability to toggle the default collapse status of fields globally.#
- Currently, I don't use Fields as much as I could be, due to their overwhelming presence. I believe these changes would help users get the most of Fields, while allowing them to fade into the background when possible.#
I really want "relative dates" or "less/greater than or equal to" in Tana "Search Nodes" (Update: Resolved for particular use-case)#
- On my Tana dashboard, I have sections for:#
- In order to make these work as intended, I need to manually adjust the defer date in the query to TOMORROW's date each day (Defer date is less than @tomorrow).#
- I need to do this because:#
- There is no less than or equal to operator#
- There is no relative date option in queries: e.g. "TOMORROW" or "PARENT +1"#
- Either of those fixes would be adequate for this particular use-case, but I think Tana would really benefit from BOTH of these simple enhancements.#
- UPDATE: As I wrote this I realized a workaround solution:#
- There's a feature in Tana called semantic function — it feels powerful, but it's also a bit of a mind-bender.#
- The intention is that you can develop "is a part of" relationships, that can assist in facilitating meaningful connections between nodes, and improved search results. #
- My hope is that the feature enables lighter data entry, and more inferred relationships. #
- If project is a part of goal which is a associated with an area, then I want to be able to infer that the project is associated with the area via that 2º relationship.#
- I'm struggling to put this into practice, but it feels possible. Almost certainly a knowledge-gap in my application of the concept/feature.#
- UPDATE: It works!! 🎉 #
There's something about managing all of the structured data in Tana that feels more binding than working in Roam#
- I first came across Dave Winer's work via a Twitter conversation about outliners during Summer '21. He knows a thing or two about outliners. Since then, I have been coming to know his suite of software programs and innovations that have shaped (and continue to shape) the web as we know it today. Truly spectacular stuff.#
- From RSS, to blogging and podcasting, Dave's impact has been substantial in the domain of web publishing.#
- What I really like about Dave's stuff is that these tools are real. This is the free and open internet as it was supposed to be. No BS. Less layers of abstraction and fog. In using these tools, I feel like I am connecting with what's really happening with the information. That feels powerful and wonderful.#
- My first experiment was getting a Little Outliner blog up and running on PagePark. This was ambitious. It was my first time trying to setup or operate a web server, and my first time accomplish something using the command line interface. Overall, though, it was a success! The experience opened up my eyes to a whole new world of web publishing. While it was overwhelming, and the learning curve was steep, I was strangely hooked. #
- It was around that time that Dave was working on releasing a new tool called Drummer that would effectively replace and improve upon the functionality of Little Outliner. There were things I was trying to accomplish in LO that were probably better suited for waiting until Drummer was released for testing.#
- Fast to the last few months, when the purchase of a new MBP prompted a revisiting of the command line, and with it, a return to the web publishing stuff. I set up the new machine without "Migration Assistant", made good use of Homebrew in installing apps and services, and then had to re-figure-out some of the server stuff in order to configure the new permissions and re-establish the setup I had on the old machine for publishing. This return inspired me to carry on from where I left off with Little Outliner, and led me to getting started with Drummer. #
- Thankfully, Dave has created a whole library of documentation for these tools, and over 20 years of blog archives. There is no shortage of interesting material to learn from. One of the most valuable lessons I have learned (and am continuing to learn) from Dave is to read the docs. They are there for a reason — to teach folks how things operate in clear and carefully selected language, in a navigable format to address FAQs and common challenges. #
- Another great lesson is to ask clear and specific questions, with the proper context. Or better yet — don't ask until you've genuinely tried your best to find the answer in the docs, forums, and through deep thought. This is a good one. Communities are stronger and more willing to offer assistance when there is a culture of respect and genuine effort (do your best and be considerate). #
- All that is easier said than done for a clueless newbie trying to navigate the unfamiliar terrain of software, code, and programming jargon. These tools and languages can be challenging! But putting in the effort has proven valuable thus far. Little my little I am starting to gain some confidence and familiarity. Thank you to Dave and to anyone who has guided me along the way — I truly appreciate it.#
- So where are we? Well — we're online! #
- The outline for the blog is created in Drummer and rendered by Old School to transform the OPML file into a stylized blog. It is served by PagePark on a personal domain. It also features a linksblog powered by Radio3, which give the ability to collect and publish interesting links in a rolling blog format. #
- The core structures of this setup are simple, and for anyone half-way technical this would be a walk-in-the park to do. You could even simplify it even further by omitting the PagePark aspect. Though, setting up the server was one of the coolest parts.#
- I'm really looking forward to deepening my familiarity with these tools and programs. And that through learning, I am enabled and inspired to create and share ideas. That's what this is all about, anyway.#
- Back to the docs.#
- I stumbled upon the NYT News Chatbot that Dave Winer posted on his blog. #
- Curious, I clicked on the service that was powering the Chatbot — spectacular! #
- Link: Chat Thing#
Added copyright notice to the bottom of the page.#
Can I have BOTH "urlSiteContents" and "mirror" in the same config.json in a PagePark domain folder?#
- When I add the urlSiteContents line to the config.json file in /PagePark/domains/brandontoner.ca the mirrors in the config file no longer redirect as expected, and other file in the domain folder are not accessible (e.g. brandontoner.ca/hello.md)#
- Could I workaround this with subdomains somehow? e.g. map the blog to blog.brandontoner.ca?#
Since Tana is an outliner PKM tool, it should interop, or at least export to OPML format.#- Tana's development team has prioritized support for more structured data, through it's implementation of Fields and Supertags. #
- My thought is that the Fields could integrate with the OPML Headers. #
- Surely there are some challenges to creating an export or integration that would need to be sorted, but Dave seems keen to work with teams that are interested in building integrations.#
- Logseq has developed the ability to work with OPML format, even going as far as being able to publish a blog right from within Logseq, similar to what Drummer does.#
- A great first implementation of OPML in Tana could be an export format from the Tana Command Line: "Export as OPML"#
- Why this is important: #
- If Tana could export as OPML, I could draft writing in Tana, then export to Drummer for publishing on the blog! #
- Ability to work with other tools that support OPML format#
- More interoperability on the web is Good.#
- OPML is an established standard in Outline format and is a logical export format to support.#
- For Developers: OPML Developer Package#
- Short-Term#
- Improve keyboard navigation skills in Drummer editor#
- Improve the workflow efficiency of working with images for the blog.#
- Publish image/file to a hosted server.#
- Add image/file url to the clipboard for inclusion in published content.#
- Setup a River5 RSS Feed#
- Create an iconbar script that toggles the collapse status of a node.#
- Create a menubar script that toggles the list style of a node.#
- Be able to host and render a standalone OPML file on my PagePark server #
- I'd like to be able to easily work with both static and live OPML files easily here.#
- Is "LittleOutliner2" any use to me here?#
- Be able to tweet standalone tweets and threads from Drummer#
- Create scheduler script to "download my files" as a backup.#
- Can I specify the directory?#
- Replace the default PagePark 404 page with something custom#
- Medium- to Long-Term#
- Be able to modify the style template of the Old School blog generated by Drummer such that it can integrate standalone pages.#
- Be able to create and render multiple Old School outliner blogs for various purposes (Main, Rotary, Pharmacy)#
- These are useful to be able to spin up for various purposes.#
- Create an improved brandontoner.ca index page that navigates to various domain assets in a more aesthetically-pleasing way.#
- Remove the RT icon from the blog template (I don't like the way it presents on Twitter)#
- It seems that standalone pages can be created on Old School blogs... just gotta figure out the nuances.#
- From Dave's Notes:#
- Standalone pages. If you want to do an About page for your blog, this is how you do it.#
- Create a new sub-outline, outside the calendar structure. A headline is in the calendar structure if it has a name att or it is contained within a node with a name att.#
- It must have a type attribute of page.#
- It must have a relpath attribute that says where the resulting file is to be written, relative to the top of the blog.#
- image#
- The URL of an image that appears to the right of the text of the post it's attached to.#
- imageLink#
- If you have an image attribute, you can cause it to link to another place by adding an imageLink attribute whose value is the web address of the place#
- inlineImage#
- The URL of an image that appears above the text of the headline it's attached to. To be used when the image is part of the content, not off to the side.#
- urlvideo#
- URL of a YouTube video. If present there's a wedge to the left of the headline, click it to reveal the video below the post. You can get the URL by viewing the video in YouTube, click on Share and copy the URL.#
- urltweet#
- URL of a tweet. If present there's a wedge to the left of the headline, click it to reveal the embedded tweet below the post. You can get the URL by viewing the tweet in Twitter, copy the address in the address bar of the browser.#
- urlexpandableimage#
- URL of an image. If present there's a wedge to the left of the headline, click it to reveal the image below the post.#
- description#
- Attach this to the title headline of a titled post. It's the description of the Twitter and Facebook metadata in the page for the post. Twitter and Facebook will pick it up when you link to the story.#
- flBulletedSubs#
- Add this to a headline with subs. When viewing the page the reader will see bullets next to each of the subs.#
- flNumberedSubs#
- Add this to a headline with subs. When viewing the page the reader will see a number, in sequence, next to each of the subs.#
- collapse#
- Add this to a headline with subs. If present and true, the subs will be collapse initially when displayed for the reader.#
- type#
- relpath#
- More here#
- Find more by looking at the Source.opml document of Old School#
- Had a blast today cheering on some folks that were running the 127th Annual Boston Marathon. #
- The app for the event is spectacular, with live-updating location trackers for each runner! #
- We pre-saved the bib #s for people that we knew were running, which made it easy to check in on their progress as they each progressed through the course.#
- It sounds like the event experience was spectacular for the runners. One friend said "I must have given a thousand high-fives" and that there were spectators along the entire way.#
- I can only imaging the rush of adrenaline making that final turn onto Boylston Street with the crowds cheering you on.#
- #
- List#
- Personal (brandontoner.ca/blog)#
- Rotary (brandontoner.ca/rotary)#
- Pharmacy (brandontoner.ca/pharmacy)#
- Work (under the work domain)#
- How this would work#
- Create each blog as a separate outline in Drummer; make it "public"#
- Create a mirror for each one in PagePark in the config.json file with the brandontoner.ca domain folder#
- Doing it#
- Ran into a hitch: it doesn't seem like I can "build my blog" for more than one outline... it defaults to "Brandon's Blog" somehow... #
- Must be fixable! #
- Clues & Questions#
- The public blog is created by Old School#
- Here is the oldschool.buildblog verb, that's gotta be useful!#
- Maybe I could have a separate script in the iconbar that instructs to build each different outline...?#
- What determines WHICH outline is built as the blog?#
- Inspecting the "build my blog" menu button reveals: "buildMyBlogCommand ();"#
- Finally got around to dealing with a few of the annoyances around the house:#
- Fixed a broken coat rack#
- Cleaned out a spare room, made it into a better office space#
- Dealt with a bunch of loose papers#
- Digitally archived and tossed/shredded a bunch of paper files#
- Feels much better!#
- It's interesting how dealing with spaces that represent stuck energy have an alleviating effect in the mind. Feels like closing a bunch of open loops, or dealing with a nagging issue. #
- I was going to write a post about what's next and what questions I currently have, to think through them, but I decided that sort of content should live somewhere more stable so that I can come back to it across different days.#
- So I created a section in the About page for now.#
- That got me thinking about other "pages". Where does that fit into this blog structure?#
- Surely there's a way to integrate a more stable topography, rather than just a river-like blog stream.#
- I'll be thinking on that a bit more over the last while.#
- Some ideas:#
- Somehow create a sidebar of pages.#
- Create a new "Home" page, so that the blog lives on "brandontoner.ca/blog" rather than at "brandontoner.ca".#
- Create other outlines in Drummer or LO2 for the pages, make them public, mirror them on PagePark.#
- Find a way to do git-style updates from a local folder that publishes OPMLs to brandontoner.ca#
- Sidebar mockup#
- (How do I make this inline? By using item-level attributes?#
- Domain registered at Name Cheap#
- PagePark running on a Digital Ocean remote machine #
- Domains folder in PagePark contains a directory called "/brandontoner.ca", which determines which content is served when that domain is called.#
- Outline generated by Drummer, and processed by Old School to create an outliner blog.#
- It's hosted by PagePark, by adjusting the config.json file to include:#
- {"urlSiteContents": "http://oldschool.scripting.com/{myusername}"}#
- Linksblog created with Radio3 and connected to Drummer so that it displays as a tab on the blog.#
- About page is an outline in Drummer, which is added to the blog via the OPML header "urlAboutOpml". #
- Configured Public Folder to publish local files in a specified folder to an AWS Bucket. #
- I couldn't quite get the log file to publish to the other bucket. Not sure what the issue is there.#
- The whole point of this is to be able to easily work with files in Drummer (like image), I guess. Since they need to be hosted to reference.#
- AWS is hard, man. Hurts my head.#
- http://scripting.com/images/2021/12/12/zen.png#
- Test worked → Glossary terms need to be wrapped in quote in the writing in order to trigger the Glossary substitution.#
- Used these Guidance docs#
It's a beautiful day #
Hello world#
- The Garmin Connect app will allow you to create a custom workout, but it does not allow you to share that workout with someone else. #
- Fortunately, there is a workaround for this using a Google Chrome web extension. #
- Steps to Export:#
- Download "Share Your Garmin Connect Workout" from the Chrome App Store#
- Visit the Garmin Connect web application.#
- Create a workout (Training & Planning → Workouts → Select "Create a Workout" → Follow the steps)#
- Once finished, save the workout and give it a name.#
- Click the download button (created by the extension)#
- Share the JSON file with whoever you'd like to share the workout with (e.g. attach to an email or FB post)#
- Steps to Import:#
- Visit the Garmin Connect web application (as above).#
- Go to Training & Planning → Workouts#
- Click "Import Workout"#
- Select the JSON workout file.#
- Voila!#
- Once you have the workout in Garmin Connect, it should be available to send to your watch/device.#
- On some web pages, enabling comments is a useful feature to gather feedback and engagement on content. (e.g. blog post, podcast episode, etc)#
- With Disqus, it appears that I can embed a comment section on any page with their free version without much limitation.#
- Users can comment with their Disqus account, or as a guest. #
- I even have some moderation capabilities. #
- Eventually, I'd like to have a more self-hosted solution for this — but right now that exceeds my capabilities, and this seems functional enough! #
- Next step: break the podcast episodes into individual pages with comments enabled on each.#
- If a podcast is not discoverable within the podcast player app, most apps will allow you to add it via the show's RSS feed.#
- The process for this varies by app, but in general look for "manually add show", "follow a show by URL", "Add RSS feed", etc.#
- Once you find it, select this option, then enter the URL of the RSS feed of the show into the field provided. Once you press enter, the show should begin to load into your library.#
- I've been working to create a personal website with basic web publishing capabilities as a custom, self-hosted project.#
- This weekend, I updated the index html, added a basic stylesheet, moved the web files to blockstorage, created audio and image directories, setup RSS feeds for two podcast experiments, with corresponding show pages.#
- Tana was waiting to release their AI feature suite until they found an implementation that could make use of the structured data already in Tana. The result is mindblowing.#
- Tana AI uses the OpenAI API Key to:#
- Return results from a prompt#
- Suggest data fields#
- Modify prompt templates#
- Adjust the AI parameters applied to a result. #
- They've documented the feature-set well, and the community has already released some great videos showcasing its power. #
- Tana AI Features#
- AI for Builders#
- Video: Andre Foeken - Tana AI Features - AI Enhanced Fields and more#
- Stoked on the potential of this! Things are moving fast ⚡️ #
- What I like:#
- His website is totally self-hosted and follows his “Tech Independence” principles.#
- He writes everything in HTML, in Vim.#
- He has a “Now” page (he coined the custom)#
- He has a vast collection of his personal “Book Notes”#
- His articles are super simple, focusing on the ideas. #
- URLs are domain/title — great.#
- He includes some headshots for use.#
- He has a ?feed of his Tweets. (How?)#
- He has a “Tools I use” page#
- He has a basic podcast with episodes and RSS feed link right on his site.#
- The podcast pages are awesome: audio, transcript, image, comments section. #
- He has a list of all of the podcasts on which he has been guest (with mp3 file downloads) #
- On his articles and posts, he has an integrated comments section#
- Really, this is exactly what I am looking for in a personal website! #
- I would just add a date-based blog, and adjust the style somewhat.#
- I wonder if he has blogged about the creation of his website… I would LOVE a step-by-step on how to follow his footprints on this. #
- On his most recent Tim Ferriss Podcast appearance, he seemed very passionate about empowering people to create self-hosted personal websites. So a how-to on this seems like a logical product to publish. Perhaps if he hasn't published the making of his site, he would be interested in doing so.#
- One of my challenges with this blog format is the writing experience in Drummer. It feels a bit clunky (that's very likely because I haven't figured out the keyboard commands and navigation shortcuts). It's very different from other outliners that I am used to.#
- Using the list of OPML-compatible apps, I discovered a few alternatives that might work well#
- Bike #
- Workflowy #
- Maybe a bit much for my purposes#
- 250 bullets/mo on the free version might suffice; $5/mo for the Pro if needed#
- iOS version#
- Good links support.#
- OmniOutliner#
- None of the above options seem to have support for OPML-attributes, which is unfortunate. I was hoping for an easier way to add things like "flbulletedlist", "urlimage", etc.#
- Test successful!#
- Fields in Tana are quite powerful. #
- You can create a set of default fields for Supertags, and they will automatically be suggested below the node as soon as the Supertag is assigned.#
- The problem: They are distracting! #
- Structured data is great; but sometimes you just want to focus on the text. #
- For Fields to feel really good for me in Tana, they need some enhancements around visibility. The following might help:#
- Ability to adjust the default show/hide preferences for a field for each Instance of that field.#
- e.g. I may want "Area" to be "show when empty" on a project, but "always hide" on another Supertag.#
- Ability to quickly toggle the visibility of all fields on a node. #
- i.e. collapse them, without collapsing the sub-node contents.#
- This should be assignable to a keyboard shortcut (which is easy to do as long as its in the Command Line.#
- Ability to adjust the show/hide default for a particular session. Like adjusting light/dark mode.#
- When I'm writing-focused, for example, I want to be able to enter a "hide all fields, unless I toggle them on for a node" mode. #
- In summary:#
- Adjust default show/hide for each instance of a field (on different supertags).#
- Ability to toggle the collapse status of fields per node.#
- Ability to toggle the default collapse status of fields globally.#
- Currently, I don't use Fields as much as I could be, due to their overwhelming presence. I believe these changes would help users get the most of Fields, while allowing them to fade into the background when possible.#
I really want "relative dates" or "less/greater than or equal to" in Tana "Search Nodes" (Update: Resolved for particular use-case)#
- On my Tana dashboard, I have sections for:#
- In order to make these work as intended, I need to manually adjust the defer date in the query to TOMORROW's date each day (Defer date is less than @tomorrow).#
- I need to do this because:#
- There is no less than or equal to operator#
- There is no relative date option in queries: e.g. "TOMORROW" or "PARENT +1"#
- Either of those fixes would be adequate for this particular use-case, but I think Tana would really benefit from BOTH of these simple enhancements.#
- UPDATE: As I wrote this I realized a workaround solution:#
- There's a feature in Tana called semantic function — it feels powerful, but it's also a bit of a mind-bender.#
- The intention is that you can develop "is a part of" relationships, that can assist in facilitating meaningful connections between nodes, and improved search results. #
- My hope is that the feature enables lighter data entry, and more inferred relationships. #
- If project is a part of goal which is a associated with an area, then I want to be able to infer that the project is associated with the area via that 2º relationship.#
- I'm struggling to put this into practice, but it feels possible. Almost certainly a knowledge-gap in my application of the concept/feature.#
- UPDATE: It works!! 🎉 #
There's something about managing all of the structured data in Tana that feels more binding than working in Roam#
- I first came across Dave Winer's work via a Twitter conversation about outliners during Summer '21. He knows a thing or two about outliners. Since then, I have been coming to know his suite of software programs and innovations that have shaped (and continue to shape) the web as we know it today. Truly spectacular stuff.#
- From RSS, to blogging and podcasting, Dave's impact has been substantial in the domain of web publishing.#
- What I really like about Dave's stuff is that these tools are real. This is the free and open internet as it was supposed to be. No BS. Less layers of abstraction and fog. In using these tools, I feel like I am connecting with what's really happening with the information. That feels powerful and wonderful.#
- My first experiment was getting a Little Outliner blog up and running on PagePark. This was ambitious. It was my first time trying to setup or operate a web server, and my first time accomplish something using the command line interface. Overall, though, it was a success! The experience opened up my eyes to a whole new world of web publishing. While it was overwhelming, and the learning curve was steep, I was strangely hooked. #
- It was around that time that Dave was working on releasing a new tool called Drummer that would effectively replace and improve upon the functionality of Little Outliner. There were things I was trying to accomplish in LO that were probably better suited for waiting until Drummer was released for testing.#
- Fast to the last few months, when the purchase of a new MBP prompted a revisiting of the command line, and with it, a return to the web publishing stuff. I set up the new machine without "Migration Assistant", made good use of Homebrew in installing apps and services, and then had to re-figure-out some of the server stuff in order to configure the new permissions and re-establish the setup I had on the old machine for publishing. This return inspired me to carry on from where I left off with Little Outliner, and led me to getting started with Drummer. #
- Thankfully, Dave has created a whole library of documentation for these tools, and over 20 years of blog archives. There is no shortage of interesting material to learn from. One of the most valuable lessons I have learned (and am continuing to learn) from Dave is to read the docs. They are there for a reason — to teach folks how things operate in clear and carefully selected language, in a navigable format to address FAQs and common challenges. #
- Another great lesson is to ask clear and specific questions, with the proper context. Or better yet — don't ask until you've genuinely tried your best to find the answer in the docs, forums, and through deep thought. This is a good one. Communities are stronger and more willing to offer assistance when there is a culture of respect and genuine effort (do your best and be considerate). #
- All that is easier said than done for a clueless newbie trying to navigate the unfamiliar terrain of software, code, and programming jargon. These tools and languages can be challenging! But putting in the effort has proven valuable thus far. Little my little I am starting to gain some confidence and familiarity. Thank you to Dave and to anyone who has guided me along the way — I truly appreciate it.#
- So where are we? Well — we're online! #
- The outline for the blog is created in Drummer and rendered by Old School to transform the OPML file into a stylized blog. It is served by PagePark on a personal domain. It also features a linksblog powered by Radio3, which give the ability to collect and publish interesting links in a rolling blog format. #
- The core structures of this setup are simple, and for anyone half-way technical this would be a walk-in-the park to do. You could even simplify it even further by omitting the PagePark aspect. Though, setting up the server was one of the coolest parts.#
- I'm really looking forward to deepening my familiarity with these tools and programs. And that through learning, I am enabled and inspired to create and share ideas. That's what this is all about, anyway.#
- Back to the docs.#
- I stumbled upon the NYT News Chatbot that Dave Winer posted on his blog. #
- Curious, I clicked on the service that was powering the Chatbot — spectacular! #
- Link: Chat Thing#
Added copyright notice to the bottom of the page.#
Can I have BOTH "urlSiteContents" and "mirror" in the same config.json in a PagePark domain folder?#
- When I add the urlSiteContents line to the config.json file in /PagePark/domains/brandontoner.ca the mirrors in the config file no longer redirect as expected, and other file in the domain folder are not accessible (e.g. brandontoner.ca/hello.md)#
- Could I workaround this with subdomains somehow? e.g. map the blog to blog.brandontoner.ca?#
- Since Tana is an outliner PKM tool, it should interop, or at least export to OPML format.#
- Tana's development team has prioritized support for more structured data, through it's implementation of Fields and Supertags. #
- My thought is that the Fields could integrate with the OPML Headers. #
- Surely there are some challenges to creating an export or integration that would need to be sorted, but Dave seems keen to work with teams that are interested in building integrations.#
- Logseq has developed the ability to work with OPML format, even going as far as being able to publish a blog right from within Logseq, similar to what Drummer does.#
- A great first implementation of OPML in Tana could be an export format from the Tana Command Line: "Export as OPML"#
- Why this is important: #
- If Tana could export as OPML, I could draft writing in Tana, then export to Drummer for publishing on the blog! #
- Ability to work with other tools that support OPML format#
- More interoperability on the web is Good.#
- OPML is an established standard in Outline format and is a logical export format to support.#
- For Developers: OPML Developer Package#
- Short-Term#
- Improve keyboard navigation skills in Drummer editor#
- Improve the workflow efficiency of working with images for the blog.#
- Publish image/file to a hosted server.#
- Add image/file url to the clipboard for inclusion in published content.#
- Setup a River5 RSS Feed#
- Create an iconbar script that toggles the collapse status of a node.#
- Create a menubar script that toggles the list style of a node.#
- Be able to host and render a standalone OPML file on my PagePark server #
- I'd like to be able to easily work with both static and live OPML files easily here.#
- Is "LittleOutliner2" any use to me here?#
- Be able to tweet standalone tweets and threads from Drummer#
- Create scheduler script to "download my files" as a backup.#
- Can I specify the directory?#
- Replace the default PagePark 404 page with something custom#
- Medium- to Long-Term#
- Be able to modify the style template of the Old School blog generated by Drummer such that it can integrate standalone pages.#
- Be able to create and render multiple Old School outliner blogs for various purposes (Main, Rotary, Pharmacy)#
- These are useful to be able to spin up for various purposes.#
- Create an improved brandontoner.ca index page that navigates to various domain assets in a more aesthetically-pleasing way.#
- Remove the RT icon from the blog template (I don't like the way it presents on Twitter)#
- It seems that standalone pages can be created on Old School blogs... just gotta figure out the nuances.#
- From Dave's Notes:#
- Standalone pages. If you want to do an About page for your blog, this is how you do it.#
- Create a new sub-outline, outside the calendar structure. A headline is in the calendar structure if it has a name att or it is contained within a node with a name att.#
- It must have a type attribute of page.#
- It must have a relpath attribute that says where the resulting file is to be written, relative to the top of the blog.#
- image#
- The URL of an image that appears to the right of the text of the post it's attached to.#
- imageLink#
- If you have an image attribute, you can cause it to link to another place by adding an imageLink attribute whose value is the web address of the place#
- inlineImage#
- The URL of an image that appears above the text of the headline it's attached to. To be used when the image is part of the content, not off to the side.#
- urlvideo#
- URL of a YouTube video. If present there's a wedge to the left of the headline, click it to reveal the video below the post. You can get the URL by viewing the video in YouTube, click on Share and copy the URL.#
- urltweet#
- URL of a tweet. If present there's a wedge to the left of the headline, click it to reveal the embedded tweet below the post. You can get the URL by viewing the tweet in Twitter, copy the address in the address bar of the browser.#
- urlexpandableimage#
- URL of an image. If present there's a wedge to the left of the headline, click it to reveal the image below the post.#
- description#
- Attach this to the title headline of a titled post. It's the description of the Twitter and Facebook metadata in the page for the post. Twitter and Facebook will pick it up when you link to the story.#
- flBulletedSubs#
- Add this to a headline with subs. When viewing the page the reader will see bullets next to each of the subs.#
- flNumberedSubs#
- Add this to a headline with subs. When viewing the page the reader will see a number, in sequence, next to each of the subs.#
- collapse#
- Add this to a headline with subs. If present and true, the subs will be collapse initially when displayed for the reader.#
- type#
- relpath#
- More here#
- Find more by looking at the Source.opml document of Old School#
- Had a blast today cheering on some folks that were running the 127th Annual Boston Marathon. #
- The app for the event is spectacular, with live-updating location trackers for each runner! #
- We pre-saved the bib #s for people that we knew were running, which made it easy to check in on their progress as they each progressed through the course.#
- It sounds like the event experience was spectacular for the runners. One friend said "I must have given a thousand high-fives" and that there were spectators along the entire way.#
- I can only imaging the rush of adrenaline making that final turn onto Boylston Street with the crowds cheering you on.#
- #
- List#
- Personal (brandontoner.ca/blog)#
- Rotary (brandontoner.ca/rotary)#
- Pharmacy (brandontoner.ca/pharmacy)#
- Work (under the work domain)#
- How this would work#
- Create each blog as a separate outline in Drummer; make it "public"#
- Create a mirror for each one in PagePark in the config.json file with the brandontoner.ca domain folder#
- Doing it#
- Ran into a hitch: it doesn't seem like I can "build my blog" for more than one outline... it defaults to "Brandon's Blog" somehow... #
- Must be fixable! #
- Clues & Questions#
- The public blog is created by Old School#
- Here is the oldschool.buildblog verb, that's gotta be useful!#
- Maybe I could have a separate script in the iconbar that instructs to build each different outline...?#
- What determines WHICH outline is built as the blog?#
- Inspecting the "build my blog" menu button reveals: "buildMyBlogCommand ();"#
- Finally got around to dealing with a few of the annoyances around the house:#
- Fixed a broken coat rack#
- Cleaned out a spare room, made it into a better office space#
- Dealt with a bunch of loose papers#
- Digitally archived and tossed/shredded a bunch of paper files#
- Feels much better!#
- It's interesting how dealing with spaces that represent stuck energy have an alleviating effect in the mind. Feels like closing a bunch of open loops, or dealing with a nagging issue. #
- I was going to write a post about what's next and what questions I currently have, to think through them, but I decided that sort of content should live somewhere more stable so that I can come back to it across different days.#
- So I created a section in the About page for now.#
- That got me thinking about other "pages". Where does that fit into this blog structure?#
- Surely there's a way to integrate a more stable topography, rather than just a river-like blog stream.#
- I'll be thinking on that a bit more over the last while.#
- Some ideas:#
- Somehow create a sidebar of pages.#
- Create a new "Home" page, so that the blog lives on "brandontoner.ca/blog" rather than at "brandontoner.ca".#
- Create other outlines in Drummer or LO2 for the pages, make them public, mirror them on PagePark.#
- Find a way to do git-style updates from a local folder that publishes OPMLs to brandontoner.ca#
- Sidebar mockup#
- (How do I make this inline? By using item-level attributes?#
- Domain registered at Name Cheap#
- PagePark running on a Digital Ocean remote machine #
- Domains folder in PagePark contains a directory called "/brandontoner.ca", which determines which content is served when that domain is called.#
- Outline generated by Drummer, and processed by Old School to create an outliner blog.#
- It's hosted by PagePark, by adjusting the config.json file to include:#
- {"urlSiteContents": "http://oldschool.scripting.com/{myusername}"}#
- Linksblog created with Radio3 and connected to Drummer so that it displays as a tab on the blog.#
- About page is an outline in Drummer, which is added to the blog via the OPML header "urlAboutOpml". #
- Configured Public Folder to publish local files in a specified folder to an AWS Bucket. #
- I couldn't quite get the log file to publish to the other bucket. Not sure what the issue is there.#
- The whole point of this is to be able to easily work with files in Drummer (like image), I guess. Since they need to be hosted to reference.#
- AWS is hard, man. Hurts my head.#
- http://scripting.com/images/2021/12/12/zen.png#
- Test worked → Glossary terms need to be wrapped in quote in the writing in order to trigger the Glossary substitution.#
- Used these Guidance docs#
It's a beautiful day #
Hello world#