Stats

Basic deckdeckgo repo stats
3
1,177
9.9
about 21 hours ago

Deckdeckgo Alternatives

Similar projects and alternatives to deckdeckgo based on common topics and language

  • GitHub repo esbuild

    An extremely fast JavaScript bundler and minifier

  • GitHub repo Ionic Framework

    A powerful cross-platform UI toolkit for building native-quality iOS, Android, and Progressive Web Apps with HTML, CSS, and JavaScript.

  • GitHub repo stencil

    A Web Component compiler for building fast, reusable UI components and static site generated Progressive Web Apps

  • GitHub repo Blaze UI

    Atoms for Blaze UI (by BlazeUI)

  • GitHub repo blaze

    Atoms for Blaze UI [Moved to: https://github.com/BlazeSoftware/atoms] (by BlazeCSS)

  • GitHub repo ionicons

    Premium hand-crafted icons built by Ionic, for Ionic apps and web apps everywhere 🌎

  • GitHub repo date-picker

    Duet Date Picker is an open source version of Duet Design System’s accessible date picker. Try live example at https://duetds.github.io/date-picker/ (by duetds)

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better deckdeckgo alternative or higher similarity.

Posts

Posts where deckdeckgo has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-05-24.
  • Build A Library With esbuild
    dev.to | 2021-05-24
    I recently developed plugins and, migrated all the utilities of DeckDeckGo to build these with esbuild.
  • Bundling Figma Plugin With Esbuild
    dev.to | 2021-04-20
    I recently published a new open source plugin to export Figma frames to DeckDeckGo slides.
  • Firebase Cloud Functions: Verify Users Tokens
    dev.to | 2021-04-01
    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.