130 unit tests passing; 90+ regression tests passing… still choking on real-world content/end-to-end tests. FML.
(First world problems.)
(I’ll pick it up again tomorrow.)
130 unit tests passing; 90+ regression tests passing… still choking on real-world content/end-to-end tests. FML.
(First world problems.)
(I’ll pick it up again tomorrow.)
I’m speaking at Defuse – Design For Use – at The Sugar Club in Dublin on November 10th at 7PM.
The theme is “Reclaiming Design: Taking Back Purpose in an Automated Age” and my talk’s titled “Think small.”
It’s first come, first served, so mark your calendars and show up early (and find me and say hi if you do!) :)
#ThinkSmall #DefuseDublin #IXDA #IXDADublin #SmallTech #SmallWeb #events #Dublin #Ireland #tech #design #ethics
🎶 One of these things is not like the other…🎶
Can you spot the difference kids?
#SmallWeb #SmallTech #BigWeb #BigTech #LinkedIn #PersonalWebSite
I’m speaking at Defuse – Design For Use – at The Sugar Club in Dublin on November 10th at 7PM.
The theme is “Reclaiming Design: Taking Back Purpose in an Automated Age” and my talk’s titled “Think small.”
It’s first come, first served, so mark your calendars and show up early (and find me and say hi if you do!) :)
#ThinkSmall #DefuseDublin #IXDA #IXDADublin #SmallTech #SmallWeb #events #Dublin #Ireland #tech #design #ethics
Is there a search engine for the #SmallWeb that you could recommend?
Coming soon (likely this afternoon, I’m writing tests and docs and updating examples as we speak)…
This is the sort of thing you’ll be able to do with Markdown pages. Just pop any arbitrary JavaScript you want in the new script block in the front matter and then import and use components as well as plain old JavaScript tagged template variable interpolation (not shown in this example) inside your Markdown.
The screen has all the code (sans the end of the last line of CSS and the closing tags for the
Not coming this afternoon :)
Just realised that I’m not handling nested interpolated values properly as I’m using a regular expression to simulate what JavaScript’s native tagged template feature does.
Instead, I have to write a simple parser.
If I had a penny for every time I started with regular expressions on this and then had to implement a proper parser afterwards… I’d have two pennies (the other time was for extracted nested tags. See a pattern? (I’m here all week.)
So, barring the discovery of other edge (or not-so edge) cases following further testing, I’m going to aim for middle of the week for the release of the new Markdown Pages feature.
💕
Coming soon (likely this afternoon, I’m writing tests and docs and updating examples as we speak)…
This is the sort of thing you’ll be able to do with Markdown pages. Just pop any arbitrary JavaScript you want in the new script block in the front matter and then import and use components as well as plain old JavaScript tagged template variable interpolation (not shown in this example) inside your Markdown.
The screen has all the code (sans the end of the last line of CSS and the closing tags for the
Rewriting the Windows section of Kitten’s installation instructions.
Update: it’s live now.
#Kitten #SmallWeb #SmallTech #web #dev #HTML #CSS #JavaScript #NodeJS #FOSS #tech #Windows #Microsoft #israel #genocide #ethnicCleansing #apartheid #settlerColonialism #Palestine #Gaza #WestBank #StopIsrael #StopTheGenocide #BoycottDivestmentSanctions #BDS #FreePalestine
Looking for server recommendations for a friend:
- POC, AuDHD friendly
- Asian LGBT+ fan media (esp Thai BL)
- Creative arts, Indie Web (as a newbie), UI/UX, creative coding
- Language learning (Thai, Cambodian, Mandarin) and linguistics (like languages at risk of being lost or color processing)
My first thought was yesterweb, any other thoughts?
The new integrated Markdown parser I’ve been implementing in Kitten has been kicking my ass for the past few weeks but I think I finally have it fully working and seamlessly so. Expect a new release this/next week that brings the parsing of Markdown pages (.page.md files) in your apps up to the standard of the recently-improved runtime Markdown parsing in Kitten HTML tagged-template strings (within <markdown>…</markdown>
blocks).
The coolest thing is I was able to implement this without introducing any new syntax. In fact, I was able to simplify things so that you can now add arbitrary JavaScript to your Markdown pages within a multi-line script block in the YAML front matter (script: |
) and use JavaScript string interpolation syntax in your Markdown (and, of course, Kitten components and conditionals, which, themselves, rely on string interpolation).
The only place where you have to deviate from standard Markdown in your Markdown pages is if you have JavaScript string interpolations or Kitten components/conditionals in code fences within your Markdown. In that case, you’ll have to escape them (e.g., <\${Component} />
, \<if \${something}>something\</if>
, etc.). And, to be fair, the person most impacted by this is likely me as the Kitten documentation at https://kitten.small-web.org is written in Kitten so I had a lot of escaping to do. But for any other use case, it means that things should just work and work exactly as they do in JavaScript pages (page.js files).
Anyway, so this is going to be a breaking change so I thought I’d give you (the three of you playing with Kitten right now?) a heads up. Of course, I’ll be updating the documentation to reflect all this.
(Remember, Kitten is in pre-release and it’s the framework I’m building/using to create Catalyst – the Small Web hosting solution – and Yarn – a small web – peer to peer – personal site app. So Kitten isn’t the means, not the end. And, at least until the Version 1 API freeze, things can and will break. That said, there’s nothing stopping you from playing with it now and, to be fair, at this point, such breaking changes should become rarer and rarer).
💕
#Kitten #SmallWeb#SmallTech #web #dev#Markdown#JavaScript#HTML#CSS#JavaScript#NodeJS
Bloody hell, finally, I think I’m done with the Markdown support rewrite in Kitten.
The Markdown rule for interpreting four spaces as code fences has been the biggest pain in my neck during this whole ordeal but, bitching aside, it means the parser is now more accurate and thus stronger for it.
If all goes well, expect a Monday release :)
💕
#Kitten #SmallWeb#SmallTech #web #dev#Markdown#HTML#CSS#JavaScript#NodeJS
Looking for server recommendations for a friend:
- POC, AuDHD friendly
- Asian LGBT+ fan media (esp Thai BL)
- Creative arts, Indie Web (as a newbie), UI/UX, creative coding
- Language learning (Thai, Cambodian, Mandarin) and linguistics (like languages at risk of being lost or color processing)
My first thought was yesterweb, any other thoughts?
Hi, fedi! I'm crawling out of my hermit hole to share my new app, TumblBee, with you all 🐝
https://lilacpixel.itch.io/tumblbee
TumblBee is a pay-what-you-want cross-platform app for exporting your original #Tumblr posts (and pages) to Markdown or HTML. Back up your content and browse it locally, or export to Markdown and drop your posts into your favorite static site generator. (There's even a guide to exporting for Obsidian, if that's your thing.)
If you decide to give it a try, I'd love to hear about it! Boosts are, as always, hugely appreciated 💕 Thanks so much!
#software #tools#IndieDev#IndieWeb #SmallWeb #blogging #backup #markdown
Version 1.1.0 of TumblBee is now available:
https://lilacpixel.itch.io/tumblbee
This update adds support for resuming unfinished exports, plus a few bug fixes and other improvements.
More (and exciting!) updates to come very soon! (I hope!) Watch this space 👀
Happy Friday, fedi! Version 1.2.0 of TumblBee is now available!
https://lilacpixel.itch.io/tumblbee
A few small but nice tweaks in this update! You can now exclude empty reblogs from your exports, and self-reblogs will now link to the exported original post where possible. (Also: some new goodies for those of you who like finding Easter eggs. 🥚)
#software #tools#Tumblr#IndieDev#IndieWeb #SmallWeb #blogging #markdown
The new integrated Markdown parser I’ve been implementing in Kitten has been kicking my ass for the past few weeks but I think I finally have it fully working and seamlessly so. Expect a new release this/next week that brings the parsing of Markdown pages (.page.md files) in your apps up to the standard of the recently-improved runtime Markdown parsing in Kitten HTML tagged-template strings (within <markdown>…</markdown>
blocks).
The coolest thing is I was able to implement this without introducing any new syntax. In fact, I was able to simplify things so that you can now add arbitrary JavaScript to your Markdown pages within a multi-line script block in the YAML front matter (script: |
) and use JavaScript string interpolation syntax in your Markdown (and, of course, Kitten components and conditionals, which, themselves, rely on string interpolation).
The only place where you have to deviate from standard Markdown in your Markdown pages is if you have JavaScript string interpolations or Kitten components/conditionals in code fences within your Markdown. In that case, you’ll have to escape them (e.g., <\${Component} />
, \<if \${something}>something\</if>
, etc.). And, to be fair, the person most impacted by this is likely me as the Kitten documentation at https://kitten.small-web.org is written in Kitten so I had a lot of escaping to do. But for any other use case, it means that things should just work and work exactly as they do in JavaScript pages (page.js files).
Anyway, so this is going to be a breaking change so I thought I’d give you (the three of you playing with Kitten right now?) a heads up. Of course, I’ll be updating the documentation to reflect all this.
(Remember, Kitten is in pre-release and it’s the framework I’m building/using to create Catalyst – the Small Web hosting solution – and Yarn – a small web – peer to peer – personal site app. So Kitten isn’t the means, not the end. And, at least until the Version 1 API freeze, things can and will break. That said, there’s nothing stopping you from playing with it now and, to be fair, at this point, such breaking changes should become rarer and rarer).
💕
#Kitten #SmallWeb#SmallTech #web #dev#Markdown#JavaScript#HTML#CSS#JavaScript#NodeJS
The new integrated Markdown parser I’ve been implementing in Kitten has been kicking my ass for the past few weeks but I think I finally have it fully working and seamlessly so. Expect a new release this/next week that brings the parsing of Markdown pages (.page.md files) in your apps up to the standard of the recently-improved runtime Markdown parsing in Kitten HTML tagged-template strings (within <markdown>…</markdown>
blocks).
The coolest thing is I was able to implement this without introducing any new syntax. In fact, I was able to simplify things so that you can now add arbitrary JavaScript to your Markdown pages within a multi-line script block in the YAML front matter (script: |
) and use JavaScript string interpolation syntax in your Markdown (and, of course, Kitten components and conditionals, which, themselves, rely on string interpolation).
The only place where you have to deviate from standard Markdown in your Markdown pages is if you have JavaScript string interpolations or Kitten components/conditionals in code fences within your Markdown. In that case, you’ll have to escape them (e.g., <\${Component} />
, \<if \${something}>something\</if>
, etc.). And, to be fair, the person most impacted by this is likely me as the Kitten documentation at https://kitten.small-web.org is written in Kitten so I had a lot of escaping to do. But for any other use case, it means that things should just work and work exactly as they do in JavaScript pages (page.js files).
Anyway, so this is going to be a breaking change so I thought I’d give you (the three of you playing with Kitten right now?) a heads up. Of course, I’ll be updating the documentation to reflect all this.
(Remember, Kitten is in pre-release and it’s the framework I’m building/using to create Catalyst – the Small Web hosting solution – and Yarn – a small web – peer to peer – personal site app. So Kitten isn’t the means, not the end. And, at least until the Version 1 API freeze, things can and will break. That said, there’s nothing stopping you from playing with it now and, to be fair, at this point, such breaking changes should become rarer and rarer).
💕
#Kitten #SmallWeb#SmallTech #web #dev#Markdown#JavaScript#HTML#CSS#JavaScript#NodeJS
My book/comic review blog has been overhauled, with a full index and vastly improved navigation. 260+ fantasy/horror/SF reviews, some of them even kinda thoughtful! 🧐
🥳 New Kitten Release
Housekeeping:
• Updated runtime version to Node version 22.18.0 (latest LTS).
• Removed --experimental-global-customevent
in node launch command (as CustomEvent
is no longer behing the CLI flag since Node v19.0.0)
• Renamed --experimental-loader
flag to --loader
as the experimental prefix is no longer required.
Enjoy!
💕
#Kitten#KittenRelease #SmallWeb#SmallTech #web #dev#HTML#JavaScript#CSS#NodeJS
Ah, and also, forgot to mention this change:
Improved:
• Debugging your Kitten app is now easier when you run it using `INSPECT=true kitten …` as the Node runtime is launched using the `--inspect-brk` tag instead of the `--inspect` tag. This means that execution will wait for your debugger (e.g., Chromium’s DevTools at `chrome://inspect`, etc.) to connect before starting the server. This makes it possible to hit breakpoints that might previously have been impossible to reach as they occured before you had a chance to run the debugger.
Full change log:
https://codeberg.org/kitten/app/src/branch/main/CHANGELOG.md#2025-08-12
#Kitten #SmallWeb #SmallTech #NodeJS #debugger #debugging #web #dev #JavaScript
A space for Bonfire maintainers and contributors to communicate