Closed dbu closed 7 years ago
I would keep it simple and not explain sonata again, means:
i wonder how much of https://github.com/symfony-cmf/symfony-cmf-docs/blob/master/tutorial/sonata-admin.rst we should move here or if we leave that in the tutorial?
sonata has enough own documentation, the phpcr-backend part too. With that bundle we also alligned a lot, so one single admin example can be enough from my POV.
Our main purpose is not to explain how sonata is working. We should focus on the stuff, where we present the features of the CMF mean:
Will you also do #786 here?
depends on what we mean by "all sonata docs". i think we should move bundle docs per bundle, as we clean up the bundle documentation in general. that will be more manageable than one huge move.
I would say:
@dbu are you working on this PR or can I take it over and continue writing?
i hope to find some time this friday or saturday to move this forward. until then, if you can continue with the foundations, please do. maybe we can also add some todo's here and then merge this to work in smaller junks.
Bootstrapped the documentation the way I think we should document this. I think we can merge it as is and fill in the other bundle integrations per bundle in seperate PRs.
As always, open for every comment you can think of 😃.
i fixed the errors. would love to decide on splitting configuration (and other doc) into a page per bundle and do that in here, then we can merge this and fill in things in parallel
squash and merge?
fix #785
i want to merge this asap so that we can move the individual bundle admin docs and clean up stuff. i wonder how much we want to explain about setting up sonata in general. should we leave that in the tutorial or move here?