Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Feature Request) Collaboration Features (comments on findings; tracked changes) #425

Open
includesec-nick opened this issue Apr 30, 2024 · 3 comments

Comments

@includesec-nick
Copy link

Our internal QA workflow involves a combination of inline editing and comments by our Technical Writers, which are then reviewed by consultants. It would be awesome if Ghostwriter supported comment threads and tracked changes/version history on individual findings so that consultants and reviewers can easily iterate on findings throughout the QA process.

If you have any thoughts on how this could be implemented please let me know--we might be able to help!

@includesec-nick includesec-nick changed the title Collaboration Features (comments on findings; tracked changes) (Feature Request) Collaboration Features (comments on findings; tracked changes) Apr 30, 2024
@domwhewell-sage
Copy link

+1 for this feature.
We're finding ourselves generating docx's QA'ing those then making changes in ghostwriter which can get complex. It would really help if there was a system for in-line comments!

@domwhewell-sage
Copy link

Hmm looks like the editor in use currently "tinymce" has a comments plugin tinycomments this looks to be very nifty as it adds a <span> containing an ID that can map to a record in the database containing the comment. However it looks to be a premium plugin

@domwhewell-sage
Copy link

Looking around abit more and I found LANCE a plugin to add inline comments to the editor. It works similar to the other one wrapping the selected text in an <annotation> tag and storing the comments in a dictionary in the annotations-data attribute. It seemed promising as I was able to add the plugin into my configuration but the editor was striping the <annotation> tag upon save.
There is also FLITE to track changes in your editor field.

The implimentation seems abit difficult to me as there is not much documentation out there and what does exist is rather vague
@chrismaddalena I dont know if you could help at all? A way these features could be implemented using these plugins or another way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants