Skip to content

Improve README

ng-druid edited this page May 26, 2022 · 17 revisions

Engagement activities could be higher. Reevaluate content of main readme for higher engagement and interest. The current readme is targeted mostly towards devs. Instead of doing that lets try a different approach this time around. The target will be climate enthusiast that are not necessarily developers. This might lead to more engagement success pending ng-druid.com. The primary audience can also be re-evaluated at every level of marketing and content.

In order to achieve this goal content needs to talk about specific features as they relate directly content publishing of builders rather than perhaps dev. Advanced topics with REST integration can be kept to dev documentation or advanced features. Datasources will be discussed but only on the surface using static data sets rather than remote APIs initially. It may be worth considering how using remote APIs can be made more none developer friendly.

Begin with explaining how to implement key components of content publishing using druid.

  • html pages
  • markdown pages
  • forms
  • lists
  • tables
  • data tables

Druid is a new kind of publishing platform that will run on 100% renewable energy by 2025. In addition to running on clean energy additional measures have been taken to significantly reduce energy consumption. Druid achieves this feat via eliminating servers and infrastructure from the web hosting equation. In contrast to traditional websites druids run completely in the browser and communicate securely directly with resources in the cloud when necessary. Druid is designed to build the web back better on the net 0 web without sacrificing latency, availability, responsiveness, or scalability.

Clone this wiki locally