How to use {tag_pagecontent} correctly?

Report · Mar 21, 2013

I've been all over the place and haven't seen anything about how {tag_pagecontent} works and what it is used for. I understand it is the "editable region " of the page but it doesn't work like I would think it should. To make matters worse, there seems to be no documentation out there for me to learn. For now, I've been hiding them in places on the page where they won't be noticed and using Dreamweaver's editable regions.

What I've gotten from Youtube, Google and BC is that you NEED one, and only one, instance of {tag_pagecontent} in each template. That's it - that's all I know.

It seems from trial and error that you can put {tag_pagecontent} inside one set of HTML tags to make it editable. Got it. So if I want to make a paragraph editable in BC's in-context editing tool I can do this:

<body>

<p>{tag_pagecontnet}</p

</body>

That seems to work fine. But what happens with multiple paragraphs, div's, h1's, etc? Plus Dreamweaver has editable regions for templates as well. For example:


	<!-- Start Tabs -->
	<div class="span6">
	<h3>Tabs</h3>

	<!-- Start Tabs Widget -->
	<div class="tabs">
	<!-- Start Tabs Nav -->
	<ul>
	<li><a href="#tabs-1">Who we are</a></li>
	<li><a href="#tabs-2">What we do</a></li>
	<li><a href="#tabs-3">How we do it</a></li>
	</ul>
	<!-- End Tabs Nav -->

	<!-- Start Tab -->
	<div id="tabs-1">
	<p>Proin elit arcu, rutrum commodo, vehicula tempus, commodo a, risus. Curabitur nec arcu. Donec sollicitudin mi sit amet mauris. Nam elementum quam ullamcorper ante. Etiam aliquet massa et lorem. Mauris dapibus lacus auctor risus. Aenean tempor ullamcorper leo. Vivamus sed magna quis ligula eleifend adipiscing. Duis orci. Aliquam sodales tortor vitae ipsum. Aliquam nulla. Duis aliquam molestie erat. Ut et mauris vel pede varius sollicitudin. Sed ut dolor nec orci tincidunt interdum. Phasellus ipsum. Nunc tristique tempus lectus.</p>
	</div>
	<!-- End Tab -->

	<!-- Start Tab -->
	<div id="tabs-2">
	<p>Morbi tincidunt, dui sit amet facilisis feugiat, odio metus gravida ante, ut pharetra massa metus id nunc. Duis scelerisque molestie turpis. Sed fringilla, massa eget luctus malesuada, metus eros molestie lectus, ut tempus eros massa ut dolor. Aenean aliquet fringilla sem. Suspendisse sed ligula in ligula suscipit aliquam. Praesent in eros vestibulum mi adipiscing adipiscing. Morbi facilisis. Curabitur ornare consequat nunc. Aenean vel metus. Ut posuere viverra nulla. Aliquam erat volutpat. Pellentesque convallis. Maecenas feugiat, tellus pellentesque pretium posuere, felis lorem euismod felis, eu ornare leo nisi vel felis. Mauris consectetur tortor et purus.</p>
	</div>
	<!-- End Tab -->

	<!-- Start Tab -->
	<div id="tabs-3">
	<p>Mauris eleifend est et turpis. Duis id erat. Suspendisse potenti. Aliquam vulputate, pede vel vehicula accumsan, mi neque rutrum erat, eu congue orci lorem eget lorem. Vestibulum non ante. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Fusce sodales. Quisque eu urna vel enim commodo pellentesque. Praesent eu risus hendrerit ligula tempus pretium. Curabitur lorem enim, pretium nec, feugiat nec, luctus a, lacus.</p>
	<p>Duis cursus. Maecenas ligula eros, blandit nec, pharetra at, semper at, magna. Nullam ac lacus. Nulla facilisi. Praesent viverra justo vitae neque. Praesent blandit adipiscing velit. Suspendisse potenti. Donec mattis, pede vel pharetra blandit, magna ligula faucibus eros, id euismod lacus dolor eget odio. Nam scelerisque. Donec non libero sed nulla mattis commodo. Ut sagittis. Donec nisi lectus, feugiat porttitor, tempor ac, tempor vitae, pede. Aenean vehicula velit eu tellus interdum rutrum. Maecenas commodo. Pellentesque nec elit. Fusce in lacus. Vivamus a libero vitae lectus hendrerit hendrerit.</p>
	</div>
	<!-- End Tab -->
	</div>
	<!-- End Tabs Widget -->
	</div>
	<!-- End Tabs -->

All of those regions need to be editable. I can replace ONE of them with a {tag_pagecontent} and make that editable but what about the rest? I've been using the editable regions in Dreamweaver and they work fine but the content isn't editable in-context in BC's tool.

Surely there is something I am missing... There can't be a limit of just ONE editable element when pages have become quite complex these days... right? I want to say "this is editable and this is editable and this is editable..." but how?

Sorry for the long post, I just can't figure this out!

Report · Mar 22, 2013

Hi,

Editable regions can be assigned to both templates and standard pages. Basically they apply to elements like links, divs, images, etc. Here's the reference:

- http://kb.worldsecuresystems.com/839/cpsid_83979.html

- http://kb.worldsecuresystems.com/838/cpsid_83855.html

- http://kb.worldsecuresystems.com/838/cpsid_83856.html

- http://kb.worldsecuresystems.com/838/cpsid_83852.html

A generic example of {page_content} can be sketched like this:

Aside from buliding regular pages, you can also construct (or import) templates in BC. That serves to streamline the process of creating new pages, allowing to user to focus on generating the relevant content for each new page, without bothering for what would be static/repetitive content. To that extent, a page template can look like this:

<!DOCTYPE html>
<html lang="en" class="no-js">
<head>
<title>YOUR PAGE TITLE</title>
<link href="/StyleSheets/ModuleStyleSheets.css" type="text/css" rel="StyleSheet" />
<script type="text/javascript">var jslang='EN';</script>
<script type="text/javascript" src="/CatalystScripts/ribbon.js"></script>
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></script>
</head>
<body>
{tag_pagecontent}
</body>
</html>

While your page can be just this:

<div> <p> Hello World</p><img src="images/img.gif" ></div>

Here's a good reference:

http://bcgurus.com/tuts/site-templates

Kind Regards,

Alex

Report · Mar 22, 2013

Thank you very much Alex! That's all good info. I'll sit down and read through them.

The example you gave was a huge help. I was thinking incorrectly about how to apply the tag - now it makes a lot more sense.

Adobe Community

How to use {tag_pagecontent} correctly?