On 2013-10-28 08:53, David Buchmann wrote:
> In cookbook/creating_basic_cms.rst:
> 
>> +a homepage you need to actually make the CMS use this information
> to render
>> +the designated page.
>> +
>> +This is easily accomplished by adding a new action to the
>> +``DefaultController`` which forwards requests matching the route
> pattern ``/`` to
>> +to the page action::
>> +
>> + // src/Acme/BasicCmsBundle/Controller/DefaultController.php
>> + // ...
>> +
>> + class DefaultController extends Controller
>> + {
>> + // ...
>> +
>> + /**
>> + * @Route("/")
> 
> ups, i did not read closely enough. i usually have a fixed thing
> beging the homepage. but what you do is a valid use case as well, and
> an interesting one at that. the only drawback i see is which menu
> point is open then, as in simple cms menu and content tree are the
> same.

Hmm .. I would guess the content voter would work and highlight the 
correct item?

> 
> however i would redirect to that page, not simply render it. otherwise
> you show the same content under two urls which google does not like.
> 

Good point ... another option I guess would be to have "/page/home" 
redirect to "/". In any case I think just adding a note/warning for the 
user would suffice.

> --
> Reply to this email directly or view it on GitHub [1].
> 
> Links:
> ------
> [1] 
> https://github.com/symfony-cmf/symfony-cmf-docs/pull/303/files#r7241610