Codeinwp / Codeinwp/otter-blocks
Woo Booster in Custom Layouts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
Thanks for all the help so far Bogdan, we can keep the discussion at the [build](https://github.com/Codeinwp/neve-pro-addon/pull/2443#issuecomment-1483195159).
@HardeepAsrani Whenever you can, it would be great if we can address the issue of Otter's Woo Builder blocks not appearing in the custom layouts context (as commented above)
Even if we use some dummy data in the editor for now. Let me know if you need help or clarifications.
Originally posted by @JohnPixle in https://github.com/Codeinwp/neve-pro-addon/issues/2203#issuecomment-1484834789
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 reading the linked build discussion and issue #2203, then trace how Otter's Woo Builder blocks are handled in the custom layouts context. Done means the blocks appear there, with suitable editor data if required; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100