dhempy
Posts: 40
|
| Posted: 06/23/2004, 12:38 PM |
|
I'm building a pretend site to evaluate CodeCharge Studio...just a tiny site with a public list of widgets, and a set of staff tools to edit the widgets. I'm curious how experienced CCS users organize these two sections on their web server.
In past projects I created by hand, the public pages start in the root of the website, and may or may not use any directories.
I always put the staff tools in a separate directory, such as /staff/.
The two sections are completely distinct, with no links between the two.
So now I'm framing this up in CCS. It seems CCS really does not want to use multiple directories...everything ends up in one place. I can see three ways to deal with this:
1. Just let all the files (public and staff) sit in the same place, not linking to each other. I suppose this shouldn't be a problem, but really grates against my organizational tendencies. It makes me nervous about accidentally linking to inappropriate files, or forgetting to protect each file individually, as opposed to just protecting the whole directory once and being done with it.
2. Create two completely distinct CCS projects, each in a separate folder. It seems that project-level settings aren't too complex or dynamic, so that might not be too bad. (I'm currently leaning toward this approach.)
3. Create one project, but do whatever it takes to get CCS to put different pages in different folders, with different headers and such. I haven't pursued this too far, but I'm getting the feeling I'd be fighting CCS on this one. Any observations on that hunch?
So...how do you experienced CCS designers approach this situation? I'm sure 99% of all CCS projects have the same public/staff areas.
-dave
_________________
David Hempy
Director of Broadcast and Education Technology
Kentucky Educational Television
800-333-9764 |
 |
 |
Don Safar
|
| Posted: 06/24/2004, 10:34 AM |
|
Just look at the CCS Example Pack for utilizing multiple directories.
"dhempy" <dhempy@forum.codecharge> wrote in message
news:240d9dc21b8463@news.codecharge.com...
> I'm building a pretend site to evaluate CodeCharge Studio...just a tiny
site
> with a public list of widgets, and a set of staff tools to edit the
widgets.
> I'm curious how experienced CCS users organize these two sections on their
web
> server.
>
> In past projects I created by hand, the public pages start in the root of
the
> website, and may or may not use any directories.
>
> I always put the staff tools in a separate directory, such as /staff/.
>
> The two sections are completely distinct, with no links between the two.
>
> So now I'm framing this up in CCS. It seems CCS really does not want to
use
> multiple directories...everything ends up in one place. I can see three
ways
> to deal with this:
>
> 1. Just let all the files (public and staff) sit in the same place, not
linking
> to each other. I suppose this shouldn't be a problem, but really grates
> against my organizational tendencies. It makes me nervous about
accidentally
> linking to inappropriate files, or forgetting to protect each file
> individually, as opposed to just protecting the whole directory once and
being
> done with it.
>
> 2. Create two completely distinct CCS projects, each in a separate folder.
It
> seems that project-level settings aren't too complex or dynamic, so that
might
> not be too bad. (I'm currently leaning toward this approach.)
>
> 3. Create one project, but do whatever it takes to get CCS to put
different
> pages in different folders, with different headers and such. I haven't
pursued
> this too far, but I'm getting the feeling I'd be fighting CCS on this one.
Any
> observations on that hunch?
>
>
>
> So...how do you experienced CCS designers approach this situation? I'm
sure
> 99% of all CCS projects have the same public/staff areas.
>
>
> -dave
>
> _________________
> David Hempy
> Internet DBA
> Kentucky Educational Television
> 800-333-9764
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
|
