On 9/27/13, Ryan Ollos <[email protected]> wrote: > On Thu, Sep 26, 2013 at 1:08 PM, Olemis Lang <[email protected]> wrote: > >> On 9/26/13, Ryan Ollos <[email protected]> wrote: >> > On Tue, Sep 24, 2013 at 11:29 PM, Apache Bloodhound < >> > [email protected]> wrote: >> > >> [...] >> > >> > Btw, how does one navigate to the product view >> > `/products/<product>/products/<product>`? It doesn't seem to be linked >> from >> > anywhere, at least in a default configuration. Shouldn't it be linked >> from >> > the product list page `/products`? >> > >> >> AFAICT products list page (both global and local) are not linked from >> anywhere else (cmiiw) . AFAICR there was a main nav once upon a time >> ... prior to bep 3 and latest theme implementations . > > > I propose we do the following: > - Link the Product list page (`/products`) from somewhere that is always > visible (mainnav would be the most obvious choice).
+ > - From the produce list page, link to `product_view.html` for each > product. It's the Dashboard . The fact is that the default product URL namespace overlaps with product_view.html in global scope but not in product scope . Therefore , in order to provide a consistent navigation in all contexts . Indeed /product_view.html is a kind of dashboard too . In the case of sub-domain deployments that overlapping does not exist , that's why I noticed these issues ;) > Maybe the //Home// button should direct there? > IMO the home button should point at the product home page , usually the wiki but maybe other page in the web site depending on configuration . > Thoughts? I'd rather advocate inserting a new nav item e.g. View pointing at $product_base_url/products/<prefix> which would be expanded to /products/<prefix>/products/<prefix> in default install or <prefix>.dom.ain/products/<prefix> for sub-domains (... or the corresponding path if other URL namespace is deployed ;) Items would look like this ... View | Edit | Home | Tickets | Wiki [...] -- Regards, Olemis - @olemislc
