Improvement suggestions for ETL page

[anupama-pathirage]

Description

1. Be consistent on the wording Realtime vs real-time. It is better to use the hyphenated form "real-time," which is more commonly accepted and used in formal writing.

2. It seems both title case and sentence case is used in blade titles. Be consistent and use sentence case always.

3. Can we use backticks to highlight the text instead of single quotes?

4. Better to use configurables?

5. Do we really need the retry config? As it is optional and not related to the concept explained in the blade, isn't it better to remove it?

6. Can we link to an example of data mapper too?

[pcnfernando]

5. Do we really need the retry config? As it is optional and not related to the concept explained in the blade, isn't it better to remove it?

I don't see harm in removing it. But, this is coming from the AI usecase samples https://ballerina.io/usecases/ai/#write-robust-api-powered-ai-applications
Do you think both use cases should be updated? @anupama-pathirage

[anupama-pathirage]

2. It seems both title case and sentence case is used in blade titles. Be consistent and use sentence case always.

This is not fixed. Check other two similar sub titles.

4. Better to use configurables?

Add githubAccessToken also as a configurable.

[anupama-pathirage]

5. Do we really need the retry config? As it is optional and not related to the concept explained in the blade, isn't it better to remove it?

I don't see harm in removing it. But, this is coming from the AI usecase samples https://ballerina.io/usecases/ai/#write-robust-api-powered-ai-applications Do you think both use cases should be updated? @anupama-pathirage

It is fine to have it in AI page in that explicit sample as its main point is about robust apis. So retry is a good thing to explain the robustness there.

But in the Refining data excellence title of the ETL page, we are talking about AI capabilities. So IMO it is an overhead to have retry config here.

[anupama-pathirage]

Closing as this is done and page is live. https://ballerina.io/usecases/etl/