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

Sort Table of Contents #392

Open
zoffixznet opened this issue Feb 11, 2016 · 15 comments
Open

Sort Table of Contents #392

zoffixznet opened this issue Feb 11, 2016 · 15 comments
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority

Comments

@zoffixznet
Copy link
Contributor

As reported in Raku/user-experience#10, the method names in the table of contents are in no coherent order, which makes it hard to spot the one you want to read about. I'd suggest them to be sorted alphabetically.

untitled

@AlexDaniel
Copy link
Member

Are you saying that 「combinations」 and 「permutations」 should be far away from each other? I don't think so. In fact, I always loved how it was more or less sorted in “what I need is usually on top” order.

@tbrowder
Copy link
Member

Then maybe there ought to be clear category subparts under which such things could be grouped. Closing this without more discussion isn't helpful IMHO.

@Skarsnik
Copy link
Contributor

Yep. For me an example of a good documentation is Qt. it's alphabetical
order but methods that do thing related thing are mentioned in each other.

2016-02-11 13:49 GMT+01:00 Tom Browder notifications@github.com:

Then maybe there ought to be clear category subparts under which such
things could be grouped. Closing this without more discussion isn't helpful
IMHO.


Reply to this email directly or view it on GitHub
#392 (comment).

Sylvain "Skarsnik" Colinet

Victory was near but the power of the ring couldn't be undone

@zoffixznet zoffixznet reopened this Feb 11, 2016
@zoffixznet
Copy link
Contributor Author

@tbrowder would you have any examples of how such a category layout would look like?

In the screenshot above, I see keys, values, and kv as one group, pairs is somewhat similar to kv, but doesn't really fit into that group entirely. To me classify more tightly fits into a group with sort, but you can equally argue the grep group is appropriate too.

There is some intelligence with the current grouping; trying to break it up into more refined subcategories would result in a lot of bikeshed IMO, especially since many methods are inherited from other classes.

Also, does anyone know how the current sorting is made up? It is all just hand-ordered?

@tbrowder
Copy link
Member

On Thursday, February 11, 2016, Skarsnik notifications@github.com wrote:

Yep. For me an example of a good documentation is Qt. it's alphabetical
order but methods that do thing related thing are mentioned in each other.

Sounds like a good solution to me (maybe a bit of pain for doc writers, but
only for a brief while).

-Tom

@AlexDaniel
Copy link
Member

Yeah, closing this is not helpful. If somebody feels uncomfortable with the current layout then we should do something.

There are other interesting ways to tackle this. For example, we can add a javascript _A-Z_ button that will sort the list alphabetically.

@coke
Copy link
Collaborator

coke commented Jun 10, 2016

Managing a category layout is more work that we're not going to be doing yet. For now, the best solution is a case insensitive sort, IMO. The existing order has no obvious meaning, let's at least provide something that lets people find what they're looking for more easily.

@coke
Copy link
Collaborator

coke commented Dec 8, 2016

If anyone disagrees with my Jun 10th comment, please ping this ticket in the next week or so; otherwise we'll go with that for now.

@coke coke self-assigned this Dec 8, 2016
@JJ
Copy link
Contributor

JJ commented Jan 27, 2018

I'm pinging this ticket now. What happened to it? Do we have a proper order? If that's the case and there are problems somewhere else like having categories, I suggest to open a separate discussion for that.

@JJ
Copy link
Contributor

JJ commented Feb 10, 2018

I'm not so sure about this. Right now they are in the same order as in the original document, which I guess has some merit to it, because it's how it was intended by its author(s). You can still search within the page using Ctrl-F and the website search. As @AlexDaniel has commented, we would need a major refactoring of htmlify.p6 to add JS code that sorts this. I don't see how that effort would have a good return on investment by offering an arrangement of contents that would be arguably better.
There's a point in the rearrangement of documentation, however... But once again, it escapes the boundaries of this particular issue.

@coke
Copy link
Collaborator

coke commented Feb 10, 2018

This work was never done. This work still needs to be done.

@tbrowder
Copy link
Member

tbrowder commented Feb 10, 2018 via email

@JJ
Copy link
Contributor

JJ commented Feb 10, 2018

If you feel it helps, do it by all means...

@tbrowder
Copy link
Member

oops, that was for files, not parts inside a file!

@JJ
Copy link
Contributor

JJ commented Apr 18, 2018

Since tables are now sortable, maybe we could throw this inside a table and just make it sortable by default?

@JJ JJ added wishlist "nice to have" issues; might require a lot of work or a big change or be low priority and removed JJ TPF Grant labels May 14, 2018
@coke coke removed their assignment Jul 29, 2018
@coke coke removed the build label Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority
Projects
None yet
Development

No branches or pull requests

6 participants