SDK: Improve All Examples Documentation

[rjvelazco]

Parent Issue

#30943

Task

As a developer using the NextJS Example, I want the documentation to be clear, comprehensive, and easy to follow, so that I can effectively use and modify the example to suit my needs.

Proposed Objective

Technical User Experience

Proposed Priority

Priority 3 - Average

Acceptance Criteria

1. Update README:
   • Provide a clear and concise introduction explaining how the example works with NextJS and DotCMS.
   • Clearly state any dependencies or prerequisites needed to use the example.
   • Ensure the README covers the GraphQL integration.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

Here is a list of the most important JSDoc annotations:

• @param - Documents the parameters of a function.
• @returns or @return - Documents the return value of a function.
• @typedef - Defines custom types.
• @property - Documents properties of an object.
• @example - Provides example usage of the function or method.
• @throws - Documents the exceptions that a function might throw.
• @deprecated - Marks a function or method as deprecated.
• @see - Provides a reference to related information.
• @async - Indicates that a function is asynchronous.
• @callback - Documents a callback function.

Quality Assurance Notes & Workarounds

• Ensure that the documentation is consistent and follows a uniform style.
• Include practical examples and use cases in the README to help developers understand how the example works.
• Review and test the documentation to ensure accuracy and completeness.

Sub-Tasks & Estimates

No response

[fmontes]

I updated, so we do it for all the examples.