blaze VS deckdeckgo

BlazeCSS/blaze - Open Source CSS Toolkit

We are developing a proof of concept to port our web app, DeckDeckGo, to DFINITY's Internet Computer.

Exciting news, we received a 25k USD grant from the DFINITY foundation to port our web editor for slides, DeckDeckGo, to the Internet Computer.

I recently developed plugins and, migrated all the utilities of DeckDeckGo to build these with esbuild.

I recently published a new open source plugin to export Figma frames to DeckDeckGo slides.

Anyone can try out DeckDeckGo, there is no mandatory login or sign-in upfront if you just want to give it a try. It is something really important to us, we are not chasing data or number of users, we are developing an editor for presentations for users’ who want to use it, or not 😉. That being said, if users want to share publicly their presentations, because we don’t want to have too much “This is a test” or “Yolo” decks publicly published, respectively avoid if possible not meaningful public content, we do restrict our “publishing process” (the one in which we transform and deploy the presentations online as Progressive Web Apps), to signed users. For these processes, we are using the ability given by Firebase to use anonymous users. That’s why, in addition to verify the tokens, I also add to check this information. Fortunately, this can also be solved easily, as the payload provided by the verifyToken function does contain such information.