Especially for lists with many GitHub links since the frontend is largely based on information provided by GitHub (like last commit date, repository creation date, number of stars, readme, etc.).
The main focus of the frontend:
Easier management of addition requests. (No PR conflicts, readme one click away.)
The community can vote on addition requests.
Better interface for the user. (The list is sorted by GitHub stars and repository creation date. Readme and last commit date one click away.)
Originally created by @brillout on GitHub (Sep 18, 2016).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/767
I've built a frontend for a list of react components: [devarchy.com/react-components](http://devarchy.com/react-components). (The list on Github: [github.com/brillout/awesome-react-components](https://github.com/brillout/awesome-react-components).)
It is open source ([github.com/brillout/devarchy](https://github.com/brillout/devarchy)). Maybe it could be useful for other lists as well.
Especially for lists with many GitHub links since the frontend is largely based on information provided by GitHub (like last commit date, repository creation date, number of stars, readme, etc.).
The main focus of the frontend:
- Easier management of addition requests. (No PR conflicts, readme one click away.)
- The community can vote on addition requests.
- Better interface for the user. (The list is sorted by GitHub stars and repository creation date. Readme and last commit date one click away.)
It's been tried multiple times. I think that http://awesomelists.top/ is the most feature complete one out there.
<!-- gh-comment-id:247844363 -->
@inputsh commented on GitHub (Sep 18, 2016):
It's been tried multiple times. I think that http://awesomelists.top/ is the most feature complete one out there.
I am aware of it and its corresponding ticket #427.
It's not what I wanted though. See the 3 bullet points of the OP.
<!-- gh-comment-id:247844917 -->
@brillout commented on GitHub (Sep 18, 2016):
@aleksandar-todorovic
I am aware of it and its corresponding ticket #427.
It's not what I wanted though. See the 3 bullet points of the OP.
I personally think Awesome lists should stay on GitHub. The Markdown rendering here is great and it makes it super easy to contribute.
<!-- gh-comment-id:467582420 -->
@sindresorhus commented on GitHub (Feb 26, 2019):
I personally think Awesome lists should stay on GitHub. The Markdown rendering here is great and it makes it super easy to contribute.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @brillout on GitHub (Sep 18, 2016).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/767
I've built a frontend for a list of react components: devarchy.com/react-components. (The list on Github: github.com/brillout/awesome-react-components.)
It is open source (github.com/brillout/devarchy). Maybe it could be useful for other lists as well.
Especially for lists with many GitHub links since the frontend is largely based on information provided by GitHub (like last commit date, repository creation date, number of stars, readme, etc.).
The main focus of the frontend:
@inputsh commented on GitHub (Sep 18, 2016):
It's been tried multiple times. I think that http://awesomelists.top/ is the most feature complete one out there.
@brillout commented on GitHub (Sep 18, 2016):
@aleksandar-todorovic
I am aware of it and its corresponding ticket #427.
It's not what I wanted though. See the 3 bullet points of the OP.
@sindresorhus commented on GitHub (Feb 26, 2019):
I personally think Awesome lists should stay on GitHub. The Markdown rendering here is great and it makes it super easy to contribute.