Hi Hilton, (Copying in the developers list as well, as I think part of the work of managing such a theme repository would fall to the developers.)
As of yet, an official Theme repository hasn't yet been created. Though, not out of lack of interest. But, rather, we haven't yet figured out a good place to share all these themes. That being said, there have been some past brainstorms on whether we could use GitHub to more easily share themes between institutions. If we went the GitHub route, each institution could essentially share & manage their theme(s) via their own GitHub account. Then, we'd need to find a way to make these themes easily "findable" to other institutions. Another even more simplistic solution is to just start up a DSpace Wiki page, and allow anyone to list their theme(s) there, and provide link(s) for where it can be downloaded/installed. This is something that could be done almost immediately (by anyone). == Technical brainstorm (how GitHub could potentially help) == One past attempt at a Theme Repository (from a few years back) was the following GitHub project: https://github.com/DSpace/xmlui-webapp Essentially, the idea here was that institutions could "fork" this GitHub project and share their own themes via that fork. Those forks could then be found via GitHub via the project "network": https://github.com/DSpace/xmlui-webapp/network/members The issues around this method are that we end up with two completely separate copies of the XMLUI Webapp that need to be maintained/synced at all times: 1) The official XMLUI webapp (in the main GitHub project): https://github.com/DSpace/DSpace/tree/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp 2) This separate project: https://github.com/DSpace/xmlui-webapp This unfortunately adds an extra burden on the Committers to maintain two copies of the same code. So, this either means we need to find a more automated way to maintain this syncing, or we perhaps we need to simplify so that we just have a "Theme Template" GitHub project which any institution can fork & use to create/share their own Theme(s). This "Theme Template" project may just literally be the basic "/themes/template" code: https://github.com/DSpace/DSpace/tree/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/themes/template Even with this approach, we still may want to start up a wiki page to help people locate themes. We also wouldn't want to force everyone to use GitHub (as we want to avoid barriers to sharing themes, if we can). But, at the same time we'd likely want to encourage usage of GitHub, as it will help others contribute code back to your theme and perhaps encourage more cross-collaboration between institutions on specific themes. This is all just a brainstorm & meant to get more discussion going. I'm not going to claim that this is the answer or right answer to your question. :) - Tim On 5/31/2012 8:34 AM, Hilton Gibson wrote: > Hi All > > There was talk of creating a Manakin Theme Repository/Store on one of > the DSpace mailing lists. > Has this happened ? > I am willing to upload/donate, without prejudice, our theme. > See: http://scholar.sun.ac.za > > Cheers > > hg > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
