denizk0461/pages
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added reference to mdsvex on about page

Browse Source
This commit is contained in:
denizk0461
2026-02-01 12:28:49 +01:00
parent 17c54456bc
commit 20cf98c375
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/routes/meta/about/+page.svelte
View File

@@ -86,7 +86,7 @@
<h4 id="software">Tools & Software</h4> <h4 id="software">Tools & Software</h4>
<p>My main IDE for writing this website is <a href="https://vscodium.com/">VSCodium</a>, and the website itself is developed using <a href="https://svelte.dev">SvelteKit</a>. I perceive SvelteKit as a relatively light web dev framework: it allows me to create easily-reusable components (like the header, footer, title banner, etc.) and I can also configure it to create HTML from markdown files (which is how I write posts for the <a href="/blog">Blog</a> and the <a href="/projects/projectn5">Project N5 devlog</a>). After setting it up, it's easier to add content than if I were to rawdog HTML – and it's a <b>lot</b> easier to change something if the need arises (which I do more often than I'd like to admit). A lot of the actual page creation is still done with almost entirely vanilla HTML/CSS though, so there's not <i>too</i> much to re-learn.</p> <p>My main IDE for writing this website is <a href="https://vscodium.com/">VSCodium</a>, and the website itself is developed using <a href="https://svelte.dev">SvelteKit</a>. I perceive SvelteKit as a relatively light web dev framework: it allows me to create easily-reusable components (like the header, footer, title banner, etc.) and I can also configure it to create HTML from markdown files (which is how I write posts for the <a href="/blog">Blog</a> and the <a href="/projects/projectn5">Project N5 devlog</a>). For this, I use <a href="https://mdsvex.pngwn.io/">mdsvex</a> by pngwn. After setting it up, it's easier to add content than if I were to rawdog HTML – and it's a <b>lot</b> easier to change something if the need arises (which I do more often than I'd like to admit). A lot of the actual page creation is still done with almost entirely vanilla HTML/CSS though, so there's not <i>too</i> much to re-learn.</p>
<p>This website uses two fonts: body text uses <b>Bai Jamjuree</b> by Cadson Demak (<a href="https://fonts.google.com/specimen/Bai+Jamjuree">G Fonts</a> | <a href="https://github.com/cadsondemak/Bai-Jamjuree">GitHub</a>), headers and monospaced text use <b>Kode Mono</b> by Isa Ozler (<a href="https://fonts.google.com/specimen/Kode+Mono">G Fonts</a> | <a href="https://github.com/isaozler/kode-mono">GitHub</a>).</p> <p>This website uses two fonts: body text uses <b>Bai Jamjuree</b> by Cadson Demak (<a href="https://fonts.google.com/specimen/Bai+Jamjuree">G Fonts</a> | <a href="https://github.com/cadsondemak/Bai-Jamjuree">GitHub</a>), headers and monospaced text use <b>Kode Mono</b> by Isa Ozler (<a href="https://fonts.google.com/specimen/Kode+Mono">G Fonts</a> | <a href="https://github.com/isaozler/kode-mono">GitHub</a>).</p>
@@ -98,5 +98,5 @@
<p>hmm... this website and everything else I make comes straight from my own hands and brain. No generative AI is used, ever.</p> <p>hmm... this website and everything else I make comes straight from my own hands and brain. No generative AI is used, ever.</p>
<p><i>Last updated: 2026-01-29</i></p> <p><i>Last updated: 2026-02-01</i></p>
</Content> </Content>