Address Doc Hackathon Feedback Related to the Algolia Search

[praneesha]

Description

Need to address the items below in the Algolia search of B.io as per the internal hackathon feedback.

algolia.com/blog/ux/what-are-predictive-search-and-autocomplete/ could be helpful in configuring the items below in Algolia.

• Crawl BAL file code comments in Algolia (e.g., mime, quoted identifiers)
• Crawl keywords on the HTML in Algolia. (https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/)
• Check on embedding the Google search in B.io
• Include spec.ballerina.io in Algolia search
• Make Algolia to detect partial words (when searching for parse vs parsing, read vs reading)
• Check if we have analytical support in Algolia (what are the keywords people are searching for etc.)
• Hyperlinks are not crawled in Algolia (e.g., the word mime https://ballerina.io/learn/by-example/http-response-with-multiparts.html)

Related website/documentation area

Add/Uncomment the relevant area label out of the following.

Area/CommonPages

Describe your task(s)

A detailed description of the task.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

[praneesha]

Will be addressed via #5944.