Outcome of our first call for contributors

August 01, 2019

#motivation #webdev #contributorswanted #opensource

Wow — Owen Wilson

Last week we published our first call for contributors for our open source project DeckDeckGo and the outcomes are just mesmerizing 🤩 Therefore, before going further, we would like first to thanks each and every persons who read the article, interacted with or volunteered to resolve issues and even sent us Pull Requests. You are truly awesome and your reactions cheered up all up, THANK YOU ❤️❤️❤️

Pull requests

Following our blog post, many persons contacted us to take over the issues we listed and even found other issues to solve in our repo 😜 Some of these are still in progress but two notable features have now been developed, that’s why we thought that it would be cool to display their outcomes and to give credits to their authors.

Before we start

Something I personally really like in our project is its modularity. All our web components could be use as standalone components in any applications (“with or without any modern frameworks”), or could be use in our starter kit if you are developing your presentation using HTML or Markdown (npm init deckdeckgo ) and are also used in our upcoming web editor for presentations.

It’s kind of cool to think, that if you are improving or fixing a component, this improvement could be use in so many constructs.

Optional line numbers for code highlighting

The goal of this feature was to add an option to our code highlighter component, which use Prism.js under the hood, in order to be able to automatically display line numbers at the begin of each lines.

This feature was developed by Stefan Nieuwenhuis (Twitter / Github) and was submitted in the PR #213. Not all heroes wear capes, you are awesome Stefan 👍

Automatically display line numbers at the begin of the code you want to showcase

Youtube short Url

We faced an issue with our component and “Youtube” template (which allow users and developers to easily integrate Youtube video in their presentations) when short url were used to embed video, as urls have to respect a specific format.

This fix was developed by Rohit Bokade (Github) and was submitted in PR #207. The force is strong with you Rohit, thanks a lot 👍

Integrate easily a YouTube video to your presentation

Cherry on the cake 🍒🎂

We still have issues to solve 🤣 Most of them flagged as “good first issue” are in progress and the others might not be that straight forward, but who knows, you might find one you are interested in and more important, we are really open to any idea or suggestions. Therefore don’t hesitate to submit your feature requests, that would be super cool.

To infinity and beyond 🚀

David

Blog

Read the article

Map a JSON file to ENUM in Java

August 16th 2019

#java #tutorial #webdev #maven

Read the article

Outcome of our first call for contributors

August 1st 2019

#motivation #webdev #contributorswanted #opensource

Read the article

Contribute to our open source project

July 26th 2019

#opensource #beginners #motivation #webdev

More articles

Address

Fluster GmbH c/o The Hub Zürich Association Sihlquai 131 8005 Zürich

On the web