Codeinwp / Codeinwp/otter-blocks
The “subscribe form” block is wildly misleading.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
What problem does this address?
The “subscribe form” block is wildly misleading. The obvious expectation is that something called a “Subscribe Form” will actually subscribe someone to the blog--in other words, it will create a new user of the WP site, with the role of “subscriber.”
What is your proposed solution?
Rename this, if it's useful to some; and create an attractive block that actually subscribes someone.
Thanks,
Lance
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing “subscribe form” block and how it is currently presented. Clarify whether the work requires renaming the existing block, creating a new block that creates a WordPress subscriber, or both; done should mean the block’s name and behavior match the agreed subscription outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wordpress
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100