Use with GitHub API
vwochnik opened this issue · 9 comments
Description:
This is a very interesting plugin but I as a developer would never use locally because I have my own editor. I would rather deploy it somewhere for non-tech-savvy users to make simple changes to their site. Like prose.io, but the interface of this plugin is mch more suited to jekyll.
I have looked at the recommended siteleaf and other options but I like the more simpler approach of this interface.
I'm glad that you like the interface ❤️ I really want the same thing as you do. The future plan is to have Jekyll Admin on the cloud. But until then there are lots of things to do like securing the interface, fixing current major bugs, implementing necessary features and so on. Unfortunately we are going kind of slow in that way and I'm not sure if this will be available in the near future.
Well, why in the cloud? GitHub API provides everything you need to manage the files for Jekyll. The interface needs slight adaptation to login to GitHub and then the static HTML/JS/CSS for this Admin-Panel can simply be added to your repository.
The interface needs slight adaptation to login to GitHub
Will you be able to send in a PR?
@benbalter What do you think about this? Is it doable?
It's definitely doable! Not sure how much would have to be written to e.g., list files via the API, or if it makes more sense to authenticate, get the token, and clone locally.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
Multi-login with OAuth is a pretty nice feature.
Facebook, Twitter, and Google
How about roles and permissions? Is possible to implement this? If yes, how Jekyll Admin behavior with that?
And about how things will work on multi-user scenarios, the Admin could have a button that sends all new things and edits to a Pull Request to project's repo.
Ideally we should be planning to accommodate git in general, not specifically GitHub.
Since the repository is remote, we will have to stay in sync with the remote repository by pulling often to update the local copy.
User roles and permissions are the only thing holding me back from making use of jekyll-admin with integration to a personal created web stack of mine for client base awesome sauce.
The other options like NetlifyCMS, Siteleaf and Forestry are other premium commercial options with fair pricing. How difficult would it be to integrate roles and permissions into jekyll-admin to be included as an API service being run on AWS or other similar hosting services? I am imagining jekyll-admin how Staticman for comments works when running our own instance.
We will plug-in a link to login back-end to create posts, manage settings and other privileged things of the liking. The only three privileged roles could be admin, developer and writer. They login via secure authorization protocol they have been invited to.