collective / collective/rapido.core
hard to customise listings
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
# User problem
If there is a listing of items such as search results, summary view, etc it's not easy to make simple change to this, such as adding a publish date to each content item listed. The current way would be create a diazo rule to replace the whole listing and rebuild it in rapido. This could be tricky if the search is coming out of collection for example.
# Options
## context arguments
Somehow make it easy to pass in an id or actual object into a rapido block so it can get data out of the and display it in the desired place in the listing.
e.g.
```
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points and presents several competing designs for customisable listings. Start by tracing the existing Rapido block and Mosaic tile/listing mechanisms described in the issue, then establish a chosen approach and acceptance criteria for per-item customisation, including how listing brains and object access are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100