Bug report comments

[renoirb]

Hi Tracey,

I noticed your comments aren't displayed anymore and staticman seem to be erroring.

For example the comment you made for blogtini.com/2020-07-like-kubernetes-k3s-is-dead-on-floor-fast doesn't display.

---

Initial comment

This blogtini thingy is amazing! After an half-finished WordPress migration that started before COVID-19, I recently was wondering how I could have a page in a path/foo/bar.md load markdown and by some magic load that application-layout (the common "web app Chrome").

I never thought to do path/foo/bar.html and insert raw markdown like you're doing. Smart! Even using script[type=module] sweet!

My half-finished attempt was with using nuxt-content. But it's a bit too much.

I recently tried close to what you're doing by having some HTML document to load from GitHub using JSONP. See this Gist, open it in a browser or try renoirb.com/286211f2c32d41c955a43a40723df535.html

---

Your commenting system

Looking at the code though and seeing your GitHub repo comments, they aren't shown.

Known bug?

Have you thought of changing js/blogtini.js to have a customElement and load them and use them as normal tag? That'd be neat to avoid writing to .innerHTML = '...' too much

KUTGW!

(I've tried writing a comment on your site to see if you staticman instance will do something. It didn't.)

[traceypooh]

hi @renoirb !
sorry for the delay...
yes, I have a "fixme" too hook-in & allow blogtini.com to use the staticman small deploy in order to post comments (as new JSON files into PR for the repo/blog being commented on -- for the blog author to consider and merge or ignore/delete).

i could certainly "accept list" domains to it -- but OTOH it seems like it could be good to alter/update its backing codebase to allow (say) comment POSTs from any site out there that is using blogtini.js or some alt. way to verify that.