GithubHelp home page GithubHelp logo

lod-wiki's Introduction

LoD-Wiki

Wiki for the videogame Legend of Dragoon

lod-wiki's People

Contributors

drewuniverse avatar

Watchers

Corey Frenette avatar  avatar

lod-wiki's Issues

Better Templates & Automation

Investigation for how to create better templates, and thus automation.

Originally, I created templates that acted as "starter skeletons". New articles that fit a category, like Locations or Player Characters, would be injected with this template to place all the layout framework, allowing editors to focus on actual content instead of wrestling with layout code.

However, every time we find a way to improve the layout, we then manually have to update every location article to match. There are also a few cases were editors altered the layout without making suggestions to change the style guide. I'm wondering if there's a way we can make layouts more automated, in such a way that we just change the "core" layout in a template and have that reflect automatically on every location article.

We really need to keep the layout synchronized between any two location articles, boss articles, and so on.

How to investigate: Google search, and checking the MediaWiki knowledgebase directly.

Proposal to Remove Subgroups: Accessories, Armor, and Weapons

We have a few options for how to approach equipment groupings. The article Equipment will exist either way, but the question is whether we also erect subgroupings for Accessories, Weapons, and Armor. The idea would be that these sub-groupings go into a little more detail than would be present on Equipment. I think we have two of these sub-groupings already set up.

At present, these sub-grouping articles are just copies of everything on Equipment, and there's not much to add to make them worth the separate articles. That means it wouldn't make the Equipment article too much longer to keep it all there. Second, where would a piece of equipment link back to? Equipment, or one of the sub-groupings? I feel this may cause some navigational frustration.

I think we should consider removing the sub-groupings. It'd simplify where we link equipment pieces back to, we can collapse tables by default if necessary, and we'll only have to manage one set of data for all that gear. If there are still valid uses of Weapons, Armor, and Accessories, they can merely be linked to anchors within Equipment.

Articles for Specific Equipment - Set Up Redirects

There are a few existing articles for specific equipment, that need to be turned into a redirect. We will also need to set up redirects for all remaining pieces of equipment. I don't think we ever explored how to do this, so it's an investigation that looks at MediaWiki's documentation.

This topic is dormant until we decide what to do about the sub-groupings dilemma (issue #20)

Articles for Items - Set Up Redirects

There are about ten Item articles, like Healing Potion, that need to be turned into a redirect. We will also need to set up redirects for all remaining items. I don't think we ever explored how to do this, so it's an investigation that looks at MediaWiki's documentation.

Update MediaWiki Version

Our MediaWiki version is out of date. To determine exactly which release to upgrade to, our current version must be checked. Secondly, there are specific PHP requirements that slowly increase with major releases, so Drew will need to check what version of PHP is possible on our web server before we commit to a specific new release.

General Upgrade Guide

Tasks

  • Check Current Version
  • Check Requirements of Latest Version as well as latest LTS release, and choose one. Most likely the LTS
  • Verify that our web server supports the PHP version requirements of the chosen release
  • Complete the backup process
  • Complete the upgrade process on our test site
  • Verify test site is functioning completely (new articles, edits, accounts, etc.)
  • Proceed with upgrading the live wiki site
  • Verify life site is functioning properly

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.