this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Rss test

Tholp 223a1dcb 6e668b50

+30 -13
+10
content/style.css
··· 50 50 51 51 --text-mild: #b07a5f; 52 52 53 + --attention: rgb(255, 191, 0); 54 + --attention-bg: rgba(255, 191, 0, .4); 55 + 53 56 font-family: "Gontserrat", "Noto Sans", sans-serif 54 57 } 55 58 ··· 669 672 h1, h2, h3 { 670 673 font-family: "Gontserrat Semibold", sans-serif; 671 674 } 675 + 676 + blockquote { 677 + border-left: 6px solid var(--attention); 678 + background: var(--attention-bg); 679 + margin-left: 10px; 680 + padding-left: 20px; 681 + }
+2 -2
skid/blog/blog1.sk
··· 1 - &insert("//style.sk") 2 - &insert("blog_templates.sk") 1 + !insert("//style.sk") 2 + !insert("blog_templates.sk") 3 3 4 4 !blog_post( 1 "Is This Thing On?" "2-6-2025" "The 'thlog'? probably not.") 5 5 {{{
+3 -3
skid/blog/blog2.sk
··· 1 - &insert("//style.sk") 2 - &insert("blog_templates.sk") 1 + !insert("//style.sk") 2 + !insert("blog_templates.sk") 3 3 4 4 !blog_post( 2 "An Overview on Skidmark" "2025-7-11" "Nominative determinism in software") 5 5 {{{ ··· 141 141 142 142 Templates are defined with the `template` macro, `template`'s first parameter is the name of the new template, additional arguments are used as parameters for the new template. within the block is the content of the template, the values of a template's parameters are used by enclosing the name of it in double brackets, like this: `[[arg]]` a template can also use blocks with `[[\{}]]`, and accept trailing arguments outside of the initial definition with `[[..]]` or `[[".."]]`. `[[..]]` pastes all trailing arguments space separated, `[[".."]]` pastes all arguments with quotes around them, also space separated. 143 143 144 - You may have noticed the different prefixes on macros notably: `\!&section()` and `\&section()`. The `section` macro has the uninteresting behavior of expanding to it's unmodified input block, it's prefix is what makes it useful. All macros can be prefixed with `\!`, `\&` or `\!&`. Which is chosen changes how it behaves when inserted into another file. 144 + You may have noticed the different prefixes on macros notably: `!\&section()` and `\&section()`. The `section` macro has the uninteresting behavior of expanding to it's unmodified input block, it's prefix is what makes it useful. All macros can be prefixed with `\!`, `\&` or `\!&`. Which is chosen changes how it behaves when inserted into another file. 145 145 146 146 * `\!` will always expand no matter where it came from 147 147 * `\&` will only expand if its file of origin is the same as the one currently being processed.
+2 -2
skid/blog/blog3.sk
··· 1 - &insert("//style.sk") 2 - &insert("blog_templates.sk") 1 + !insert("//style.sk") 2 + !insert("blog_templates.sk") 3 3 4 4 !blog_post( 3 "Rainy Bass" "2025-7-30" "Not fishing for compliments") 5 5 {{{
+4
skid/blog/blog_templates.sk
··· 37 37 &page_title("Blog #[[number]]: [[title]]") 38 38 &basic_embed("Blog #[[number]]: [[title]]" "[[desc]]") 39 39 40 + !&section(title){{{[[title]]}}} 41 + !&section(blurb){{{[[desc]]}}} 42 + !&section(date){{{[[date]]}}} 43 + 40 44 !construction() 41 45 42 46 <header style="text-align: center;">
+9 -6
skid/blog/rss.sk
··· 1 1 <?xml version="1.0" encoding="UTF-8" ?> 2 2 <rss version="2.0"> 3 - 4 3 <channel> 5 - <title>Thlog</title> 4 + <title>The Thlog</title> 6 5 <link>https://tholps.site</link> 7 6 <description>Tholp's Blog</description> 8 - !for_each_file_in_group("blog") 7 + <generator>Skidmark</generator> 8 + <webMaster>tholp@tholps.site</webMaster> 9 + !for_each_file_in_group( file "blog") 9 10 {{{ 10 11 <item> 11 - <title>\!insert([["..file"]] "Title")</title> 12 - <link>https://tholps.site/blog/\!filename([["..file"]])</link> 13 - <description>\!insert([["..file"]] "description")</description> 12 + <title>!insert("[[file..1]]" "title")</title> 13 + <guid>https://tholps.site/!output_filename("[[file..1]]")</guid> 14 + <link>https://tholps.site/!output_filename("[[file..1]]")</link> 15 + <description>!insert("[[file..1]]" "blurb")</description> 16 + <pubDate>!insert("[[file..1]]" "date")</pubDate> 14 17 </item> 15 18 }}} 16 19 </channel>