I guess this would be a huge pain while tweaking, for example: "Change this header, ok, let's see what it looks like - Now we gotta get Alan to help us to apply the template. Ok, now we see what it looks like, but, oh darn, we gotta change this nav bar. Ok, change it, have Alan apply it, see what it looks like, "
ad nauseum. if my above assumptions are correct, that would take _forever_ to get this done ;) Isn't there a more efficient way? On Mon, Aug 18, 2008 at 1:16 PM, Allan Ditzel <[EMAIL PROTECTED]>wrote: > For me, the part where I have to send a third party (for example, you) the > template file so that we can changeh LnF is really limiting. > > On Mon, Aug 18, 2008 at 1:05 PM, Alan D. Cabrera <[EMAIL PROTECTED] > >wrote: > > > > > On Aug 18, 2008, at 9:45 AM, Les Hazlewood wrote: > > > > I think my current preference is the manually maintained one. I rarely > >> update the JSecurity website today, and do so only for the occasional > >> announcement and product release - something that would still be easy to > >> do > >> in a manually maintained site environment (e.g. checked in to SVN). For > >> some reason, I just don't feel CWIKI is flexible or configuable enough > for > >> our needs, and the "no linking to the wiki" rule really rubs me the > wrong > >> way. I don't like that anyone visiting our website would have to know > to > >> adhere to weird linking rules - its just not in the spirit of the web > and > >> could be confusing for some people. > >> > > > > > > I have no preferences but, I have a few questions. What part of CWIKI is > > not configurable enough for our needs? What is this "no linking to the > wiki" > > rule? > > > > > > Regards, > > Alan > > > > >
