Taxonomy Node creates a single node of a configurable content type for each term in a specific vocabulary. This is the start of documentation for the node.

Install in /sites/all/modules as usual. Go to Administer » Site building » Modules and switch on the following entry.
Taxonomy Node 6.x-1.0-beta3 Associates automatically a taxonomy term with a node.

You get the following message.
The Taxonomy Node module was installed. This module extends the configuration screen of vocabularies so you can associate content types with them.

Go to Administer » By module » Taxonomy Node.
Taxonomy Node 6.x-1.0-beta3 Associates automatically a taxonomy term with a node.

You get the following option.
[ ] Map Node Operations
Select this checkbox if you want to map node operations to term operations. Creating a content type associated to vocabularies will create terms on those vocabularies. Deleting or unpublishing a node will delete the associated term, publishing it back will recreate it. Updating the name and hierarchy is still only possible on by editing the actual term.

The readme file says:
6. (Optional) Go To "Administer" -> "Settings" -> "Taxonomy Node" and choose if you want node operations to sync to specific terms.

Where do you go next? There is no change in Administer » Content management » Content types. There is one change in Administer » Content management » Taxonomy. When you add or edit a vocabulary, you select a content type to associate with the vocabulary. The content type has to be defined first. If you want to add a content type to vocabulary PHP, you would create content type PHP first then edit vocabulary PHP and select content type PHP

For my test, I created content type PHP with everything the same as content type Page except:
Name: PHP
Type: php
Description: Content type for vocabulary PHP.

I then edited vocabulary PHP and there was a new option box with two options, a drop down list to select the content type and a check box to create nodes for existing terms. I do not know what happens when there is already a page the same as a term.

Taxonomy Node
Content type: PHP

Choose the content type that will be created when adding new terms. Important note: If you change your content type selection once nodes have been created, you will have to manually remove the already created nodes for each of the terms of this vocabulary as well as unset the old content type from the Types associated to this vocabulary.
[ ] Batch create
Select this checkbox if you want to create content types of the current terms inside this vocabulary. There is a limit of 50 nodes to prevent the script from timeout. If you have more than 50 terms you will have to edit and check this box until you get a "0" nodes created message.

I added the content type PHP for vocabulary PHP using the batch create option and received the following messages
Taxonomy Node: Information set.
Taxonomy Node: Batch operation, 9 nodes created.
Updated vocabulary PHP.

Editing a node

When I visit one of the nodes created by Taxonomy Node, I do not get the edit tab. I have to go to Administer » Content management » Content, find the node, then select edit. The node edit page looks normal except for the title and PHP vocabulary selection set to read only plus the following message.
Taxonomy Node: Disabled form elements should be only changed on the associated term PHP. To delete this node, just delete the term.

Converting a term to a node

I added a content type to a vocabulary then edited term Debian. The term edit page has the following additional option. The drop down selection box did not contain anything. There is a link on tcreate a new one
Taxonomy Node
There is no associated node available for this term.
You can choose an existing one from the select box below and save the term or create a new one.
Choose a free Technology to be associated to this term. The node's title will be replaced with the term name and the the parent term will be added to the node's taxonomy.

I created a new one using the link, received the following message, and there is an edit link on Debian.

Taxonomy Node: Node created.
Taxonomy Node
You can edit the associated node Debian as well.

The link went to a node edit page as described in the previous section. I created the page at http://petermoulding.com/debian. The page http://petermoulding.com/debian_5.0.5_amd64_installation has the term Debian attached so I selected the term link and ended up at a different page, http://petermoulding.com/taxonomy/term/396.

I can see how this would work for some sites. For my use, I want the taxonomy/term/396 page replaced by the debian page or to have the debian node content displayed on the taxonomy/term/396 page and the debian alias applied to taxonomy/term/396. I do not know if that requires a different option or module. Perhaps someone with more experience of this module can expand the options here.

What if the page already exists?

At this stage the complicated interactions for some of my large existing vocabularies, with 100 or more terms, are too painful to think about. I will leave the batch creation off so I can hand create each page and make sure it fits in with the existing page, the existing path alias, and the existing menu entry. Some user experience about Taxonomy Node interaction with Pathauto and similar modules would be useful.