Issue #3791 resolved

A homepage for multiple projects

Uri Cohen
created an issue

I'm working on a several projects with a common theme where the main branch and release usually done by the user which started the project.

This has the effect that each of the projects usually publish a different URL for its users as the 'main site', with username as part of the URL.

I would like to create a minisite around the common theme (think, which will contain some content I'll be able to control and links to the documentation, download pages and issue trackers of the actual projects. A sample site which is my inspiration is (but there they have a dedicated server which I would like to avoid).

This has many advantages: Projects benefit from the good reputation of other projects, exposing the users of one projects to all others Single URL = more search engine visibility, higher page rank * A URL without a username is more respectful, easier to remember and does not depend on change of personnel which is common in open-source projects

No need to unify the issue tracking or release mechanism, as development may still be done in a distributed manner by many different users.

Note that having some mechanisms would cause me to unify all projects on bitbucket, while currently some of them are on github. :)

Comments (4)

  1. Nicolas Venegas


    It sounds like our static hosting feature would be perfect for this:

    Say your username is neuroscience, simply create a public repository named in that account, and you'll be able to serve static files from there (e.g., index.html).

    Let me know if that works for you.



  2. Uri Cohen reporter

    (Reply via

    Thank you, it would do the trick!! I would recommend allowing also for project pages, like, to avoid the hassle of creating a username which match my requirements. Thanks again, Uri Cohen

    On Thu, Mar 22, 2012 at 11:09 PM, Nicolas Venegas <> wrote:

  3. Nicolas Venegas

    Hi Uri

    We are likely to stick with restricting these to match the name of a repository: it is simpler in the sense that we don't need to introduce the concept of a project that groups repositories.



  4. Uri Cohen reporter

    (Reply via

    Hello Nicolas, I'm not sure I understood correctly- currently you restrict static hosting names to usernames, not repository names. I tried to create a static site for one of my repositories (pyneuron) and it doesn't work: Do I miss anything? Thanks, Uri Cohen

    On Sat, Mar 24, 2012 at 5:09 AM, Nicolas Venegas <


  5. Log in to comment