pull down to refresh

Using Drupal open-source code does not make this tool open-source itself.
Why? Mostly because
  • Code powering the website is not available for fork/review/contributions.
  • People cannot submit new apps or edit existing ones.
The easier option would be to add a form for people to submit new apps or edit existings ones.
Even so, using such powerful dinosaur for such simple project does not feel appropriate to me. A simple jekyll static website (or similar) hosted on git would do much better and easy for others to maintain as it uses markdown, a formatting language that is intuitive and easy to learn. You could actually deploy in some blossomservers.com for hosting the website and use gittr.space as a code repository.
Don't get me wrong, I truly appreciate such projects. The issue is that typically we use what we aim to deliver what we can, and is not enough for it to make it successful and useful for the masses. Allow others to contribute.
0 sats \ 1 reply \ @sebastix 19h
You're correct on all the points.
As a Drupal specialist I've helped @jurjendevries to setup this Drupal powered website. I also know that Jurjen is not very familar with Git (yet), but I'm sure he will be totally fine to host the code somewhere in a public repo (using ngit). Deploying it as a static website (nsite) won't be possible, as Drupal is still a 'classic' PHP powered website which needs a webserver to handle the requests.
reply
Yes correct, I was referring to a site built with jekyll or similar static frameworks to be hosted on GH pages or somewhere else that is easier to contribute and keep the list updated.
reply