In reply to Anuj Ahooja
Any idea how sequoia would treat, or standard.site lexicons would interact with, a static front end that pulls data from a CMS on build? Would it need to be local .md files with front matter? Assuming yes but wondering (hoping) not.
I *think* it does, but @stevedylan.dev is probably the right one to ask
Yeah currently sequoia reads the local frontmatter to create the standard.site lexicons (text content isn't required, just a bonus). That means if you have a CMS there is likely a way to build some kind of script/workflow that creates the records based on the info. Happy to help if you need it! :)
What's even more wild is that basically the PDS can act as the CMS:
- Create the records on the PDS as standard.site lexicons from the start
- Have a static site request to the PDS based on the path/params
- Render the posts based on the content schema of your choice
Such a cool system
I use Ghost as a more professional blog/newsletter, but then use tags to route microposts and photos to a static site front end. Iād love to integrate standard.site lexicons at some point, but need to educate myself more.
I know I've seen someone attempt Ghost but it is tricky since its generally content hosted on another server. I could see some kind of script that downloads raw data from Ghost, creates the records, then creates some kind of state tracking to make sure nothing is duplicated.
Anyway if you end up wanting to attempt something or have more questions about standard.site in general I'm happy to chat anytime! I think it's a really cool advancement in connected and aggregated content publishing.
I wired up saving long form posts with standard.site lexicons directly from an iOS app I'm working on. That way I don't have to mess with image uploads, static builds, etc. my @ghost.org blog at lowvelocity.org is actually showing up in the @leaflet.pub and @pckt.blog feeds. Not perfect, but works.
I am curious about this because it seems like the opposite of a CMS, but replaces GIT. I may not be understanding fully as
I am teaching myself as a hobby and not very knowledgeable. I have seen people use plugins for Obsidian as a front end to negate a CMS.
Sorta! Git is primarily for version control while the PDS is really just a special server with folders and files. If you haven't seen pds.ls I think its worth exploring to see how it's all structured. If you click up the tree you can see how its organized pds.ls/at://did:plc...