-
Notifications
You must be signed in to change notification settings - Fork 156
Conversation
or should we use the sandbox for the quick tour to avoid having to set up an AppBundle and such stuff? |
9ed0555
to
8cf24b4
Compare
That's what I had in mind. Imo, people should mostly look in the quick tour, not write. |
good. i will see what i can do tomorrow on the train
|
quick_tour/the_model.rst
Outdated
public function load(ObjectManager $documentManager) | ||
{ | ||
// ... | ||
$route = new Route(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we do all this in the model chapter, or rather just show the node dump here, and go to the route chapter for adding the route?
quick_tour/the_model.rst
Outdated
$page->setName('new_page'); // the name of the node | ||
$page->setName('quick-tour'); // the name of the node | ||
|
||
vno sandbox übernehmen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i need to update the code here.
@@ -157,6 +131,8 @@ more SEO information. | |||
Sonata Admin | |||
------------ | |||
|
|||
TODO: rewrite for sonata admin integration split out |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this says todo...
574dfb2
to
8e49370
Compare
this is ready for final review. glad for input, i might have missed places but don't see it anymore after having gone over it several times... |
6908096
to
f4b71b9
Compare
ping @wouterj do you want to review this or should i just merge it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice job! Just read everything and commented on some things, but looks perfect in general.
quick_tour/the_big_picture.rst
Outdated
@@ -25,36 +25,31 @@ the core parts of the CMS. | |||
|
|||
The CMF is created to solve this framework versus CMS dilemma. It provides | |||
bundles, so you can easily add CMS features to your project. But it also | |||
provides flexibility and in all cases you are using the framework, so you can | |||
provides flexibility and you can use the underlying Symfony framework to | |||
build custom functionality the way you want. This is called a `decoupled CMS`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that my previous sentence was all but correct, but let's improve it even more. Maybe something like:
The Symfony CMF is created to solve this framework versus CMS dilemma. It
provides bundles, so you can easily add CMS features to your project. Yet, as
you're still using the Symfony framework, you can build any custom functionality
you can think of. This flexibility is called a `decoupled CMS`_.
quick_tour/the_big_picture.rst
Outdated
build custom functionality the way you want. This is called a `decoupled CMS`_. | ||
|
||
The bundles provided by the Symfony CMF can work together, but they are also | ||
able to work standalone. This means that you don't need to add all bundles, you | ||
can decide to only use one of them (e.g. only the RoutingBundle or the MediaBundle). | ||
can decide to only use one of them (e.g. only the RoutingBundle or the SeoBundle). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, SeoBundle is just the one bundle that doesn't work standalone nicely :). Maybe leave out the second example here?
extension. After that, run these commands: | ||
|
||
.. code-block:: bash | ||
|
||
$ cd cmf-sandbox | ||
$ cp app/config/phpcr_doctrine_dbal.yml.dist app/config/phpcr.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Windows, cp
is not available by default. Maybe we should add a comment about it:
$ cd cmf-sandbox
$ cp app/config/phpcr_doctrine_dbal.yml.dist app/config/phpcr.yml
# Or when you're on a Windows PC:
# $ copy app\config\phpcr_doctrine_dbal.yml.dist app\config\phpcr.yml
$ php bin/console doctrine:database:create
[...]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
quick_tour/the_big_picture.rst
Outdated
content is updated. | ||
Now you know the request flow, you can start editing content. While the normal | ||
usage will be to edit content through a web interface, the CMF sandbox also | ||
supports loading content from static files. This is mainly useful for testing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
double space after "supports"
quick_tour/the_model.rst
Outdated
time, you'll create a page by doing it yourself. | ||
Now that you know a little bit more about PHPCR and you know the tool to interact | ||
with it, you can start using it yourself. In the previous chapter, you edited | ||
a page by using a yaml file which was parsed by the fixture loader of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"a Yaml file"
quick_tour/the_router.rst
Outdated
configuration or by tagging the router services. For instance, the router used | ||
by the SimpleCmsBundle is a service registered by that bundle and tagged with | ||
``cmf_routing.router``. | ||
You see that a route like ``/company/team``, which consist of 2 "path units", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 -> two
quick_tour/the_router.rst
Outdated
by the SimpleCmsBundle is a service registered by that bundle and tagged with | ||
``cmf_routing.router``. | ||
You see that a route like ``/company/team``, which consist of 2 "path units", | ||
has 2 documents in the PHPCR tree: ``company`` and ``team``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 -> two
contains all items implementing the ``NodeInterface`` inside the | ||
``/cms/simple`` (since the basepath in the Standard Edition is ``/cms``). | ||
``/cms/menu/main`` (since the basepath in the CMF Sandbox is ``/cms/menu``). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"inside the /cms/menu/main
path"
persisted using PHPCR, it also needs a block document, which is located in | ||
``Acme\DemoBundle\Document\UnitBlock``. | ||
``AppBundle\Document\UnitBlock``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, this paragraph is no longer true, is it? Maybe comment it out for now and add this block when reworking the CMF sandbox (nr. 1 priority for me after 2.0 stable).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i removed the part about the blocks being custom blocks because that is no longer true. but we do show blocks on the homepage of the sandbox.
|
||
You can also disable/enable all CMF Admin classes by configuring this on the | ||
``cmf_core`` bundle: | ||
By default, the Admin classes for the CMF bundles that are installed are activated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the other way around: By default, all admins are disabled. Should we change that in the integration bundle?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, you are right. i would say lets keep it that way. otherwise adding new admins would have to be considered a BC break, or we would have to be inconsistent when adding new admins. i adjusted the doc
f4b71b9
to
a63ce48
Compare
thanks for the feedback. pushed an update that should adress all of this. |
a63ce48
to
ba4955a
Compare
standard editionsandbox, or if we first need to create some more things now.fix #788