![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Title, author, and image for current story. B. Story text. Content SourcesThe story page has a single content source, the Stories table from the Stories database. When the user arrives at this page by clicking on a story link, the URL includes the ID of the story that the user has clicked. The Stories content source uses this ID to automatically select the appropriate story. TabsThe Administration View tab uses Show Details of Current Record so that a user can click over to the administration view to edit the current story. A.The title, author, and image are all simple bindings that display the appropriate parts of the story. B.The main story text is also a simple binding. Notice that the mock content consists of several fake paragraphs separated by line breaks. There's no way to create a binding that spans multiple paragraphs in GoLive, but this technique allows you to design the layout as a single paragraph. The actual database content can contain any number of paragraphs, as well as arbitrary markup. A story author can use HTML and CSS to format his story. |