Difference between revisions of "Talk:Main Page"

From Kolmafia
Jump to navigation Jump to search
(New section: Current wiki layout...)
imported>Fewyn
Line 75: Line 75:
  
 
Just wondering if we could get it centered? :P
 
Just wondering if we could get it centered? :P
 +
 +
 +
What do you mean? And please sign your comments --[[User:Fewyn|Fewyn]] 10:59, 6 December 2007 (PST)

Revision as of 18:59, 6 December 2007

Save these links for now:

Getting started

21895299452399151244860

Wiki layout...

We really should consider exactly how to lay out the wiki... We should probably see how others (especially the KoL wiki) do it and take inspiration... :)

Also, I'm thinking we should eventually have a page for each function, to make searching the wiki more valuable... :)

--Daychilde 23:00, 8 January 2007 (CST)

I agree with your idea about one-page-per-function.

Also I think every* function's documentation should show a real-world example of use. The links to example scripts are a good start in this direction, but some code to read right on the function page would be nice. (*Yes, even the "you are not cool enough to use this" undocumented stuff.)

A master ASH function list page would be helpful. When trying to Find a keyword in browser to see if KM implements a given functionality, it's a minor PITA to have to click into each categorized page and search them all individually.

Also welcome would be some kind of icon, color, or other indicator for newly-added functions. Master list sorted/sortable by implementation version/date if possible.

Also, on the subject of general layout/UI improvements (since you asked): for the main page, I prefer a high-level bulleted-listy index/ToC, kinda like the ToCs on the current sourceforge manual pages. Personally, I find this more useful than the increasingly popular "widgety-portaly-stocks-news-and-weather" look.

Redundancy should be removed wherever possible -- e.g. (ASHRM) in front of every link. I understand if prefixes of that sort are there to assist in organizing the underlying database, but if not, I think they are totally unnecessary and a distraction -- that is, provided the containing page is appropriately identified with a nice big "ASH Reference Manual" heading at the top, breadcrumbs, etc.

I'll quit before I arrive at a frenzy of usability fanaticism the likes of which would make J. Nielsen repent like a dirty sinner. (Got work to do, actually. Now maybe if there was a "job opportunities" section.......)

--User:somebody who sincerely appreciates not having to register/login and probably wouldn't participate elsewise 12:35, 30 January 2007 (EST)

On the other hand, speed-bumping idiot apammers may be worth it. I could go on for ages about how offensive I find that kind of griefing (If you think life isn't a game, you're doing it wrong)--Metraxis 11:27, 18 February 2007 (CST)

Updating?

Let's get started, guys. Soon enough, I'll have a list of all the functions, which I think should go in a wiki page to (as someone above said) search and link. Also, is there a way to do monospacing with code? --MagiNinjA 00:35, 29 March 2007 (CDT)

You can get mono-spaced text by using <code> tags. For example, using
<code>EXAMPLE TEXT</code>
produces this as a result. EXAMPLE TEXT
If you need anymore help, just drop me a line on my talk page. &#151;ksumoe (talk &#149; contrib) 18:35, 10 April 2007 (CDT)

Ideas...

These are my ideas that I have floating around in my head:

  1. A template to put all the relevant information about a function into a table (with proper colored backgrounds and such)
    1. I can do this; I just need to know what information is 'relevant'.
  2. Move this type of discussion to the Community Portal. Right now the CP is just a bunch of links (we can make a 'links' page and add it to the sidebar if needed).
  3. An overhaul of the main page. Someone said that they don't like the 'portal' type of look, but that kind of look has become the de facto standard for wikis, as it is the most popular. I'll pound out a rough draft on a subpage of my user space.
  4. Creation of a template structure. Templates for requesting deletion, protection, etc. That way non-sysop flagged users can 'tag' pages such as this for deletion.
  5. Logo! 'Cause we need to be cool like that.
  6. Define a category structure. Do it now before too many pages get created.

Like I said... I'm here to help. Comments plox. &#151;ksumoe (talk &#149; contrib) 21:17, 13 April 2007 (CDT)

I added some links on the home page -- hope that helps users find more documentation... :) -Daychilde

I corrected the Script Repository link to http://www.kolmafia.us from http://www.kolmafia.ua. ;) -Regnar

Links to Redirects?

While I understand the need for redirect, why are we linking to redirect pages? Why not use [[Page Title|Displayed Text]] links instead?


Protection

Seriously, protect the front page. This is getting completely destroyed by spam 80.189.248.109 12:05, 27 August 2007 (CDT)

Is $wgSpamRegex set? If not it should be. If it is, it needs updating. Spam storming in like the flood! -divinewind420

Articles on the subject http://nothing.tmtm.com/archives/2571 http://wiki.evernex.com/index.php?title=Blocking_Spam_in_Mediawiki -divinewind420

Current wiki layout...

Just wondering if we could get it centered? :P


What do you mean? And please sign your comments --Fewyn 10:59, 6 December 2007 (PST)