Now to address what you were actually talking about earlier. I have a couple concerns about using a single-line placeholder.

-	**Performance:** In order to determine if the content that follows a single-line block is default content, you will have to scan ahead to the end of the file looking for an endblock statement. This won't be achievable using the current one forward-pass parser that's written. The best way I can think to implement this would be to add a pre-parse step that scans the file and tags any single-line blocks with an <% endblock %>. Then in the second pass, the parser can assume that any content following a <% block %> statement is default content.

-	**Potential ambiguity:** Can default content include a block? In other words, would you allow this:

	```html
	<% block container %>
	<div class="container">
		<% block content %>
	</div>
	<% endblock %>
	```

	If so, then the parser is going to have an ambiguity problem. Is the above code a single-line `container` block, followed by a `content` block with default content, or a `container` block with default content containing a single-line `content` block? If you don't want to allow this behavior it's not an issue, but I can see it being useful in certain scenarios.

-	**Local block variable:** My reason for opting to use a local variable instead of an embed statement was to allow the ability conditionally include decorative HTML in the layout file. For example:

	```html
	<% if (blocks.title) { %>
	<div class="page-title">
		<h1><%- blocks.title %></h1>
	</div>
	<% } %>
	```

	This doesn't mean that you can't also have a command statement to include a block, but <%- blocks.title %> seems just as concise as <% block title %>, and precludes the other issues.