-
Notifications
You must be signed in to change notification settings - Fork 0
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
Collaborate on text editing / commenting #14
Comments
I'm good with that option, used before 👍 |
I do like that it uses the github login, and accepts markdown, and looks to have some level of integration with vscode. Never used it, but looks like a better fir than g docs |
Hey wait, we could also use github itself for editing / commenting on markdown files, no? 🤔 The script would then not be in the body of an issue, but it could be a pull request with an actual md file. Then again, not sure if editing/commenting on PRs is really easier. |
I mean, comments on PRs work pretty well and can be marked as resolved, so it could work. |
Good with me also |
Can PRs be added to project boards? If not we can just link the PR to the existing card but was curious if you'd tried |
Added published video scripts to repo as markdown. Added upcoming video scripts as open pull requests. Did not update instructions in main README.md file. |
We started a discussion there: #13 (comment)
But it should warrant a discussion of its own and not meddle with producing that very video.
So I found other tools like https://hackmd.io/ for example.
They support markdown and git, login via github, so to me feels more inclined to Mudlet infrastructure than google docs.
What do you think? Got other tools or experience to share?
The text was updated successfully, but these errors were encountered: