fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-24 01:42:10 +00:00
Code Issues Projects Releases Wiki Activity

New note: welcome to the IndieWeb

Browse source
This commit is contained in:
Rohan Kumar 2022-06-20 14:30:25 -07:00
parent 1e2595cfe3
commit b3a676c72d
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
content/notes/welcome-to-the-indieweb.md Normal file
View file

@ -0,0 +1,22 @@
---
title: "Welcome to the IndieWeb"
date: 2022-06-20T14:30:24-07:00
replyURI: "https://www.miriamsuzanne.com/2022/06/04/indiweb/"
replyTitle: "Am I on the IndieWeb Yet?"
replyType: "BlogPosting"
replyAuthor: "Miriam Suzanne"
replyAuthorURI: "https://www.miriamsuzanne.com/who/"
---
Welcome to the IndieWeb, Miriam!
> I've struggled to categorize what on my wite is a "post" worth syndicating vs a "page" vs ???
I had this struggle too, and solved it with per-section and combined feeds. [My combined feed](https://seirdy.one/atom.xml) contains every page on my site that includes a publication date in its metadata; my sections for articles and notes have their own respective feeds.
> If I want live updates (this is a static site) there’s still more to learn.
Remember that pretty much all IndieWeb features are optional. You only have to implement what interests you. You can get really far when it comes to bringing a static site to the IndieWeb, so I'd suggest against jumping onto a dynamic site immediately.
You can also push live updates using WebSub. Your main site can still be static, but you can pint a (first- or third-party) WebSub hub to push content as soon as you update your site. I plan on using this approach soon.
I like the "static site with ancillary services" model: it keeps the core fast and simple, and makes extra modules easy to add and replace.