Looks like there is issue with docs:build command, It generate the documentation only if component is exported as default. Otherwise pipeline get failed. How do we resolve this ?

@sunil25393 can you give me an example of this? Because I just tested with usePostScheduleLabel which is not the default export and seems to work for me..

Sure @ntsekouras , here is my draft PR #60932

I'm just dropping an update here. I'm organizing an internal WP Engine Contributor Day on Thursday, May 16, 2024, and I plan on utilizing this issue to provide some folks with some quick wins and empower them to feel successful in their contribution efforts. Hopefully, we'll have all the items wrapped up that day. Thanks!

@ntsekouras I'm happy to do a follow-up pull request to take a pass at refining the consistency of some of these docs. Two items I'm currently seeing:

Different use of @return (random sampling)

• @return {JSX.Element} The rendered dropdown content.
• @return {Component} The component to be rendered.
• @return {JSX.Element|null} The rendered button component.
• @return {Component|null} The component to be rendered. Return null if the post type doesn't...
• @return {Element} The component to be rendered.

Description phrasing (random sampling)

• Renders a control for enabling or disabling pingbacks and trackbacks in a WordPress post.
• Renders the PostSlug component. It provide a control for editing the post slug.
• This component renders a navigation bar at the top of the editor. It displays the title of the current...
• Component handles the keyboard shortcuts for the editor.

@colorful-tones I had the same thinking; I was waiting for the remaining documents to be completed so that we could refine them all at once.

I'm happy to do a follow-up pull request to take a pass at refining the consistency of some of these docs. Two items I'm currently seeing:

That sounds good, thank you!

I was waiting for the remaining documents to be completed so that we could refine them all at once.

Yeah, it would be great to do them all at once, since the changes would be minimal.

@ntsekouras it seems that ServerSideRender is deprecated and should not be on the list, correct? I just wanted to verify. Thanks.

@ntsekouras it seems that ServerSideRender is deprecated and should not be on the list, correct? I just wanted to verify

You're right. I'll remove it.

I would go with these options for documentation uniformity

for return of component,
@return {Component|null} The component to be rendered or null if the post type doesn't

for description of component,
Renders a control for enabling or disabling pingbacks and trackbacks in a WordPress post.
Following simple structure of Render { render what? } for { whats the use } makes it easy to understand the purpose of component.

@colorful-tones @ntsekouras Let me know your thoughts.

@akasunil I think your suggestions make sense.

I recommend we finalize the initial work in this issue, close it and then open a follow-up issue with notes/reference back to this one and submit a separate pull request towards the newer issue. Reasoning: clean break for work and intent, but I'm open to other ideas. Perhaps that is more work. 🤷

@ntsekouras I'm not clear as to whether we need to add docs for transformStyles , as it is in packages/editor/src/index.js ? 🤔

https://github.com/WordPress/gutenberg/blob/trunk/packages/editor/src/index.js#L16

recommend we finalize the initial work in this issue, close it and then open a follow-up issue with notes/reference back to this one and submit a separate pull request towards the newer issue.

Sounds good. And we will mention this issue in a new issue for future reference.

Thank you all for the awesome work you did here! 🚀 Additional kudos to @colorful-tones for also organising a contributors day event!! transformStyles is just for back compat, so we can skip it and close this issue.

@colorful-tones I have created issue #62744 as we discussed