-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nimib document compilation #245
Comments
Agree it makes sense to have this part of the process accessible as a standalone, not sure about the name. Ideally in the beginning How to proceed now is tricky, it might even that the planned big refactoring might give us a hand there (the additional tasks could be default blocks added in some automatic way at the end?), but we are a bit stuck there. (Start off topic) In general very happy to see all these activities @neroist 👏 ❤️ With @HugoGranstrom we are due a nimib speaking hours, would you be interested in joining if we organize it? (Feel free to decline with absolutely no need for explanation, just thought I should offer) |
Is the blog public? Link? |
I think this should be easier to do after the refactoring. I want to remember that rendering a nimib document modifies the context and such you can't render the same document twice. After the refactoring we are planning to make all the steps of the rendering much more defined such that the context isn't changed for example, allowing you to render a document using multiple backends for example.
100% agree with this! Thanks @neroist ❤️ |
The entire blog is in toki pona lol, but its available at https://neroist.github.io/niko.old/! I'm currently in the process in porting it over to HappyX & setting it up with the domain I bought. |
Thank you both! @HugoGranstrom @pietroppeter ❤️ |
lipu pona!
💛 |
sina sona e toki pona la pona mute a! 😆 |
mi sona lili e toki pona... ...but I do love it 💘 and I can get help from chatGpt 😇 |
I think it would be nice to have a routine to "compile" a nimib document (ie do everything that
nbSave
does, but instead of writing a file it returns a string of the generated markdown/html). Very simple, here's what I use (for my personal website/blog thingy):My main use case for this is compiling a lot of nimib documents at once. This is so much more faster than compiling every single file. There are, of course, a myriad of other uses too.
The text was updated successfully, but these errors were encountered: