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

Rearrange items in alphabetical order #7

Open
napsternxg opened this issue Feb 20, 2019 · 2 comments
Open

Rearrange items in alphabetical order #7

napsternxg opened this issue Feb 20, 2019 · 2 comments

Comments

@napsternxg
Copy link
Owner

@angelosalatino I have opened an issue based on our discussion in #6

Do you have suggestion on making this part automated, so that every time we add a new item to the list, we can verify the sorting? I want the curation of this list to be minimal effort so that it has high coverage of content, and contributors find it easy to contribute.

What are your thoughts? Maybe just the sorted interface on the website?

@angelosalatino
Copy link
Contributor

@napsternxg Thanks.

In general, having sorted items helps users in browsing the list. Perhaps a sorted interface on the website would do the job. For each heading, we can alphabetically sort the items in its associated list.
I am wondering if keeping the unsorted lists on the README file will produce any harm for the curators in the long run.

Otherwise, a completely manual solution could be that we sort all the current items manually and then every new contribution, needs to be located in the right place and not just in append. This will sort both curator and user side.

@napsternxg
Copy link
Owner Author

I think we can utilize this github action to auto-sort the pages before deployment.
https://github.com/JamesIves/github-pages-deploy-action

However, I think the manual suggestion is best as it will keep the README clean.

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

No branches or pull requests

2 participants