Show proposals and votes from TaskStream on a project's page
The most voted bug reports and ideas, the link to send one while the board takes them, and how many want each epic on the roadmap. The mock API serves a showcase for the catalogue so every section can be seen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
10
README.md
10
README.md
@@ -132,9 +132,13 @@ pass on the server:
|
||||
| Contact form | `POST /contact` |
|
||||
|
||||
A project page also asks TaskStream, when the project has a board there
|
||||
(`taskstream.showcase_url` in its payload): roadmap, releases, the sprint under
|
||||
way and tickets labelled `good-first-issue`. It is public, answers within four
|
||||
seconds or the page goes without those sections, and its links open the board.
|
||||
(`taskstream.showcase_url` in its payload): roadmap (with how many want each
|
||||
epic), releases, the sprint under way, tickets labelled `good-first-issue`, and
|
||||
the most voted bug reports and ideas from the public, with a link to send one
|
||||
while the board takes them. It is public, answers within four seconds or the
|
||||
page goes without those sections, and its links open the board (voting needs
|
||||
signing in there). `npm run mock` serves a showcase for the «Catálogo abierto»
|
||||
project, so every section can be seen without TaskStream.
|
||||
|
||||
`landing/openapi.yaml` is the specification the app was written against, and
|
||||
`landing/src/app/core/api.types.ts` is the API's own generated type file. Both
|
||||
|
||||
Reference in New Issue
Block a user