I think we may have access to Category JSON in there somewhere. I'm hoping to get access to enable easy page navigation controls.
What's on your mind?
While the hero page design is in an alright spot, I feel it could be better. Specifically, the SkillDesign placement and usage is in question. I'd like to make it more compact and more organized. I'm also still on the fence regarding where the Transcendence info should go and how the Unique Weapon info should be displayed.
The other wiki isolates all this info per object type. That isn't very context sensitive. T3 and T4 are skill-based perks. I'll mull over this later.
It might be fun to play with Lua over winter break as well. It may be fairly powerful when combined with functions to allow more dynamically generated pages. This would be advantageous for matrix pages.
this week has been very busy for me. I've barely had time to play the game. I've plans this weekend as well. Even so, I plan on hitting this wiki pretty hard. I'll also have lots of free time next week.
I feel I can finish all the hero pages this weekend to the extent of the data I have access to.
For next week, move my attention to polishing the Hero page design and moving on to other objects like the boss info, T1 and T2 info, matrix pages, etc. Once I've admin access I'll cleanup the design and landing page. Some of that work can be done before I've admin access of course. After that I'll advertise the wiki.
so... last night i was looking for alternative ways to obtain all the string info for the game objects. I'm not sure it's possible. Sigh... I may mess with it later to make sure. For now I'm just gunna have to do this manually... ick.
Anyhoo, tonight I'll start creating the wiki data objects in mass for the heroes. I expect it to take about 20-25min per hero, not including the image. I'll do images later. For images, I'll likely followup on what my predecessor was doing and collect the "framed" 2D image of each hero as well as their portrait. I'm not sure what resolution they should be, but will deal with that later.
For the data objects I expect to get done about six per night. There are about 40 heroes so it may take as long as a week. The HeroDesign implementation on the Hero page is super simple so I'll throw those up too at the end of every night.
Once it's all done I'll prolly toss up a secondary nav object on the landing page for the Heroes.
I'm at a pretty good spot with the Hero page design. I've considered the HashTable extension and the Lua extensions. I don't feel the need to move over to either right now. I feel my data setup is generic enough to be ported over to either if there are issues.
Now I'm going to start creating the Hero Data templates on mass. I'm hoping to be done with that in two weeks. I may also futz with the landing page a bit today.
I'm pretty happy where the hero page design is am about ready to move on. There's one last thing I'd like to check. I'm currently just using a switch function to store all my object data. It might be more efficient to use a hashtable as defined here
After which I would like to start populating the existing Hero pages with the same style. Then I could add all the new heroes and populate their pages. I could then add a temporary navigation control onto the landing page for hero navigation since I don't have access to the site's admin functions.
I'm still debating on how I'd like to represent Hero skills and transcendence perks. Is it too much to put all the skill info into Infoboxes? What about the trans info? What other options are there? Tables aren't highly regarded in wikis. They don't often translate well to mobile.
I will likely use a design object template for the hero pages and next the HeroInfobox (and SkillInfoboxes) inside it. I think it's a good idea for all content to go within those HeroDesign template implementations to allow our Hero pages to be uniform.
Looking around for good examples on how to construct wiki pages I found borderlands.wikia.com. It has good examples on how to use variables and nested templates. I can also tell the dev gave a good amount of thought to the construction.
1. Finish HeroInfobox template: There requires deleting all the skill info and adding any of the basic data left. I think it's pretty much done. All stats data is tied to the hero type (ie assassin, warrior, etc). We'll have separate hero type pages for those base stats. Don't worry about the images either yet. We'll do that later.
2. Create a SkillInfobox template: This basic template structure for this is mainly complet on the HeroInfobox. We need to split it off into its own Infobox and test how three of them will look on the Hero's page. I think it will work out okay.
3. Decide how to handle T3-T5: I'm not 100% certain whether T3 and T4 should be in the SkillInfobox or if they should be separate. If not, then perhaps we'll create a TranscendanceInfobox for each trancendance level.
4. Finish the PoC on the Epis page: This just means we'll be using the Epis page as a starting point. Clean it up of all all the old templates and make it work first.
5. Apply the final Hero page design to the other Hero pages.
6. Throw up some quick KR graphics on the splash page: I'm not certain I've full rights to do this yet. I just want it to look a bit nicer and more inviting than it does now.
- kingsraid.wikia.com/wiki/Special:ThemeDesigner (this requires admin permission)
7. Start populating data: I expect this will take at least a week to finish, so let's do this in parallel with continuing to flesh out and clean up the site.
If we do it this way for the Hero pages we'll have seven infoboxes stacked up on top of each other. I think this is okay, but I'm new here. In the end we want to make sure our pages can easily be consumed by both a desktop and mobile platform.
I'll start on all this after work tonight.
I've run out of time to work on this tonight. However, toying with the HeroInfobox template I came to a conclusion on a better way to organize the. The skills should be separate of the Hero infobox. In fact there should be a infobox just for skills. Hence, on each hero page we'd define three Skill infoboxes. Doing this will allow us to continue using simple names for the labels.
As for the transcendence perks, I haven't quite decided. I assume another infobox for that. Is it worth merging in the T3 and T4 data into the skill infobox? Hmmm... Context-wise it make sense.
Also, once we have the T1 and T2 templates we could perhaps just have them load on each page as pre-defined data. I'm not sure which object type would be best for that.
allows you to manage everything about the wiki
I'm familiarizing myself with the wikia tools. Looking around our wiki I see the original dev put a lot of effort into several templates. You can browse them here:
We'll want to evaluate them before continuing to use them. For instance, that Infobox_Character template is has more info than we probably need.
Also, regarding heroes or any entity that will require multiple pages, we'll want to create a viable page first with one hero and then use that page as a "template" to create all the others from rather than creating a bunch of empty pages.
The original contributor to this wiki put in some good work earlier this year. He stopped contributing, but left a decent start.
I plan on dedicating some of my time to contributing. I feel this is a better URL than kingsraid-en.wikia.com and it already has more of a skeleton in place.
A few things to consider. First, I'm new to editing public wikis. Second, we should use other, similar wikis as references (like Summoner's War). Third, the information here should be easy to consume. That includes making pages consumable via mobile.
I feel the first priority should be the hero stats. Each hero needs their own page with stats, skill descriptions, and unique weapons. I think we'd also eventually benefit from skill and trans listings to allow people to quickly search them and compare.
Second in priority would probably be artifacts and runes.
Third is basic game info such as locations, NPCs, game mechanics, boss fights, lore/story, and guides.
Fourth would be tracking KR Plug, KR notices/events, and KR patches.
I'm going to assume we can freely use KR's artwork. We'll certainly one to dress the wiki up a bit.