Could you expand your opening comments in each source code file?
The .py source in the Gramps folder says it is for WordPress but doesn't mention that it is an Add-on for Gramps to generate WordPress compatible output.
Likewise, the .php source mentions Gramps but not WordPress.
Because the tools interweaves both, the need to eliminate ambiguity is actually raised. Introductory comments probably shouldn't just say 'Gramps' or 'WordPress' but should also actually define the objective of those applications.
Could you expand your opening comments in each source code file?
The .py source in the Gramps folder says it is for WordPress but doesn't mention that it is an Add-on for Gramps to generate WordPress compatible output.
Likewise, the .php source mentions Gramps but not WordPress.
Because the tools interweaves both, the need to eliminate ambiguity is actually raised. Introductory comments probably shouldn't just say 'Gramps' or 'WordPress' but should also actually define the objective of those applications.