5 ms·

Shameless plug but I built a tiny unopinionated static site generator that is great for blogs. No toolchain or anything fancy, I just added RSS support too :) I

Shameless plug but I built a tiny unopinionated static site generator that is great for blogs. No toolchain or anything fancy, I just added RSS support too :) It would be my pleasure if someone wants to try it https://github.com/donuts-are-good/bearclaw https://github.com/donuts-are-good/bearclaw

pcthrowaway 4y ago
Just gave it a (very) quick look > a static site is a site with no fancy clicky things, signups, comments, just plain html Technically I think you can have comments via some embedded widget. Each page is still static, but there's a script tag in there that embeds a widget into the page that gives you commenting, usually via some SaaS I think Disqus was the big one for a while. There was one I saw recently that uses github as the auth provider, which was interesting
- veyh 4y ago
  Cactus Comments [1] is another option. It uses Matrix under the hood. [1] https://cactus.chat/ https://cactus.chat/
  - lagniappe 4y ago
    oooh I like that, thanks!
- lagniappe 4y ago
  Hey thanks for checking it out :) I have been thinking about the comments feature. It's like peas and carrots having comments on a blog. I have almost added them before, but didn't for fear it would sacrifice any of the simplicity - which led me to think about modules/plugins. I like the idea of plopping down a folder or zip that the Bearclaw binary then reads and incorporates. Maybe that's feasible, maybe it's not. I'm going on a walk in a little bit and will give thought to a plugin system. Any ideas you have in mind?
- lagniappe 4y ago
  I have now added plugin support. This week I will write some sample plugins and then make a gallery for people to see them. Thanks for the inspiration!
  - lagniappe 4y ago
    The first sample plugin is complete, along with the handling for it during build time :) I'll add the gallery tomorrow!
indigodaddy 4y ago
This looks fantastic! I was going to mess about with Picocms but going to try this instead in conjunction with either Caddy or a spare shared hosting I’ve got laying around. And for the composing I will either tack on staticcms, or spin up a fly.io instance of stackedit (which I will push my md’s/edits from there to GitHub and bearclaw). You were trying to keep things simple and here I go trying to complexify it lol.. I’ll try to remember to let you know how it turns out after I get it all going..
- lagniappe 4y ago
  Oh that's great! Let me know what you think. After work today I'm creating a demo of the plugins system.
  - indigodaddy 4y ago
    Will do. FYI when I load bearclaw.blog on iOS chrome I get ERR_SSL_PROTOCOL_ERROR and no (obvious) options to proceed past that..
    - lagniappe 4y ago
      oops Sorry about that. I just purchased the domain and stuck it there then promptly fell asleep. I'll remove it for now and then route it to a bearclaw page when I get done working tonight.
      - indigodaddy 4y ago
        Figured something like that. And also for the md files. Just straight up content in there and no frontmatter or anything right? (May not even be a thing for md files, not sure)
        lagniappe 4y ago
        Essentially what's happening is it takes your markdown content then converts it to HTML, then it puts the header above and the footer below. Those are held in `./templates` if you want to modify them. You don't have to include anything in your markdown other than the content, if I'm understanding your question correctly. Also, one thing I'd like to sort out is making the page titles on the pages.html page that it generates not be based on the filename, but on the title of the article so-you-dont-see-stuff-like-this on pages.html. As of yesterday since I added config variables, I'd like to relocate those to an external file to avoid recompile, and then use those to populate the header so that people don't take time to fill in the config and then still get "Bearclaw Blog" when they fire it up. I really appreciate the time you're taking to talk this out with me, it's very inspiring and I'm getting lots of ideas. I can't wait to get done with Job 2 today so I can hammer out some of these things :) Thank you

pcthrowaway 4y ago

Just gave it a (very) quick look > a static site is a site with no fancy clicky things, signups, comments, just plain html Technically I think you can have comments via some embedded widget. Each page is still static, but there's a script tag in there that embeds a widget into the page that gives you commenting, usually via some SaaS I think Disqus was the big one for a while. There was one I saw recently that uses github as the auth provider, which was interesting

veyh 4y ago
Cactus Comments [1] is another option. It uses Matrix under the hood. [1] https://cactus.chat/ https://cactus.chat/
- lagniappe 4y ago
  oooh I like that, thanks!
lagniappe 4y ago
Hey thanks for checking it out :) I have been thinking about the comments feature. It's like peas and carrots having comments on a blog. I have almost added them before, but didn't for fear it would sacrifice any of the simplicity - which led me to think about modules/plugins. I like the idea of plopping down a folder or zip that the Bearclaw binary then reads and incorporates. Maybe that's feasible, maybe it's not. I'm going on a walk in a little bit and will give thought to a plugin system. Any ideas you have in mind?
lagniappe 4y ago
I have now added plugin support. This week I will write some sample plugins and then make a gallery for people to see them. Thanks for the inspiration!
- lagniappe 4y ago
  The first sample plugin is complete, along with the handling for it during build time :) I'll add the gallery tomorrow!

indigodaddy 4y ago

This looks fantastic! I was going to mess about with Picocms but going to try this instead in conjunction with either Caddy or a spare shared hosting I’ve got laying around. And for the composing I will either tack on staticcms, or spin up a fly.io instance of stackedit (which I will push my md’s/edits from there to GitHub and bearclaw). You were trying to keep things simple and here I go trying to complexify it lol.. I’ll try to remember to let you know how it turns out after I get it all going..

lagniappe 4y ago
Oh that's great! Let me know what you think. After work today I'm creating a demo of the plugins system.
- indigodaddy 4y ago
  Will do. FYI when I load bearclaw.blog on iOS chrome I get ERR_SSL_PROTOCOL_ERROR and no (obvious) options to proceed past that..
  - lagniappe 4y ago
    oops Sorry about that. I just purchased the domain and stuck it there then promptly fell asleep. I'll remove it for now and then route it to a bearclaw page when I get done working tonight.
    - indigodaddy 4y ago
      Figured something like that. And also for the md files. Just straight up content in there and no frontmatter or anything right? (May not even be a thing for md files, not sure)
      - lagniappe 4y ago
        Essentially what's happening is it takes your markdown content then converts it to HTML, then it puts the header above and the footer below. Those are held in `./templates` if you want to modify them. You don't have to include anything in your markdown other than the content, if I'm understanding your question correctly. Also, one thing I'd like to sort out is making the page titles on the pages.html page that it generates not be based on the filename, but on the title of the article so-you-dont-see-stuff-like-this on pages.html. As of yesterday since I added config variables, I'd like to relocate those to an external file to avoid recompile, and then use those to populate the header so that people don't take time to fill in the config and then still get "Bearclaw Blog" when they fire it up. I really appreciate the time you're taking to talk this out with me, it's very inspiring and I'm getting lots of ideas. I can't wait to get done with Job 2 today so I can hammer out some of these things :) Thank you