SX: Improving the delightful editing process

Social affiliations 💃🕺 Delightful commons
, ,
#1

However, I think it’s about experience design. Current steps to edit delightful linked data

  1. Click on Source Repository
  2. Fork the repository (assuming you already have a codeberg account)
  3. Click on README.md
  4. Click on edit
  5. make changes
  6. Click on “code”
  7. Click on the “new pull request” button
  8. Click on "new pull request"

This is HARD!

It would be nice if one could reduce this to the stuff in bold.

I’m convinced it would not be terribly hard to reduce the number of steps needed here.

1 Like
#2

:100: Agree! Code forges generally offer dev-only UI for editing. It is not intuitive to other SX stakeholders.

It would be great. You had some good recent experience with the FEP site. I am curious if this can be done with the site still being hosted by Codeberg Pages, though I think that should be possible here.

#3

Note that, though it hasn’t been tested, the Delightful commons initiative should accept curated lists that are hosted and maintained on other forges, accessed based on their git URL. Codeberg isn’t a requirement.

#4

As long as you can have a link to the username on Codeberg (because the source code is generated from the repo hosted there) it is doable using their APIs.

While working on Anvil I had touch points to half of the relevant APIs Forgejo exposes to achieve this.

1 Like
#5

I am okay with the constraint of “Delightful lists must be hosted on Codeberg” if the editing facility makes it plain easy for anyone to suggest updates for review by list maintainers. Then “hosting elsewhere” can be a concern when the need actually arises.