Thanks Patrick, that's great. There's a couple of links @LoveQuicksilver to Etienne's QS ß58 download page, but that's it. I won't link to anywhere else for now.
How does one go about editing/reviewing the QSApp.com homepage? I have a tiny bit of knowledge in several areas, but I could use a couple of pointers. For anyone reading: I'm going to post a bunch of quick tips for QS over the coming weeks, feel free to add some, or comment on the tips posted. On Dec 26, 7:09 pm, Patrick Robertson <[email protected]> wrote: > Cool! Feel free to direct users to anywhere on the QSApp.com site. I'd stray > away from directing people to anywhere on github (especially Etienne's > repository for the moment) since we're moving things about there. > > Other than that, keep tweeting I say! > If you would like to (or know of anybody that would like to) make a better > homepage for QSApp.com then feel free to get onto it, so there's a bit more > for people to see and we only need to give 1 link in the future :) > > On 26 December 2010 18:16, philgroups <[email protected]> wrote: > > > > > Hi Patrick, > > > I created a twitter account @LoveQuicksilver, and I'm directing > > readers to qsapp.com and the plugin repository. > > > Can I link to the individual plugin downloads directly, or should I > > only link to the main site? > > > On Nov 12, 8:17 am, Patrick <[email protected]> wrote: > > > So, after much debate and pondering I've finally gone ahead and > > boughthttp://qsapp.com > > > > My idea is to try and make a 'new' QS site that's going to have > > > everything everyone needs in one place. > > > > My thoughts at the moment are: > > > > 1. Expand on the plugins repo (http://qsapp.com/plugins) to add > > > tooltips with the plugin descriptions, and a way of outputting a list > > > to QS so it can update independently of the blacktree.com servers > > > > 2. Set up a wiki (http://qsapp.com/wiki) and add all the info we > > > have on the 'pages' in this group: > > > FAQs, applescripts, etc. > > > > 3. Make it clear which versions are best for which OS and make it > > > easier for people to pick and chose > > > > 4. Make a nice Dev page so interested developers can easily get > > > started on helping out with QS > > > > 5. Maybe a support forum - although I think everyone said they were > > > fine with these groups. > > > > 6. Anything else anyone else can think of, seeing as we're a > > > community :) > > > > If anybody wants to help out with getting the site set up then let me > > > know! > > > This is your chance if you've always wanted to help QS along but never > > > had the Cocoa programming skills. > > > > Let's go!
