Coda, group sites?
It would be great to have the ability to groups sites in Coda.
It's pretty hard to have a good overlook when i have 50+ sites in Coda...
It's pretty hard to have a good overlook when i have 50+ sites in Coda...
31
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?It's a great suggestion, and one we hear a lot. We're still thinkin' about the best way to tackle it for the future. Thanks for the suggestion!
-
Just split it in bars:
[========uncollapsed heading bar=========]
[ site1 ] [ site2 ] [ site3 ]
[ site4 ] [ site5 ] [ site6 ]
[=========collapsed heading bar==========]
[=========collapsed heading bar==========] -
denisnovikov: He said it would be for the future, so it's not a design problem. The problem like i understand it would be how to manipulate the Sites in question so that it would be easy and not so much junk code in Coda. -
TXC: then I lost in translation :D -
Inappropriate?I'd really like to see site configs implemented as bundles that live in an (optionally-configurable) folder. Most IDEs let you save "projects" somewhere, which you open up when you need—personally, I tend to store my project files in a folder on my iDisk (I have projects configured to use the same paths whether at home or work, so this works wonderfully).
In that context, the most obvious way of grouping sites (by context, location, whatever) would be through folders. However, I have no idea (a) whether storing sites in this way is useful enough for Panic to consider, and (b) how those folders (if supported) would be presented UI-wise anyway.
Huh, that was possibly the least helpful comment I've posted to GS ever :\
I’m undecided
1 person thinks
this is one of the best points
-
Inappropriate?I often have sites with subdomains for various parts. As such I tend to make a different 'Site' for each as the server path will have changed. It'd be super nice to be able to group all these 'sub-Sites' to clear up screen estate a little.
As a UI suggestion, my personal preference maybe to have Groups collapsed together, expanding once clicked perhaps? The way Apple's Aperture software groups similar photos springs to mind...
My 2 cent.
P. -
Inappropriate?Or give users the option to show the sites in a standard file browser manner...I'm not actually a huge fan of the eye candy approach; like others have said here, it's unwieldy when I have lots of sites.
-
Inappropriate?Site groups would be a great feature addition, but I think this should be taken a step further.
I think that a project file/bundle should be saved to disk (ideally I would save these to my sites local directory like Espresso does) and have the Sites section in Coda display the projects of choice. That way I could keep the projects I'm working on regularly in the Sites view, and the ones I don't work on so regularly I could just open the project file.
1 person thinks
this is one of the best points
Loading Profile...



EMPLOYEE


