Template talk:Alaska Airlines

__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Arsenikk-2009-10-28T12:01:00.000Z","type":"heading","level":0,"id":"h-Scope-2009-10-28T12:01:00.000Z","replies":["c-Arsenikk-2009-10-28T12:01:00.000Z-Scope"],"text":"Scope","linkableTitle":"Scope"}-->

Scope

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Arsenikk-2009-10-28T12:01:00.000Z","type":"heading","level":0,"id":"h-Scope-2009-10-28T12:01:00.000Z","replies":["c-Arsenikk-2009-10-28T12:01:00.000Z-Scope"]}}-->
__DTLATESTCOMMENTTHREAD__{"id":"c-Arsenikk-2009-10-28T12:01:00.000Z-Scope","timestamp":"2009-10-28T12:01:00.000Z"}__-->__DTCOMMENTCOUNT__1__-->__DTAUTHORCOUNT__1__-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Arsenikk-2009-10-28T12:01:00.000Z","type":"heading","level":0,"id":"h-Scope-2009-10-28T12:01:00.000Z","replies":["c-Arsenikk-2009-10-28T12:01:00.000Z-Scope"],"text":"Scope","linkableTitle":"Scope"}-->

I fear this navbox is far more elaborate than outlined at Wikipedia:Categories, lists, and navigation templates. It seems this template is more about navigating within the Alaska Airline article, than between related articles. I have several concerns:

  • The template uses a huge amount of space, while providing very little information
  • The complexity of the template makes it very difficult to find relevant information
  • Links are repeated
  • It is not normal to link every word in the navbox, and there are some horrendous examples here, such as "pre", "post" (a disambiguate page), "flotilla" (that talks about watercraft), "location" etc.
  • I don't know how many links there are to "cheatline", but there should be exactly zero.
  • The infobox is misleading (although not directly lying) since it doesn't mention accidents, and makes a claim about there being none, when there have been many accidents and there are even articles on two of them.
  • The use of tiny (virtually unseeable) pictures of every special livery is not suitable for a navbox.
  • To include an article in a navbox, the topic of the navbox should be a defining aspect of the article. For instance, Alaska Airlines is part of "airlines of the United States", because that is a defining aspect of Alaska Airlines. However, it is not a defining aspect of a particular aircraft that is has been or is used by Alaska Airlines or Horizon Air. Imagine if a navbox for every 737-operator was stuck on the B737 article.
  • The use of IATA codes for airlines and airports is very alienating for people who are not aviation geeks. After all, Wikipedia is written in eye of the person with little knowledge on the subject, and they may not even understand that the two- and three-letter codes are for airlines, and I think no-one knows the IATA codes for all of the airlines and airports in question.
  • As far as I can count, there are only the following useful and relevant links in the navbox: Alaska Air Group, Alaska Airline, Horizon Air, Alaska Coastal Airlines, Barnhill & McGee Airways, McGee Airways, Star Air Service, Jet America Airlines, Air Oregon, Transwestern Airlines, Alaska Airline destinations and Horizon Air destinations. Two important articles are left out: Alaska Airlines Flight 261 and Alaska Airlines Flight 1866. That would leave four groups: current companies (3), heritage companies (7), destinations (2) and accidents and incidents (2). Arsenikk (talk) 12:01, 28 October 2009 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2009-10-28T12:01:00.000Z","author":"Arsenikk","type":"comment","level":1,"id":"c-Arsenikk-2009-10-28T12:01:00.000Z-Scope","replies":[]}}-->
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-Smallman12q-2010-10-25T16:22:00.000Z","type":"heading","level":0,"id":"h-Flight_536-2010-10-25T16:22:00.000Z","replies":["c-Smallman12q-2010-10-25T16:22:00.000Z-Flight_536","c-WilliamJE-2010-10-25T16:41:00.000Z-Flight_536"],"text":"Flight 536","linkableTitle":"Flight 536"}-->

Flight 536

__DTELLIPSISBUTTON__{"threadItem":{"headingLevel":2,"name":"h-Smallman12q-2010-10-25T16:22:00.000Z","type":"heading","level":0,"id":"h-Flight_536-2010-10-25T16:22:00.000Z","replies":["c-Smallman12q-2010-10-25T16:22:00.000Z-Flight_536","c-WilliamJE-2010-10-25T16:41:00.000Z-Flight_536"]}}-->
__DTLATESTCOMMENTTHREAD__{"id":"c-WilliamJE-2010-10-25T16:41:00.000Z-Flight_536","timestamp":"2010-10-25T16:41:00.000Z"}__-->__DTCOMMENTCOUNT__2__-->__DTAUTHORCOUNT__2__-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-Smallman12q-2010-10-25T16:22:00.000Z","type":"heading","level":0,"id":"h-Flight_536-2010-10-25T16:22:00.000Z","replies":["c-Smallman12q-2010-10-25T16:22:00.000Z-Flight_536","c-WilliamJE-2010-10-25T16:41:00.000Z-Flight_536"],"text":"Flight 536","linkableTitle":"Flight 536"}-->

Articles relating to flight 536 if anyone wants to create an article:

Smallman12q (talk) 16:22, 25 October 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-10-25T16:22:00.000Z","author":"Smallman12q","type":"comment","level":1,"id":"c-Smallman12q-2010-10-25T16:22:00.000Z-Flight_536","replies":[]}}-->

Flight 536 incident did occur and I discovered it after my 10-24 edit was done but if you go here

http://en.wikipedia.org/w/index.php?title=Alaska_Airlines_Flight_536

You'll find out the wikipedia article on this incident was deleted because the incident was considered non notable. The article doesn't exist, the previous version of it was not deemed worthy of an article, therefore the template shouldn't have an entry.- William 16:41, 25 October 2010 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2010-10-25T16:41:00.000Z","author":"WilliamJE","type":"comment","level":1,"id":"c-WilliamJE-2010-10-25T16:41:00.000Z-Flight_536","replies":[],"displayName":"William"}}-->

Strategi Solo vs Squad di Free Fire: Cara Menang Mudah!