Board Thread:Support Requests - Getting Technical/@comment-1676371-20200222161913

Hello, I will try to be as clear as possible. I wanted to know if the coding for the following modules can be adapted to handle tabbers, qualifiers, and subpages (that require pipelining). e.g. Username_(occupation),  Username, and Username_(occupation)/Subpage_name

Pagename_(qualifier) and Pagename/Username_(qualifier)

On the VOCALOID Wiki we use LUA to transclude content:
 * https://vocaloid.fandom.com/wiki/Module:Song
 * https://vocaloid.fandom.com/wiki/Template:Song_box_2 (works in conjunction with Song module)
 * https://vocaloid.fandom.com/wiki/Module:Album
 * https://vocaloid.fandom.com/wiki/Template:Album_box (works in conjunction with Album module)
 * https://vocaloid.fandom.com/wiki/MediaWiki:CSS/Producer.css
 * https://vocaloid.fandom.com/wiki/Template:Pwt_head (table header)
 * https://vocaloid.fandom.com/wiki/Template:Pwt_row (table row, to link)

This is an example using a producer needing a qualifier and a pipeline:
 * https://vocaloid.fandom.com/wiki/GHOST_(producer) (Current song)
 * https://vocaloid.fandom.com/wiki/GHOST_(producer)/Works,_2014 (Previous song)
 * (Previous song) needing tabbers

The template is suppose to work like this:
 * https://vocaloid.fandom.com/wiki/EmpathP (Current song)
 * The "roles" section will display when triggered by (parentheses).
 * When using pipelines the roles section has to be manually triggered using |roles =. If not then the script will call "Attention" (via visual text) to the situation until fixed.
 * Same for image, title, date, and feature vocals. While I believe the 'first_line' is one of the reasons I question if there a limit to the coding and that should we change our editing techniques to accommodate the module instead. 