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

Redesign ideas #83

Open
ato opened this issue Aug 18, 2012 · 7 comments

Comments

Projects
None yet
5 participants
@ato
Copy link
Collaborator

commented Aug 18, 2012

My interface and visual design skills aren't the greatest (ever noticed how the reflection/highlight on the Clojars logo is completely implausible?) Opening this issue as a thread for design improvements.

@gf3 suggested we could adapt from a prototype he did for NPM that didn't end up getting used:

https://dl.dropbox.com/u/2176065/npm/index.html
http://dribbble.com/shots/367871-NPM-Mockup

Some random thoughts/ideas:

  • what would we display in the search results on the left when you're not searching? would it be like browsing lexigraphically nearby items? (that seems like it would work very well with all the lein-* projects).
  • where would the login/profile/dashboard links go? maybe a menu button in the top right like Google's services currently use?
  • could we make the Clojars home page more useful?
  • maybe we should merge the Lein/Maven copy-paste coordinates boxes into one tabbed box and have a cookie remember what your favourite tool is by what tab you clicked last?

Thoughts?

@ato

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 18, 2012

Should we make groups take on an organizational/navigation element, not just permissions/namespacing? Or would that be complecting them? We do already have group pages but they're not all that useful or very well linked to:
https://clojars.org/groups/ring
https://clojars.org/groups/overtone

Similarly is there something more interesting we can do with user pages:
https://clojars.org/users/rayne

@gf3

This comment has been minimized.

Copy link
Collaborator

commented Aug 18, 2012

I'm in the process of iterating on the design to adapt it to Clojars.

Speaking of the homepage, I think something a little more Rubygems-like would be nice.

I like your idea about a toggle switch between Maven/Lein. Reminds me of the toggle on the Compass site between SCSS/SASS/CSS → http://compass-style.org/examples/compass/css3/background-clip/

User pages would do well with a bit of Gravatar action and perhaps some personal links.

@wiseman

This comment has been minimized.

Copy link
Contributor

commented Nov 7, 2013

Things I like about npmjs.org that you might consider for clojars.org:

  • User pages show a short description of each user's projects.
  • User pages show full name, email address, github url, twitter url, IRC handle, etc.
  • The front page shows some interesting stats and signs of activity like "recently updated", "most depended on", "most starred" sections.
  • The front page has links to instructions on how to get packages from the repository and how to publish packages to the repository.
  • Small user icons/images are shown in many places.
  • Project pages include long descriptions. (It'd be nice if clojars even linked to a description.)
  • Project pages show counts of how often the package has been installed in the past day/week/month.

If you find these ideas attractive and would accept pull requests for them, I'd work on them.

(These are more general UI issues than just the visual design.)

@technomancy

This comment has been minimized.

Copy link
Collaborator

commented Nov 8, 2013

Mostly in favour of these, with a few exceptions.

I'm not too keen on the idea of expanding user profiles to include github, twitter, and IRC, but having a field for a single URL would be nice.

Long descriptions are probably not in the cards since we don't control the pom format read during deployment.

We do already have instructions for getting packages from the repo and a link to a tutorial that covers how to publish.

I like the idea of more fine-grained download stats especially. Adapting the visual design @gf3 previewed would be fantastic, but I understand that's probably a lot more work. =)

@gf3

This comment has been minimized.

Copy link
Collaborator

commented Nov 8, 2013

@technomancy Is it impossible to peek into the jars for a top-level README.md or something similar? Or perhaps parse github repo information from project.clj and then read it from there?

@technomancy

This comment has been minimized.

Copy link
Collaborator

commented Nov 9, 2013

@gf3 Sort of... Leiningen has started including readmes in jars a few months ago. I'd rather not go out to third-party services for this. It's important that the repository be the primary source of truth and that if we store data we derive from it, we can go back and retroactively to fix bugs.

Not everyone likes to use markdown (I certainly don't think it's a good format, but I use it anyway) for their readmes, but it's definitely got the majority. You could probably go in and get the first paragraph from most recently-published artifacts, but it remains to be seen whether you'd get better results than the description in the pom. For instance, Leiningen and Slamhound both have quotations from books as the first paragraph. You'd also need to strip out the markdown formatting; rendering to HTML might not be safe. (not sure about this; perhaps it could be done safely.) But you could give it a shot.

@spacegangster

This comment has been minimized.

Copy link

commented Aug 6, 2014

A README.md on the top level would be absolutely phenomenal!
It is the best thing about npmjs.org or cpan, because you can immediately see usage examples, code style and take a better decision.
There are already a couple of markdown parsers written in Clojure, and at least one allows custom sanity functions.
I don't understand if it is fully-readable from the jars tough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.