Skip to content
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.

Order for cards #23

Closed
vsemozhetbyt opened this issue Dec 13, 2019 · 4 comments
Closed

Order for cards #23

vsemozhetbyt opened this issue Dec 13, 2019 · 4 comments
Assignees
Labels
backend Related to backend code enhancement New feature or request UI/UX Related to UI/UX

Comments

@vsemozhetbyt
Copy link

Previously, in GitHub README.md or in the site, the snippets were sorted alphabetically. That was handy for casual consecutive reading. Currently, we have only the site with cards in a hardly understandable order. Can the alphabetical order be restored?

@Chalarangelo
Copy link
Owner

The current order is based on a recommendation engine we recently implemented. We will look into adding alphabetical order as an alternative sorting option.

@Chalarangelo Chalarangelo transferred this issue from Chalarangelo/30-seconds-of-code Dec 17, 2019
@Chalarangelo Chalarangelo added backend Related to backend code enhancement New feature or request UI/UX Related to UI/UX labels Dec 17, 2019
@Chalarangelo Chalarangelo self-assigned this Dec 18, 2019
@Chalarangelo Chalarangelo pinned this issue Dec 18, 2019
@Chalarangelo Chalarangelo added this to the 2020 Sprint #3 milestone Dec 30, 2019
@Chalarangelo
Copy link
Owner

Chalarangelo commented Dec 30, 2019

Update for anyone interested: We will be delivering this feature sometime later in 2020 Q1, most likely around early March.

The expected behavior for this feature as well as related changes are:

  • Three order types (popular, alphabetical, expertise).
  • Default order will be popular.
  • All orders will only either ascend or descend and users can fast forward to the last page and browse backwards.
  • popular will be sorted in descending order. alphabetical and expertise will be sorted in ascending order.
  • popular will handle value equality (i.e. same ranking value) by resorting to alphabetical order to sort out conflicts.
  • alphabetical and expertise will handle value equality (i.e. same name or same expertise level) by resorting to popular order to sort out conflicts.
  • Each order type will have its own slug subprefix - /p/ for popular, /a/ for alphabetical and /e/ for expertise.
  • The /a/ subprefix for archived snippets should be converted to /v/ (vault) and existing links should be 301! redirected. Change archived snippet prefix #39

This was referenced Jan 24, 2020
@Chalarangelo
Copy link
Owner

Starting work on this a little earlier than anticipated, should be able to release before the end of the month, if everything goes according to plan. There might a possible delay if we decide to bundle it up with #64 and #69, but that is yet undecided.

This was referenced Feb 8, 2020
@Chalarangelo
Copy link
Owner

Resolved in 6a4456e.

@Chalarangelo Chalarangelo unpinned this issue Mar 6, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend Related to backend code enhancement New feature or request UI/UX Related to UI/UX
Projects
None yet
Development

No branches or pull requests

2 participants