![]() notes and articles as YAML files with HTML in (wants to change these to HTML+mf2 for browsability, standards support).Stores all canonical copies of .uk site data in the filesystem and uses Taproot for publishing. Rascul stores content for in a git repository and uses crash. It has its ups and downs, but its a mix of 3 weird languages which really bothers me. Yuuuuuck! This is what jekyll sets you up with. Yaml headers (aka front-matter) with GitHub flavored Markdown mixed with liquid template include tags for post attachment metadata. comments - stored as html in the same directory as the postīret Comnes uses the following on bret.io:.webmentions - stored as html in the same directory as the post.posts - since stored as text with some textual/markdown/whatever markup, with one file per post, named year+day-of-year, key:value header for metadata and a json blob for connected resources. ![]() Kevin Marks on stores posts formatted as HTML in GitHub and deploys statically to Heroku.īear at uses Hakkan uses flat files for storage of all content: 2008-08 static site directly served from primary storage of flat files, up to 12 per year (1 per Gregorian month).Īaron Parecki on uses p3k - one file per post, YAML extensions for meta info - since ~2011. present: Falcon which stores data in HTML+microformats flat files, 6 per year (1 per bim). Tantek Çelik on uses flat files for primary storage of content: IndieWeb community members that use file storage on their personal site. time sharded: a set of posts per fixed time period per flat file.Markdown with custom (per project) extensions for various metadata.See also the databases-antipattern for reasons why flat files for storage are growing in popularity compared to databases. Many indieweb projects are storing their data in flat files on the file system for reasons of simplicity and robustness.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |