<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title><![CDATA[ Bootstrapping DokMelody - pckt ]]></title>
        <link><![CDATA[ https://bootstrapping-dokmelody.pckt.blog ]]></link>
        <description><![CDATA[ My attempt at bootstrapping DokMelody ]]></description>
        <language>en</language>
        <pubDate>Sat, 19 Sep 2026 19:38:58 +0000</pubDate>

                    <item>
                <title>DokMelody</title>
                <link>https://bootstrapping-dokmelody.pckt.blog/dokmelody-v73dy0t</link>
                <description><![CDATA[DokMelody is a federated system for programming and sharing information between individual users, groups and communities. It is composed of different systems: In this blog I will document the initial development and bootstrapping process of DokMelody.]]></description>
                <author>Bootstrapping DokMelody</author>
                <guid isPermaLink="false">dokmelody-v73dy0t</guid>
                <pubDate>Thu, 17 Sep 2026 21:13:06 +0000</pubDate>
                            </item>
                    <item>
                <title>The long journey towards Dok AST</title>
                <link>https://bootstrapping-dokmelody.pckt.blog/the-long-journey-towards-dok-ast-pzdgfky</link>
                <description><![CDATA[Now I can parse Dok (a first version of it) and generate its Abstract Syntax Tree (Dok AST). commit/a43417024115fa586dd7b4be2a27f92b87a91c0b The followed approach is far from pragmatic, but I&#039;m experimenting some paradigms that I would use also in the final project: I have the Dok grammar, written using the tree-sitter formalism. Tree-Sitter tools are used for generating a JSON description of the Dok grammar.]]></description>
                <author>Bootstrapping DokMelody</author>
                <guid isPermaLink="false">the-long-journey-towards-dok-ast-pzdgfky</guid>
                <pubDate>Thu, 17 Sep 2026 21:54:25 +0000</pubDate>
                            </item>
            </channel>
</rss>