There's a few approaches:
- If you wanted to hand-create the content for different "pages", you could create them, and wrap them in a <state> each, which you then applied or removed as needed. If you're going to remove states then it's probably best to turn pooling on. See more on states here:
http://www.laszlosystems.com/lps-2.1/docs/lzx-reference/?state.html
By the way, you could also just turn visibility on and off.
- If you wanted to have all your content to be data driven, then you could set up a template, and change its datapath to point to a specific node, say if your data was like so:
<article title="Scorching Summer Ahead!" date="March 17th, 2004" imgurl="summer.jpg">
<excerpt>
Weather analysts predict a
violently hot summer...
</excerpt>
[[your article here]]
</article>
<article title="Geese Fly Over San Francisco!" date="March 18th, 2004" imgurl="geese.jpg">
<excerpt>
An angry gaggle landed in Union Square Thursday...
</excerpt>
[[your article here]]
</article>
... they you'd have your article class and point it at the relevant <article> node in the dataset (e.g. article[1], article[2] etc.). Alternatively, you could have the article class make a request for the article data at run-time, so you'd only be fetching one article at a time.
- You might instantiate the views in the content area at run-time (e.g. new view()), although I don't recommend that approach at all.
-Antun