|
Smarty
WARNING: All discussion is moving to https://reddit.com/r/smarty, please go there! This forum will be closing soon. |
|
View previous topic :: View next topic |
Author |
Message |
volkris Smarty Rookie
Joined: 08 Jul 2003 Posts: 11
|
Posted: Mon Jul 14, 2003 1:22 am Post subject: Documentation improvements: performance, summaries... |
|
|
The documentation for Smarty is really good, but next time someone decides to go fool with it I have some suggestions:
Include a section on performance. Would there be a performance hit every time I drop down to php (not that I'm doing that)? Do runtime specified extensions run less efficienty than installed ones? Should I avoid Smarty templates on Wednesdays under a full moon? Just some hints to keep in mind would be appreciated.
Section summaries. When I click on a top level section name such as "Smarty for programmers" show a couple of sentences about the contents of the section and when to use those features. To a beginner it's not absolutely and immediately obvious what's what. A small sentence would go a long way helping people quickly get comfortable with both Smarty and its documentation.
Best practices. Some general tips that illustrate the Smarty way of doing things would be nice. I know tips are dispursed throughout the docs, but it would be nice to have more involved examples in their own section. This type of this is probably one of the most asked thing in these forums.
Worst practices. What should I avoid? For example, I didn't even think to consider {capture} to be something to be avoided until boots pointed it out.
Anyway, just a couple of thoughts. Nothing pressing, but these types of tips would help people quickly get up to speed with Smarty and use it to its maximal utility. |
|
Back to top |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|