New in Symfony 2.2: More Documentation
January 18, 2013
•
Published by
Fabien Potencier
Warning: This post is about an unsupported Symfony version. Some of this information may be out of date. Read the most recent Symfony Docs.
The weekend is fast approaching and you're not sure how to spend it? Why not read some Symfony documentation? Since Symfony 2.1, the documentation has been improved in many ways, and quite a few cookbook entries and book chapters have been added. I won't list all the changes that were made, but here are some entry points that might help you choose what to read first.
Symfony gives you great tools to develop command line scripts. But you might wonder how you can generate URLs and send emails from the console or how to enable logging in console commands.
Symfony has some nice shortcuts that help you develop faster, but some of them are not that well-known. Do you know that you can render a template without writing a custom controller?. And do you know that you can use service container parameters in your routes?.
Some web hosting companies (and that often includes big corporation hosting facilities) are very strict about the layout of your files, especially the ones written by your application. Symfony got you covered as you can easily override Symfony's Default Directory Structure.
And if you are about to deploy your shiny Symfony application, read How to deploy a Symfony2 application.
Last but not least, you might want to better understand how HttpKernel handles a request internally; what about reading the wonderful new chapter about the HttpKernel component.
Happy reading and see you next week for Symfony 2.2.0 beta2!
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
What would be the advantages of cross posting:
- The articles could be enhanced by the community,
- The articles could be updated by the community when some updates are required because of an API change in Symfony - I see very little posts being updated and this results in outdated info,
- The documentation would be centralized in a single place and indexed.
So why don't people already cross post ?
- May be because we only have a "cookbook" and a "book" sections, we might add a "technical articles" for the articles that do not fit in the 2 former sections,
- May be because people fell they don't get enough incentive (ie credits) when doing so. Fabien, Ryan, what about adding a contributors section to the documentation (and to the downloadable PDF) ? I think we should also include commits to the documentation repository on the Sf2 contributors page[2] - to me, the documentation and the code are equally important when it come to build an awesome community.
Fabien, Ryan and the blog authors, what do you think ?
Cheers,
Victor
(XPosted on https://groups.google.com/d/msg/symfony-devs/-6HAQgAB2LY/lbaq0lTM5kYJ)
[1] https://github.com/symfony/symfony-docs
[2] http://symfony.com/contributors