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

Edit Content and push to Git Repo #777

Closed
tuaris opened this issue Mar 30, 2018 · 1 comment
Closed

Edit Content and push to Git Repo #777

tuaris opened this issue Mar 30, 2018 · 1 comment

Comments

@tuaris
Copy link

tuaris commented Mar 30, 2018

Desired Feature:

Dependent on #776. This feature describes how Bookstack can be used as an editor for Markdown files stored in a remote Git repository.

Expected Behavior

Assuming a Book has been created using feature #776

The editor mode should (ideally) be Markdown, but feature #458 could also apply here. With Markdown Bookstack can define it's own content/file/directory structure on how the files should be organized. Something compatible to Read The Docs or Gitbook.

Creating a new page and saving it will create the file on local storage, perform a git add . and then a git commit using the current user's email address and name, then finally a git push. Editing an existing document follows a similar process. Chapters would correspond to sub directories.

To handle cases when more than one user edits a page in a given moment. I think Bookstack already solves this problem with the "Draft" feature. This should prevent conflicts.

@ssddanbrown
Copy link
Member

Thanks for writing this up and requesting this but since this issue relies on a non-implemented feature I'm going to close this in the interest of keeping issues actionable and focused. This can always be re-opened if #776 ever becomes a feature.

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

No branches or pull requests

2 participants