You don't - that's not the design idea. The issue is nothing to do with hiding things. Just as adornments aren't pertinent to Outline view and are not shown, the reverse is true with separators. They are effectively dividers/headings for the Outline. Separators aren't visible in Maps except if they are also containers.

Separators were not supposed to act as containers but, by accident of birth, it appeared they were and people started using/liking them thus before the original design intent could be enforced. Now that separators can be a container, it posed a problem for maps which could not see/access the nested content. So:

• Note separator: only shown in outline.
• Container separator: shown in both outline and map.

On further checking, I believe separator containers/children showing up in map or chart view is an error (as at v6.0.0).

Thanks both,

Indeed, indenting the container with the prototypes and templates until they are indented more than any container above them, does indeed work.

I thought it might have been a bit of script that could be toggled to show/hide content in the map view.

Cheers,

Graham

Hello Mark,

Unfortunately, I am obviously not following this, but keen to adopt what you have found to be best practice. As you know, exporting is a critical aspect of Tinderbox for me to sort out.

Are you suggesting a set up like this

Data Container
---Data note 1
---Data note 2
---Data Note 3
Prototypes
---prototype 1
---prototype 2
Templates
---template 1
---template 2

OR

Data Container
---Data note 1
---Data note 2
---Data note 3
prototype 1
prototype 2
template 1
template 2

Or something different. Neither of these arrangements are helping me exclude the templates/prototype notes from the map view.

Cheers,

Graham

Yes, two root containers for Content and System would seem to make sense.

Have you sorted out how to stop the System part appearing in the map view?

Graham

OK, I'll preface by saying there's no one right way. The key underlying part is start your 'content' in a container. Whether there are one or more other root level containers depends on your experience and needs. Bear in mind that if you get TB to add your first templates and prototypes, it will create folders at root level - though you could move them after.

If exporting bear in mind that an export, even if of only one note, exports relative to the root of the TB doc.  So if you export to the desktop and your exporting file is 5 containers down the the doc will make 5 nested containers on the desktop with your file inside.  For this reason, if exporting an HTML site (like aTbRef) it makes sense to have:

home page note/container
-> all other content
Prototypes/ (doesn't export)
Templates/  (doesn't export)
CSS/
Scripts/

Now the scripts and css folders are direct children of the root of the exported site, for instance, here's aTbRef:



The other root level things are bits like RSS feeds (created via agents). There are content of sorts but live - deliberately - in the root as that's where I want them to export.

I'll start a new reply for an alternate take where it's not export centric.

Let's assume we're going to do a mostly Map based (to start with) project. I'd sketch a layout like this:



BY all means sweep the prototypes and such into one common folder. Actually that side of things doesn't matter.  What does matter, is having all the 'content', i.e. not admin/back-of-house, segregated into a separate outline branch. In the outline as shown a query for descendedFrom("Container for content") can't ever match a prototype as it's outside that part of the outline.

However, the map of the root looks a bit ropey:



But, we're not using that map.  Let's hoist the view:



Now, we've our work map and in the other tab, the whole outline.

I hope that gives a few ideas...

I have found it useful to use separators with labels and distinctive colors to divide up the content and management areas. They can also be used to hold metanotes to me about tasks or gotchas in that section.

A screenshot is at:

https://www.dropbox.com/s/3c2bdk6a74ur9c7/Screen%20Shot%202014-06-04%20at%203.16...

Now this is v5, and part of the reason is that I typically have a dozen windows open. The color scheme helps me know what is what.

This may not make as much sense in v6 and following, but something to consider.