Readme - enhancement - screenshots

[johndpope]

This readme has some top level screen shots - would be helpful to see here. Looking into the api / graphql - it's most impressive - need to bubble this up to surface for people to see. https://github.com/daptin/daptin

[shreeharsha-factly]

@johndpope Sure we will update readme.

[deshetti]

@johndpope Thanks for taking the time to go through Dega, we really appreciate it. Agree with you on better documentation in the ReadMe on Github. @shreeharsha-factly will update it with some info soon.

At Factly, we use Dega in production for a couple of sites, but the CMS is still in active development. We are currently heads-down focusing on finishing developing and testing all the features required for a beta release. We believe in documentation as a key for the success of Dega and will be working on documenting all the features and also include good developer/admin documentation as well. We will focus on documentation once the beta vesion is completed.

I have opened a PR for a basic documentation site for now: https://github.com/factly/dega/pull/416

The above documentation site is published here: https://dega.factlylabs.com/

Also, note that the documentation is focused on Dega being a CMS for Fact-Checking organizations as that is how it was started. But, theoretically, with Dega, you should be able to develop anything that you could develop using WordPress, Ghost, etc. Meaning, all the core concepts of WordPress are part of Dega apart from their vast plugin directory. The difference with something like WP is that we are opinionated (yet flexible) when it comes to enforcing publishing best practices. For eg but not limited to:

• SEO, Schemas, etc are generated automatically without any extra effort from the publisher.
• Search is not on top of a sql database but on a relevant search engine like Meilisearch
• Built-in support for Image proxy server using ImageProxy
• Built-in notification support using Hukz
• A strong authentication, authorization framework built on Kavach with detailed entity level policies
• Built-in support for oembed proxy server for rich media using Iframely
• Support for multiple organizations and multiple spaces (websites) within each organization making it easy for not just publishers but also hosting providers to use Dega
• Built as microservices and is cloud-native at its core.
• Lightweight yet super performant being built on Golang

Once again appreciate your feedback once you take a look at it. It might be easier if you can connect to us on our https://slack.factly.org/ for a quick response.