This post is solely for my client and managers.
We have got caught in the situations where we receive very minor change from the client and in reply we have sent a longer time estimate. As a result, we have to spend next two days to explain to the client why the minor change is a template change and would require us to follow a small development life cycle period before releasing to production.
Lets see, if i can simplify template in common terms then it would easier for me to just redirect them here and not spend next two days explaining them.if interested in only technical info,Go to Wikipedia.
I have a website with five products and their URLs are somewhat like:
It could appear that there are 5 separate pages with each containing product details. But what if there is only one page exists and just content of that page changes for each product.
Yes, this single page behaves as template.
When the pages follow same format the developers decides to use a template in which appearance, code,placeholders remains same but only the content filling these placeholders varies.
Just think of your newspaper, where each page can be considered as template and only the content changes daily for each page but still the appearance remains same all days.
if some day,client comes with a requirement to bring some changes in the pages then these changes happens at the template level and will effect all the pages which are following that particular template.
And so there is a small development life cycle followed to introduce the changes at template level which requires liberty while providing time estimation.