browser extension development lifecycle docs and api improvements

[IF-tiger]

Describe the problem

This project is indeed a great one, but from a long-term perspective and in terms of standardization, we should establish a complete process from the extension's build to its release to help extension developers practice more efficiently.

Describe the proposed solution

Provide more comprehensive documentation, as well as improvements to the functionality of the CRX itself and its API.

Alternatives considered

null

Importance

nice to have

[github-actions]

⚠️ Important Notice: CRXJS is seeking new maintainers.

• New issues and PRs may not receive immediate attention
• A new maintenance team must establish itself by March 31, 2025 or this repository will be archived on June 1, 2025
• Learn more about the transition

---

This is an automated message. Please do not reply to this comment.

[jacksteamdev]

I love the way you're thinking! Please consider joining the maintenance team to help with these types of improvements.

[colearendt]

If you have any thoughts on docs improvements, that is one of the big projects we want to tackle right now! Even just helping with outlines / TODO items / improved blurbs and suggestions would be quite helpful!

[Toumash]

related: https://github.com/crxjs/create-crxjs

[github-actions]

Thanks for contributing to CRXJS! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days.