The problem here is that most version control systems need a folder, and we really don't want aiki files in our repo to get near custom assets.
Is custom really good? The url is: http://SOMESITE/custom rather it be something like http://SOMESITE/srv or http://SOMESITE/home to mirror linux could even make it http://SOMESITE/home/SITENAME to show we supporting idea that one aiki installation can support multiple hierarchies. Thoughts? jon On Fri, Dec 24, 2010 at 3:32 PM, Bassel Safadi <[email protected]> wrote: > I think we add /custom and keep the current structure so /assets is for our > default assets.. > btw the whole idea of having assets folder is that it's not really necessary > for aiki functionality, one can remove it and and keep aiki working without > the admin panel, if custom solution is needed. > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/694026 > > Title: > assets contains user files and core files > -- Jon Phillips http://rejon.org/ http://fabricatorz.com/ chat/skype: kidproto | irc: rejon +1.415.830.3884 (sf/global) +86.187.1003.9974 (china) +65.8330.5807 (singapore) -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/694026 Title: assets contains user files and core files Status in Aiki Framework: Confirmed Bug description: We need to decide on a file structure that is indepedent of site-specific assets like assets/extensions and other ones like assets/images which currently has default images in it. Also, there is custom javascript in the /assets/javascript folder. I think we should make a decision. Possibly, /assets is the place for default assets: /assets /apps /images /extensions /javascript /uploads Then need something like: /custom /apps /images /extensions /javascript /uploads And keep those completely empty on an installation. We should even keep these except for a README in each, and then remove /assets/uploads from the current trunk of aiki. Any other suggestions? The more I've been working with aiki, realize that its weird. The other thought is we could put something like: /assets /apps/default /images/default /extensions/default /javascript/default /uploads/default For the current default aiki assets for these folders. Thoughts? I think we should move on this sooner rather than later, noticing that several installations have a mix of core and custom assets. It just makes keeping the core VS custom distinction harder to make real...let's keep it real :) _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
