Show all packages on one page is not quite reasonable.

[mezoni]

What will happen if number of packages exceeded some reasonable value? You will need to redesign your main page to make it better. Why do not make it better already today? Why not display on the main page other information? By eg.

• Welcome
• What means this resource
• Navigation list

That is, make it as a fully functional resource for humans with voting and short reviews systems. Navigation list can contains links to:

• List of packages by categories
• List of packages by names
• List of authors

List of packages by names should be divided on the initial letters (eg. A, B, C etc)

I don'r know how to divide packages on categories but I think that there maybe some ways:

• Ask the authors of the pub package manager to add such a field in pubspec file
• Create robot which will divide them by the found well known category name keywords in the readme files (eg. parser, database, ui, dependency injection, framework, fluent, utilities, generator, authentication, authorisation etc).

[mezoni]

Create robot which will divide them by the found well known category name keywords in the readme files (eg. parser, database, ui, dependency injection, framework, fluent, utilities, generator, authentication, authorisation etc).

Clarification. Based not on the found information in readme files but on the information founs in the descriptions (latest versions). Just create a table in your database with the most valuable keywords which can be used as the tags. And fill it, of course. And your robot (analyzer) will re-assign the tags each time when you import latest version of package.

[astashov]

The goal of the project is to provide a convenient way to browse the source code of the packages in the Dart ecosystem. Like, "Go to declaration" functionality, easy file navigation (that stuff is already implemented), "Find usages" functionality, search for class/method implementation within the packages, etc (that stuff is not).

I'm not interested in reimplementing pub.dartlang's functionality, or making improved pub.dartlang, I'd better integrate with pub.dartland/Dart Docs, so they provide links to crossdart, when they need links to the source code.

I agree the whole list of the packages is pretty useless, and will probably get rid of it at all, and only show the matching packages after a user types things in the search field.

Thanks for the suggestions.

[astashov]

No, please keep it opened, I'm still going to clean up the index page.