Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDK: Improve Angular Example Documentation #29561

Closed
rjvelazco opened this issue Aug 13, 2024 · 4 comments
Closed

SDK: Improve Angular Example Documentation #29561

rjvelazco opened this issue Aug 13, 2024 · 4 comments

Comments

@rjvelazco
Copy link
Contributor

rjvelazco commented Aug 13, 2024

Task

As a developer using the Angular 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 Angular and DotCMS.
    • Clearly state any dependencies or prerequisites needed to use the example.

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.
@KevinDavilaDotCMS
Copy link
Contributor

This task will be resolved in the PR attached in this other ticket

@KevinDavilaDotCMS KevinDavilaDotCMS self-assigned this Sep 6, 2024
@KevinDavilaDotCMS KevinDavilaDotCMS moved this from Gardening Day Backlog to Internal QA in dotCMS - Product Planning Sep 6, 2024
@KevinDavilaDotCMS KevinDavilaDotCMS removed their assignment Sep 6, 2024
@dcolina dcolina assigned dcolina and unassigned dcolina Sep 9, 2024
@dcolina
Copy link
Contributor

dcolina commented Sep 9, 2024

Internal QA: Passed.

@dcolina dcolina closed this as completed Sep 9, 2024
@dcolina dcolina moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Sep 9, 2024
@jdcmsd
Copy link
Contributor

jdcmsd commented Sep 27, 2024

Great job on this! The text is crystal clear, and all instructions work perfectly; I've followed every step successfully.

@bryanboza
Copy link
Contributor

Fixed, approved based on the @jdcmsd comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

6 participants