Change Details

//The first version of this task is a draft, created as a follow-up to T234661. Please feel free to edit it and flesh it out.// At {T234661}, the topic of the lack of sufficient tools for dependency tracking tools for modules and templates came up several times. The current tools for this are: - Special:WhatLinksHere - Cascading importing Some other proposed ideas: - Have a list of extensions that are needed to render a given page. For example, if a page has <ref> tags (directly or through a template), then Cite is needed. - //Add here// What else is needed?

//The first version of this task is a draft, created as a follow-up to T234661. Please feel free to edit it and flesh it out.// At {T234661}, the topic of the lack of sufficient tools for dependency tracking tools for modules and templates came up several times. The current tools for this are: - Special:WhatLinksHere - Cascading importing Some other proposed ideas: - Have a list of extensions that are needed to render a given page. For example, if a page has <ref> tags (directly or through a template), then Cite is needed. - The GlobalUsage extension can be enhanced to show usage of modules and templates. - //Add here// What else is needed?

//The first version of this task is a draft, created as a follow-up to T234661. Please feel free to edit it and flesh it out.// At {T234661}, the topic of the lack of sufficient tools for dependency tracking tools for modules and templates came up several times. The current tools for this are: - Special:WhatLinksHere - Cascading importing Some other proposed ideas: - Have a list of extensions that are needed to render a given page. For example, if a page has <ref> tags (directly or through a template), then Cite is needed. - The GlobalUsage extension can be enhanced to show usage of modules and templates. - //Add here// What else is needed?