Introduce code component/renderer documentation

[richard-jones]

• PR: [when the PR is created, put a link to it here. DO NOT use the "linked PR" feature]

---

Find a good way to document the code so that it's easy for developers to pick up.

Acceptance Criteria

• Code is documented
• Documentation is publishable as a website

[varadekd]

@richard-jones

I have investigated few documentation tools that can be used by us for creation and maintenance of the documentation for edges. Here is the list

1. Gitbook
2. Notion
3. Basecamp
4. Github Wiki

IMO, we should use Gitbook, it is easy to use and also supports version controlling either from Github or Gitlab. A sample documentation can be read here: https://kushagras-learning.gitbook.io/solr9_nested_and_graph