Another developer reflects on integrating his site with standard.site, finding that Sequoia "handles the core use case reasonably well, but it doesn’t ... support ... multiple publications on a single site", whereas he wants publications for notes (articles and writing), projects (long-lived project writeups) & ramblings.
Another issue is that "sites like Leaflet will try to reference the content ID ... when they’re linking... but I like having pretty URLs... I’m thinking about finding Leaflet’s code and trying to fix that. ... Greengale will use the proper path, but because Sequoia isn’t setting those paths up the way I expect, links still don’t always resolve correctly." He also finds Sequoia struggling with his frontmatter, and has questions and suggestions about how it processes his content.
Overall he seems to have a bit of an existential crisis at one point: "I don’t know if I want my blog to be an app view, or if I want my blog to be the actual thing".
But he seems to have something working correctly, with the blog post's comments being pulled in from bluesky.
More Stuff I Like
More Stuff tagged atprotocol , blog , sequoia , standard.site
See also: Bluesky and the ATmosphere , Content Strategy , Social Media Strategy , Content Creation & Marketing , Communications Tactics , Social Web
MyHub.ai saves very few cookies onto your device: we need some to monitor site traffic using Google Analytics, while another protects you from a cross-site request forgeries. Nevertheless, you can disable the usage of cookies by changing the settings of your browser. By browsing our website without changing the browser settings, you grant us permission to store that information on your device. More details in our Privacy Policy.