> > but i don't really see any problem with the other pages being in the
> > same namespace as long as what is there is chosen wisely and is
> > unlikely to ever be used as a forum name. i don't think
> > "stylesheets" or "javascripts" or "preferences" would ever be forum
> > names. for things like that tips page, a /static directory can be
> > reserved where things can be lumped into later.
Ok, how about this. Keep the forums at the top level. Move all the
static stuff into /public/ (or /static/) - javascripts, css, pics,
etc. Move all the non-forum dynamic stuff (like admin) into /-/ -
this makes it easier to add other dynamic stuff later without
constantly worrying about clashing with forum names. This means that
"public" (or "static") and "-" are not valid forum shortnames, but the
namespace is not otherwise polluted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From email exchange with Gary G.
> > but i don't really see any problem with the other pages being in the
> > same namespace as long as what is there is chosen wisely and is
> > unlikely to ever be used as a forum name. i don't think
> > "stylesheets" or "javascripts" or "preferences" would ever be forum
> > names. for things like that tips page, a /static directory can be
> > reserved where things can be lumped into later.
Ok, how about this. Keep the forums at the top level. Move all the
static stuff into /public/ (or /static/) - javascripts, css, pics,
etc. Move all the non-forum dynamic stuff (like admin) into /-/ -
this makes it easier to add other dynamic stuff later without
constantly worrying about clashing with forum names. This means that
"public" (or "static") and "-" are not valid forum shortnames, but the
namespace is not otherwise polluted.