docs(chart):add KB to link to export example

[NansiYancheva]

Related to: https://github.com/telerik/blazor/issues/7634

[yordan-mitev]

The value of this KB is questionable at best as it lacks content. I would suggest reworking it and adding at least the primary steps required to export the Chart as an image. You could of course keep the link to the GitHub project with the complete implementation.

[NansiYancheva]

The value of this KB is questionable at best as it lacks content. I would suggest reworking it and adding at least the primary steps required to export the Chart as an image. You could of course keep the link to the GitHub project with the complete implementation.

@yordan-mitev

The reasons for the KB appearing as it does are:

1. The main reason for creating the KB is the lack of a link to the GitHub project in the documentation.
2. The GitHub project has instructions. We aim to avoid duplication of the guidelines (and their maintenance). The KB indicates that the GitHub project contains a README file with instructions.
3. We have another KB that looks the same https://docs.telerik.com/blazor-ui/knowledge-base/chart-print-chart-only
4. Additionally, we are planning to deprecate the GitHub repository and extract what is possible into KBs. In the meantime, we are trying to avoid duplicating guidelines while still utilizing available resources.

If these reasons are not acceptable, I will include the instructions from the GitHub project in the KB.

[ntacheva]

We have this type of KB articles for most projects in the blazor-ui repo. Their main purpose is to provide a link to the corresponding project.

Indeed, we have previously discussed that such KBs do not have much value. In addition, a lot of the customers do not like the idea of having to browse to the repo and download the app in order to just test the specific scenario. That said, we will have an initiative for extracting all projects to KBs and deprecate the blazor-ui repo. This, however will take time and we better have the KB linking the app until then.

[github-actions]

Hello @ntacheva,

Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.

• create PR to production

[NansiYancheva]

@yordan-mitev please let us know if you are ok with the proposed approach

[yordan-mitev]

@yordan-mitev please let us know if you are ok with the proposed approach

You are free to add the file as is. This, however, is not an actual KB and has no value.

• The main idea of a KB is to allow our clients to find solutions on their own. They cannot find a solution if it isn't described in an article that has sufficient content to allow search engines to index it.
• A KB that isn't indexed or ranked high serves no purpose if you are the one who has to send the link to the client.

[github-actions]

Here you are the link to your PR to production: 2138