CHAPTER 11 Supporting Your Product
<?php include('perch/runtime.php'); ?>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" /><title>Perch Example Page</title>
</head>
<body>
<?php perch_content('Content'); ?>
</body>
</html>We never want the experience of getting started with the product to
become more complex than that. However, our customers see almost every
feature request as an addition to perch_content — the tag that declares a
Perch region on your page. They want to pass an ever increasing number
of variables when creating a region, which would leave us with something
like the following on the page, and users would have to make a whole
bunch of choices just to get started.<?php include('perch/runtime.php'); ?>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Perch Example Page</title>
</head>
<body>
<?php perch_content('Content','index.php','article','html',true,'ti-
tle','ASC',‘singlepage',true,'index.php.true,1,true,',','admin,hr','tit-
le,text'); ?>
</body>
</html>We want people to get started simply and then discover the more complex
features as they need them. So, while we log these requests, we don’t imple-
ment them in the way the customer has requested. That might work for that
particular customer, but it would damage the experience of so many others.