import{_ as e,c as o,o as a,a5 as t}from"./chunks/framework.Mb1uu3dm.js";const _=JSON.parse('{"title":"Chronological","description":"","frontmatter":{"public":"true","slug":"chronological","title":"Chronological","prev":false,"next":false},"headers":[],"relativePath":"garden/chronological/index.md","filePath":"garden/chronological/index.md","lastUpdated":1717647948000}'),r={name:"garden/chronological/index.md"},i=t('<h1 id="chronological" tabindex="-1">Chronological <a class="header-anchor" href="#chronological" aria-label="Permalink to &quot;Chronological&quot;">​</a></h1><blockquote><p>Referenced by: <a href="/garden/digital-gardens/">Digital Gardens</a>, <a href="/garden/freeform-vs-chronological-dichotomy/">Freeform vs Chronological Dichotomy</a>, <a href="/garden/the-small-web/">The Small Web</a></p></blockquote><p>A collection of information that is tied to its creation or edit date</p><p>Part of the <a href="/garden/freeform-vs-chronological-dichotomy/">Freeform vs Chronological Dichotomy</a></p><p>Anything with a &quot;timeline&quot; or &quot;feed&quot; is considered chronological</p><ul><li>Even if there&#39;s algorithmic sortings that take things other than creation or edit date into account!</li></ul><p>Chronological displays are less suitable as stores of knowledge (<a href="/garden/digital-gardens/">Digital Gardens</a>)</p><p>Social media overuses timelines and feeds</p><p>RSS feeds work really well with this form of content</p>',9),l=[i];function n(c,s,d,h,g,f){return a(),o("div",null,l)}const m=e(r,[["render",n]]);export{_ as __pageData,m as default};