Board Thread:Policies/@comment-25737724-20150608172657/@comment-25737724-20150608222937

Good questions. As it's quite a large project, apologies if I was unable to eloquently describe what everything does. I put some of this information in the documentation and can certainly beef that up too :) I didn't want to bore everyone with all of the details in the beginning but here you go :) Hatebunny wrote: Secondly, as far as release dates go, I would like for there to be a standard that uses only "Month Day, Year" or "Day/Month/Year" format, and nothing else. Not any of this "Digital first" b.s. And then we can use that to shove episodes of TV series' into the week categories as episodes that aired on such and such week. Mmm yes, standards! Let's do it! As you know that's a two-second fix of just changing what outputs from the DPL call. Now, I did put the "Aired on" because if you use the same format as comics, then the TV eps aired on the same day as comics will have lots of friends in that category, not an issue but that's why I added a separate category. Not an issue, but just an FYI. I don't really have a strong vote so whatever you guys want as the standard date format, I can put. If I had to tie break, I'd say Month Day, Year Hatebunny wrote: Third, I made a push a few years ago to try to rename out episode pages to include seasons and episode numbers. This didn't pan out, and I think we're all happier the way it is now. I understand the URL SEO campaigns will be different for all the sites. I hadn't thought of DVD order changes so that's an excellent point! Now having said that, from what I can see this already accommodates for sites to customize their URL name with |PageNameOverride=input from {Series List}. See the documentation dump below for more info on this attribute and a better explanation than my previous paltry attempt. Hatebunny wrote: Fourth, there is a very specific way that episodes have to be filled out, and that series need to be named, in order for category magic to work on the image template and episode template pages. That needs to be kept in mind. I think I get your caution. So in this case the default assumes the {Pagename} Season X Y. Other than that, you can use PageNameOverride for your {Pagename} Episode: {URL} or you can send in the URL with your own link on the attribute. Now when you say "Image Template, I realize I still am using the {Image Comics:Series List} for the DPL. This will be just {Series List} for sites when it's standardized. It has it's value passed in so order shouldn't be an issue for this call that I've tested. Hatebunny wrote: Tupka217 wrote: Don't all those Fetch functions hamper load times? Big disambigs and cover galleries are already giving issues while saving. How would this affect mobile performance?

It would probably hamper load times. I bet it could be done more efficiently in Lua, but we should avoid Lua where possible. It's a fad, as far as I'm concerned. If he imagines it would work in the way that I imagine it would, then the html would still be what we use, it would just be built into the template and filled out with fields and variables instead of writing it right into the html (same as everything else). The major difference being that he wants to use dpl for release dates, which would definitely be a load issue. Yeah the HTML is built into the template. While it is a call, if this works the way I suspect it should, it would be relatively minor as opposed to the image/DPL calls in disambig. In the grand scheme of things, depending on how the DB is structured on the backend, the DPL call is probably the biggest risk for load times with how this is coded, open to your thoughts. The load for that is on the server though so I'm not sure I understand a mobile concern? That would be more about what was spit out, this shouldn't change. To double check, I could switch over Smallville TV Series on the CrossGen site as a good test for this as I think that's the longest running TV series right?

I can surely put more information in the documentation. The jist is this all starts from {Series List}. This would be the same code on Image as on Marvel as on DC and any other TV series wikia that wants to be awesome. The explanation above is just for {Series List}. I tried to explain that there are 4 attributes to drive everything from that template.

I put most of the work in {Episode Build} which is called for each episode. {Series List} will send {Episode Build} the 4 attributes mentioned in the first post above and a few other inputs basically driving out all the data for display. The basics of {Episode Build} are:

Capitalization matters.
 * The first input is the Page Name
 * The second input is the Season Number
 * The third input is the Episode Number
 * The fourth input is the URL name to override. (This was chosen as opposed to DPL in case of override desire and due to performance.)
 * (Optional) The fifth input (AffiliatePage) is the affiliate inter-wiki name
 * (Optional) The sixth input (AffSeasonX_Y) is the URL for the affiliate episode
 * 1) If both are filled in, it will create an affiliate page link in this line: "w:c::"
 * (Optional) The seventh input (PageNameOverride) is for formatting the episode URLs differently.
 * 1) If left blank, this will build the URL as " Season "
 * 2) If "DC" is input, it will use " Episode: ".
 * 3) If "On" is put as value, it will use "".

From {Episode Build}, it uses these templates for making it the table pretty and getting DPL for aired on date. There's really not much to these, most of the work is in episode build if you wanted to understand this. I'm open for improving things coding wise too if you had suggestions but basically:


 * Aired On DPL - This called by each episode to get Date aired based on episode template DPL call
 * DPL call used by {Aired On DPL}. This will be renamed to be simple in the future.
 * Episode Table Beginning - straight html dump, put in template for organization
 * Episode Table Line Column - straight html dump, put in template for organization
 * Episode Table Line - straight html dump, put in template for organization
 * Episode Table Ending - straight html dump, put in template for organization

The outputs are like what was given in the first post. Did that answer your questions? If not, I can get with Billy and setup whatever would make the most sense. I think since everyone is in different countries I can setup a teleconference or google chat meeting if we wanted to walk through anything.