brennen
/
wrt
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 27 Wiki Activity
Almost-minimal filesystem based blog.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
450 Commits
1 Branch
2.2 MiB
Branch: main
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'main'
${ noResults }
wrt/example/blog/public/1952/2/index.html

46 lines
1.4 KiB
Raw Permalink Normal View History

handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
​
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
​
​
​
​
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
​
​
​
​
​
​
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
​
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
​
​
​
​
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
​
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
​
filter-as-script approach using IPC::Cmd Dispatches filters listed in an entry's filters.prop to scripts under $wrt->{filter_dir}. This is inefficient, in that it starts an entire process (at least) per filtered entry. On the other hand, it's a pretty clean abstraction, and it means that filters could be implemented in whatever language. Adds filters/ creation to wrt init.
2 years ago
​
handle sites with an index file in the root - adds an example "flat" site with, for now, a single index in root for testing purposes - wrt-render-all handles default entry instead of just using "new" - EntryStore::all_renderable() correctly filters out paths ending in "/index" instead of "index", which if nothing else corrects a subtle bug that would have gotten in the way of naming something "windex" - WRT::handle() will return the contents of a root-level "index"
4 years ago
​
 
  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4.   <title>wrt::Wednesday, February 13, 1952</title>
  5. 

  6.   <meta name="keywords" content="some test stuff" />
  7. 

  8.   <meta name="description" content="a test wrt site" /> 
  9. 

  10.   <meta name="author" content="Example Author" />
  11. 

  12.   <link rel="stylesheet" href="https://example.com/css/p1k3.css" />
  13.   <link rel="icon" type="image/x-png" href="https://example.com/favicon.png" />
  14.   <link rel=alternate type="application/atom+xml" title="wrt atom feed" href="https://example.com/feed" />
  15.   <link rel=feed type="application/atom+xml" title="wrt atom feed" href="https://example.com/feed" />
  16.   <link rel="alternate" title="wrt JSON feed" type="application/json" href="https://example.com/feed.json" />
  17. </head>
  18. 

  19. <body>
  20. 

  21. <a href="https://example.com/" title="newest entries">new</a>
  22. <a href="https://example.com/all/" title="all entries">all</a>
  23. 

  24. 

  25. <h1>Wednesday, February 13, 1952</h1>
  26. 

  27. 

  28. 

  29. <article><div class="entry"><h1>Wednesday, February 13, 1952</h1>
  30. 

  31. <p>I still miss you.</p>
  32. 

  33. <p class="datestamp"><a href="https://example.com/">wrt</a> /
  34. <a href="https://example.com/1952/" title="1952">1952</a> /
  35. <a href="https://example.com/1952/2/" title="2">2</a> /
  36. <a href="https://example.com/1952/2/13/" title="13">13</a></p>
  37. </div></article>
  38. 

  39. <div class=entry-metadata></div>
  40. 

  41. <p><small><em>public domain</em></small></p>
  42. 

  43. <p><p>next: <a title="next" href="https://example.com/2013/1">2013/1</a></p></p>
  44. 

  45. </body>
  46. </html>