This is the Feedback testing story, which really is looking at creating two bits of this, the Twine framework to be able to collect feedback, and the backend to handle that feedback. I see two goals for this feedback. One is to have players collaborate with, "I'd like to see this part of this story developed," including *maybe* sending parts of a passage (look at writing.com where they have this kind of option). The other major one of, "I think this is a bug here." Ie. "I have followed along this way, and I experienced unexpected behaviour..." The *main* difference would be the "issue label" that might get added for the report of feedback.

Go to file

Jigme Datse Yli-Rasku 5070497669 Compiled Code html file... This is a compiled html file.		2024-10-11 18:59:38 -07:00
journal	Journal for daily journal enteries.	2024-10-11 18:58:48 -07:00
output	Compiled Code html file...	2024-10-11 18:59:38 -07:00
LICENSE	Initial commit	2024-09-12 19:52:16 -07:00
README.md	Initial commit	2024-09-12 19:52:16 -07:00

README.md

FeedbackStory

This is the Feedback testing story, which really is looking at creating two bits of this, the Twine framework to be able to collect feedback, and the backend to handle that feedback.

I see two goals for this feedback. One is to have players collaborate with, "I'd like to see this part of this story developed," including maybe sending parts of a passage (look at writing.com where they have this kind of option).

The other major one of, "I think this is a bug here." Ie. "I have followed along this way, and I experienced unexpected behaviour..."

The main difference would be the "issue label" that might get added for the report of feedback.