11ty/tugboat

Donut = experimental Tugboat

rdela opened this issue · 5 comments

As noted in #6, my devDeps update (which I followed up with #7, a package metadata update), I am beginning to noodle around Tugboat 🛟

I brought up some of my guiding questions on Mastodon:

Thinking of extending the Tugboat collection of WebC components

  • What would you like to see most?
  • A separate collection alongside Tugboat?
  • Integrating more components into Tugboat?
  • What should we consider adding?
  • Are you using a component library like this already?
  • Looking forward to any upcoming releases?

I have my own answers to all these questions which I plan to start writing about soon. My overall plan for now in regards to Tugboat (and Eleventy in general) is to keep developing eleventeen in the open and to start integrating existing Tugboat components there, alongside experimental versions of an additional set of WebC components.

Having found an abundance of adequate names in the thesaurus for this new set of experimental add-on components, in typical fashion I went with none of them, instead settling on ✨Donut✨, since it is a popular way to refer to the “life-saving buoy designed to be thrown to a person in water to provide buoyancy and prevent drowning,” that the “ring buoy” emoji (🛟) depicts, among life guards and water rescue folx.

Other names for “lifebuoy” include:

  • life preserver
  • life ring
  • lifering
  • lifesaver
  • ring buoy
  • donut
  • safety wheel
  • Perry buoy
  • Kisbee ring

With the hardest problem in software development (other than off by one errors) solved, my first thought with Donut was to get a playground, testbed type situation going. I set my fork of Tugboat’s main branch to build a mirror of https://tugboat.11ty.dev at https://tugboat.netlify.app

Then I set up the donut branch of my fork, where I am making all the new experimental additions and modfications, to build at https://donut--tugboat.netlify.app

Right now there is only one experimental WebC component, Emoji link (source, commit 617f094) that blends favicon-link with accessible-emoji. This was borne of trying to link to Tugboat with favicon-link only to realize it had no favicon.

I made separate sections for Donut Features and Tugboat Features, plus Donut Demos and Tugboat Demos, in index.webc even though I added emoji-link.webc to the same directory, _components.

Lastly, in that same commit, 7da007b, I decided to change both light and dark color schemes to help keep myself oriented context switching back and forth, inspired by the color palette of a chocolate glazed donut with sprinkles, candy sprinkles, and particluarly the pinks and oranges in this image. I also updated some of the metadata to hopefully avoid more confusion than necessary.

The general idea is that this takes any pressure off to integrate experimental components into Tugboat while providing an easy way to pull ones that do interest the Tugboat crowd into projects and Tugboat itself. I have not published anything to npm yet and it appears 11ty has not yet either. Ideal distribution and update mechanisms, starting with how do people update their starters and component setups currently, is something I am very keen to hear more about.

Hope this explains some of my thought process so far. Excited for any and all input.

🛟✨🍩

Mainly commenting because I think tugboat is underrated. Plus, I remember this site back in the day. State-of-the-art 11ty. 2019.
https://candy-11ty.netlify.app

@theapplegates Totally underrated! Feel like we need a marketing push to get the word out to the world.

Thanks for the link to https://github.com/stickhandle/candy-11ty I had not seen it and that looks very cool plus a great place to ponder ideas from. Just looking around your GH profile I found several things for my Eleventy list https://github.com/stars/rdela/lists/eleventy/

My list is no https://11tybundle.dev but it's mine haha. Things I added or saw you also interacted with of note:

Speaking of Astro I also think https://github.com/HiDeoo/starlight-blog has some thoughtful design and considerate functionality we could learn from.

Added a couple few some commits

  • use server-only comments in emoji-link 00bfb91

  • add emoji-link to donut branch from Donut demo, also linked from repo to Donut demo a103db9

  • use @emoji prop instead of attr… fd61b24

    Make any attribute into a prop by prefixing it with @. Props are server-only “private” attributes that don’t end up in the output HTML (they are private to WebC). They are identical to attributes except that they are filtered from the output HTML.

    deleted line breaks between tag and server-only comment boundaries

  • emoji-link to these comments 2c9b776

  • Use cooler emoji for OpenGraph Image and IndieWeb Avatar API Services 3492f13

my website is a fork of https://github.com/madrilene/eleventy-excellent , her site is the best in my opinion. You can keep it as is or add to it. My personal site is there at https://paulapplegate.com. The site is not done or even started by any means.
I'm not a developer so maybe you can answer this. Why under certin circumstances does GitHub make meke a pull request instead of updating a fork by just syncing it?
Either way if you want to answer maybe head to the discord server, better yet I will ask. Since Github is probably not the forum to make a thread of questions/answers
Paul

Eleventy Excellent is fabulous, feels like the most complete and actively maintained Eleventy starter out there to me right now, 3.2.0 is just out. Much respect to @madrilene

I am in the 11ty Discord, if you want to tag me my handle is rickydelaveaga - Update: responded to Paul’s question in help with some links, agree with both previous responses too.