It seems very slow to load but could be my fault. I am in Italy.
Sorry for the slow site. It's behind my adsl service (with very low bandwidth, so be patient :/). Perhaps I can apply the changes to a dev app in pythonanywhere so you can check the code also.
Looks
good, though do you plan to keep the name "Tool" and make a distinction
between that and a "Slice" (i.e., in the search box)?
For the app database side a Tool is a content type the same as with Article, Question, etc., as Anthony noted. I wanted to highlight the tool search capability for the users. Anyway, it's just a matter of removing that dropbox item and users can search for projects inside the slice search page.
If the new type is intended for posting any code repository (e.g., application, framework, plugin, module, utility, etc.), a better label might be something with a broader meaning, such as "Code" or "Package".
Yes, I also think that tool is not the better name. I like packages. If everybody agrees i'll apply that name.
The search action is still very simple. I want to add support for a subset of possible query filters: package type, date boundaries, license and qualifications (aprooved, ...)
What about project activity? The show project action could dinamically retrieve project changes/commits making requests to pypi/mercurial apis, but unless the app collects project data periodically (for example using the scheduler) it cannot store those changes in the db and filter packages using the collected data. Enybody interested in adding that feature?