But unlike the example you linked to the fic and the podfic are actually connected. The note of Happy Endings is for a story of a similar title on a trope page.
The "problem" of someone putting fic info onto the podfic page does not happen because someone is confused. It happens because they approach the two as belonging together. And on plenty of pages the fanfic and the podfic are covered on the same page, because editors there felt that the best approach.
I don't think a header in some podfic articles that says that this article is just for the podfic, is the best solution for a relatively complex issue, i.e. ensuring that podfic aspects don't simply vanish in fic dominated environment while also allowing and inviting edits for both podfic and fic. It tries to anticipate future editing in a wiki, before even knowing what additions someone may want to make. What if an editor came along who wanted to compare the impact a fic had on them to the podfic version of the same? or contrast the reception or something else that touches on both fic and podfic? Where would they put that in an article that preemptively tried to constrain future additions? An article that the initial editor, who was focused on the podfic only, envisioned to be about the podfic only may grow into an article about podfic and fic aspects without the second editor being a "concern troll" or shortchanging the podfic content.
The examples in the wiki where someone asked their additions to remain in specific forms caused IMO unnecessary editing trouble down the line. (I'm thinking of that long quote that used to be on the Slash page and is now on the Slash Controversies page, that everybody had to work around, because it is interesting, but can't be broken up or rephrased.)
no subject
The "problem" of someone putting fic info onto the podfic page does not happen because someone is confused. It happens because they approach the two as belonging together. And on plenty of pages the fanfic and the podfic are covered on the same page, because editors there felt that the best approach.
I don't think a header in some podfic articles that says that this article is just for the podfic, is the best solution for a relatively complex issue, i.e. ensuring that podfic aspects don't simply vanish in fic dominated environment while also allowing and inviting edits for both podfic and fic. It tries to anticipate future editing in a wiki, before even knowing what additions someone may want to make. What if an editor came along who wanted to compare the impact a fic had on them to the podfic version of the same? or contrast the reception or something else that touches on both fic and podfic? Where would they put that in an article that preemptively tried to constrain future additions? An article that the initial editor, who was focused on the podfic only, envisioned to be about the podfic only may grow into an article about podfic and fic aspects without the second editor being a "concern troll" or shortchanging the podfic content.
The examples in the wiki where someone asked their additions to remain in specific forms caused IMO unnecessary editing trouble down the line. (I'm thinking of that long quote that used to be on the Slash page and is now on the Slash Controversies page, that everybody had to work around, because it is interesting, but can't be broken up or rephrased.)