Documenting Action portlets
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 106
- Forks
- 190
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
Hello,
The Action Portlets don't act as I would expect. I started discussions in 2 locations and it was suggested i post it here. I would be willing to help document the Action Portlets if I could get some help understanding them. Here is were I started this discussion:
https://github.com/plone/plone.app.portlets/issues/63#issuecomment-225511418
https://community.plone.org/t/plone-5-action-portlets-not-working-as-i-would-expect/1274
I'm not on the documentation team; however, I could submit text to someone who is and get it published.
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 plone.app.portlets discussion and Plone community thread to understand the expected behavior of Action Portlets. Document the clarified behavior in the Plone documentation, with completion defined by maintainers confirming that the explanation is accurate and publishable.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100