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

editing interface #142

Open
autonome opened this issue Jul 13, 2022 · 5 comments
Open

editing interface #142

autonome opened this issue Jul 13, 2022 · 5 comments

Comments

@autonome
Copy link
Collaborator

non-technical contributors get stuck fast on git-flow.

started writing up some reqs and directions for an "admin ui"

min viable ux:

  • github login
  • no live updating (until branching/testing model exists)
  • pulls /events/*.toml into a view/editing ui
  • and submits PRs w/ proposed changes

https://hackmd.io/cpf1lPBTRQOsPu-_hkRTzw

@SgtPooki
Copy link
Member

It sounds like a web interface for editing and not necessarily admin UI.

Am I correct in thinking that the ideal workflow would allow any github account having users to become editors? Ideally, editors wouldn't need to have permissions modified prior to signing in and proposing changes; because we're just talking about filing PRs.

@SgtPooki
Copy link
Member

For the "Publish to Fleek" item on the hackmd.io doc, I think sticking to PR workflows entirely would be ideal for maintenance.

But for user contributions/edits, I think an "edit event" with github auth to submit PRs automatically would be a significant improvement.

@autonome autonome changed the title admin interface editing interface Jul 13, 2022
@autonome
Copy link
Collaborator Author

Yeah, editing is better description than admin, updated title

@autonome
Copy link
Collaborator Author

Am I correct in thinking that the ideal workflow would allow any github account having users to become editors

  • anyone can suggest a change
  • ppl w/ permissions maybe should be able to commit directly in some cases

editing front-end and permissions should be decoupled so that events using the devent system can plug their own system in.

however, using github repo perms seemed like a fast/easy first approach.

@SgtPooki
Copy link
Member

I can get down with that. I'll start throwing something together as soon as I get a chance

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

When branches are created from issues, their pull requests are automatically linked.

2 participants