- Make
<kbd>
tags work in Markdown component - Fix css duplicated by Markdown in
<svelte:head>
- Find a way to use
hljs.highlightElement
in Mardown to avoid callinghighlight
on already highlighted code. Maybe replacehljs
byprism
as I do on www.statox.fr because the highlighting is slightly better - Fix
audioContext
on iOS Safari in Metronome page - Find a better way to store authentication token. For now they are insecure in the local storage
- Add checks to allow dependabots MRs to be merged automatically
- Add link to the last GitHub Pages deployment
- Rework
fetch
calls into a framework for unified access to api.statox.fr - Rework CSS. Default should be dark theme. Add a button to switch themes
- Extend colors to get warning red, info blue, success green, ...
- Recreate mechanism to open note in its own page
- Rework home page to be more descriptive and useful
- Get toast library from https://github.com/zerodevx/svelte-toast/blob/master/src/lib/ToastItem.svelte
- Clean up the
getAccessToken()
function so that it doesn't returnstring | undefined
and handle errors properly.
- Create Tuner app in the music section
- See how to integrate statox setup maybe with some notes or guidance
- Integrate my color picker?
- Imagine a CMS-like system to add data to a todo list
For now environement variables are all public (only the backend url so far) and can have different values depending on the environement:
- Write values for local dev in
env.local
- Write values for prod in
env.prod
A script in svelte.config.js
copies the file corresponding to the environement in .env
.
The variables can then be read from components with:
import { PUBLIC_API_URL } from '$env/static/public';
When adding a new value run npx svelte-kit sync
to avoid errors like
Module '"$env/static/public"' has no exported member VARIABLE_NAME
Notes about CSS and markdown https://joshcollinsworth.com/blog/build-static-sveltekit-markdown-blog