Fanlore naming conventions say: "Articles about individual fanworks should include only the work's title in the page name". That's the rule for all fanwork pages. Sadly, technical reason's dictate that every page must have a unique title and that's where disambiguation comes in.
It's not a honorific (at least not the way I understand it? The dictionary tells me it means "giving or expressing honor or respect"; is there another meaning I'm missing as an EFL speaker?), it's a way to make it possible for several pages with exactly the same name to exist on Fanlore. If the name is not exactly the same (the 24 Hours/24 HOURS example I gave you on one of the talk pages), there is no need for disambiguation in the title of a page. That said, if there is going to be a separate page about a podfic as a fanwork, the naming of the page should follow the naming rules for all fanwork pages, otherwise the treatment of podfic on Fanlore would be not equal to the treatment of other fanworks (see for example Break Like Time: The Fifth Column, a page about a fic trailer for the story of the same name which doesn't have a Fanlore page) and therefore send the message that podfic is not equal. Also, it wouldn't be practical because it means editors would be expected to know that there are different rules for podfic pages than for all other pages, which increases the risk of breaking some editing rules without meaning to.
Adding the word "Podfic" to the name of a podfic, if that's not how the podfic creator named it to begin with, would be forcing a different name on the work and it would set precedent for that kind of approach for other fanwork pages. Forcing a different name on a fanwork is generally something Fanlore doesn't do and I think it's something we really should avoid. (However, if it became general practice for podficcers to include "Podfic" in the name of the podfic it would be part of the page title but so far I haven't seen that practice in naming podfics; the name is easy to find out by checking the entry where the podfic was posted and by checking the cover associated with it.)
Adding a disambiguation line makes sense when there already is a page for the fic, although I would hope it would already be wikilinked in the "Based On" field in the template or in the text of the page. Always adding a disambiguation line with a redlinked non-existing page would suggest that for every podfic page to exist, there would also need to be a corresponding fic page. On the one hand, that's not true, on the other hand, it would elevate the fic page to a higher importance than the podfic page while at the same time marking the podfic as a lesser fanwork that is always in need of the disclaimer that it's not something else.
Frankly, that seems like overkill to me. What's the worse that could happen? Some other editor feels inspired to add more information! That's a good thing. So what if it's about the fic? It's still new information that wasn't there before. Success! What to do with that information is part of what gardeners and other editors are there for. Maybe it should be moved to a separate page. Maybe it should both be on the same page. Maybe it's wrong and needs to be removed. Maybe it should be reworded and moved to a different section. Maybe there need to be new templates for pages that combine more than one fanwork. Maybe one or the other template works fine, depending on the examples in question. These discussions happen on the talk pages of the respective articles. Fanlore articles aren't static. They change over time and they change a lot. Someone adding something in a way you think is wrong? Completely normal and exactly what drives the growths and changes of an article, because everything can be corrected. Also, making mistakes is normal when editing a wiki, especially for new editors, and an essential part of the learning curve when editing a wiki. There is no rule that won't be broken repeatedly by several people. Basing decisions only on the fear that someone might make a mistake is not a good basis for making decisions about wiki editing rules.
Even if we go by the assumption that it was not a mistake and instead the edit of someone who thought that both fic and podfic belong on the same page, it would still hardly be a unique reaction to podfic. Just look at pages about zines made of popular netfic. Also many, many fic pages have sections about podfic on the page. If that's an acceptable way of dealing with this, the other way around shouldn't be a problem either. If the section about a fic gets too big, it can still be moved to a separate page, just like it's done the other way around.
Personally, I like aethel's suggestion best because it clearly marks the page as being about a particular type of fanwork and gives a prominent link in the header that invites the reader to find out more about that particular thing. Also, it treats all fanwork pages the same, improves the templates, and gives us reasons to make even more specific templates, which sounds like an all-around win to me.
no subject
It's not a honorific (at least not the way I understand it? The dictionary tells me it means "giving or expressing honor or respect"; is there another meaning I'm missing as an EFL speaker?), it's a way to make it possible for several pages with exactly the same name to exist on Fanlore. If the name is not exactly the same (the 24 Hours/24 HOURS example I gave you on one of the talk pages), there is no need for disambiguation in the title of a page. That said, if there is going to be a separate page about a podfic as a fanwork, the naming of the page should follow the naming rules for all fanwork pages, otherwise the treatment of podfic on Fanlore would be not equal to the treatment of other fanworks (see for example Break Like Time: The Fifth Column, a page about a fic trailer for the story of the same name which doesn't have a Fanlore page) and therefore send the message that podfic is not equal. Also, it wouldn't be practical because it means editors would be expected to know that there are different rules for podfic pages than for all other pages, which increases the risk of breaking some editing rules without meaning to.
Adding the word "Podfic" to the name of a podfic, if that's not how the podfic creator named it to begin with, would be forcing a different name on the work and it would set precedent for that kind of approach for other fanwork pages. Forcing a different name on a fanwork is generally something Fanlore doesn't do and I think it's something we really should avoid. (However, if it became general practice for podficcers to include "Podfic" in the name of the podfic it would be part of the page title but so far I haven't seen that practice in naming podfics; the name is easy to find out by checking the entry where the podfic was posted and by checking the cover associated with it.)
Adding a disambiguation line makes sense when there already is a page for the fic, although I would hope it would already be wikilinked in the "Based On" field in the template or in the text of the page. Always adding a disambiguation line with a redlinked non-existing page would suggest that for every podfic page to exist, there would also need to be a corresponding fic page. On the one hand, that's not true, on the other hand, it would elevate the fic page to a higher importance than the podfic page while at the same time marking the podfic as a lesser fanwork that is always in need of the disclaimer that it's not something else.
Frankly, that seems like overkill to me. What's the worse that could happen? Some other editor feels inspired to add more information! That's a good thing. So what if it's about the fic? It's still new information that wasn't there before. Success! What to do with that information is part of what gardeners and other editors are there for. Maybe it should be moved to a separate page. Maybe it should both be on the same page. Maybe it's wrong and needs to be removed. Maybe it should be reworded and moved to a different section. Maybe there need to be new templates for pages that combine more than one fanwork. Maybe one or the other template works fine, depending on the examples in question. These discussions happen on the talk pages of the respective articles. Fanlore articles aren't static. They change over time and they change a lot. Someone adding something in a way you think is wrong? Completely normal and exactly what drives the growths and changes of an article, because everything can be corrected. Also, making mistakes is normal when editing a wiki, especially for new editors, and an essential part of the learning curve when editing a wiki. There is no rule that won't be broken repeatedly by several people. Basing decisions only on the fear that someone might make a mistake is not a good basis for making decisions about wiki editing rules.
Even if we go by the assumption that it was not a mistake and instead the edit of someone who thought that both fic and podfic belong on the same page, it would still hardly be a unique reaction to podfic. Just look at pages about zines made of popular netfic. Also many, many fic pages have sections about podfic on the page. If that's an acceptable way of dealing with this, the other way around shouldn't be a problem either. If the section about a fic gets too big, it can still be moved to a separate page, just like it's done the other way around.
Personally, I like aethel's suggestion best because it clearly marks the page as being about a particular type of fanwork and gives a prominent link in the header that invites the reader to find out more about that particular thing. Also, it treats all fanwork pages the same, improves the templates, and gives us reasons to make even more specific templates, which sounds like an all-around win to me.