I added it because I removed the big fugly logo from the main page, and there should be some label saying it's the "deskthority wiki", not just "deskthority". However, I wanted to do it in the same font, but I'm not sure what font that is (sixty did the logo). So it's a quick fix which should be optimized later.daedalus wrote:Webwit - I don't know about you, but the 'W' in the 'Wiki' on the wiki logo looks very jagged. I think the logo looked nicer without the Wiki underneath it, but that's just my thoughts on it.
The wiki thread
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
-
- Location: Belgium, land of Liberty Wafles and Freedom Fries
- Main keyboard: G80-3K with Clears
- Favorite switch: Capacitative BS
- DT Pro Member: 0049
[ Puts on Mediawiki-wizard hat ]daedalus wrote:7bit - I think there is some way to hide unneeded fields. It's something I will have to look into.
I was talking about {{{#ifeq:}}} before but it turns out that the Infobox template actually already uses it! It looks well-made (I seem to recall you had some trouble grabbing it from the official Mediawiki site), and hiding fields should hence be easy to do simply by making the |datax= setting blank.
Here's an example for infobox dkeyboard with most parameters optional:
Code: Select all
{{ infobox
|above = {{{name|<includeonly>{{title}}</includeonly>}}}
| label1 =Part Number
| data1 ={{{pn|}}}
| label2 = Branding
| data2 ={{{branding|}}}
| label3 = Manufacturer
| data3 = {{{manufacturer|}}}
| label4 =Layouts
| data4 ={{{layouts|}}}
| label5 =Key Switches
| data5 ={{{switch}}}
| label6 =Interface
| data6 ={{{interface}}}
| label7 =Weight
| data7 ={{{weight|}}}
| label8 =Years of Production
| data8 ={{{years|}}}
| label9 =Price
| data9 ={{{price|}}}
|
}}
Obviously, the above only works if the datax parameter contains a parameter with an empty default value. If you want to do stuff like '|data8 = {{{years|}}} years' then if needs more of those {{{#ifeq:}}} logic.
[ Hat off ]
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
- daedalus
- Buckler Of Springs
- Location: Ireland
- Main keyboard: Model M SSK (home) HHKB Pro 2 (work)
- Main mouse: CST Lasertrack, Logitech MX Master
- Favorite switch: Buckling Spring, Beam Spring
- DT Pro Member: 0087
Thanks for that Jbert.
I actually changed my template a bit so that you can set the title of the infobox independently of the title of the page. I've found this useful for some stuff, such as having an article with an official name, and the infobox with the manufacturing designation or whatever.
I actually changed my template a bit so that you can set the title of the infobox independently of the title of the page. I've found this useful for some stuff, such as having an article with an official name, and the infobox with the manufacturing designation or whatever.
-
- Location: Belgium, land of Liberty Wafles and Freedom Fries
- Main keyboard: G80-3K with Clears
- Favorite switch: Capacitative BS
- DT Pro Member: 0049
I didn't change the template yet as I didn't know which parameters were unused in your articles.
Either tell me what data parameters you want to make optional or follow my instructions above.
Either tell me what data parameters you want to make optional or follow my instructions above.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
We have two keyboard model page title styles going, either "Brand/Company Model" or simply "Model". My vote would be for the first style. If we stick to that, various Cherry model pages would need to be renamed, i.e. "G80-5000" should become "Cherry G80-5000".
- 7bit
- Location: Berlin, DE
- Main keyboard: Tipro / IBM 3270 emulator
- Main mouse: Logitech granite for SGI
- Favorite switch: MX Lock
- DT Pro Member: 0001
I've found my G80-2100 more sleek. The shorter the names the less to type.webwit wrote:We have two keyboard model page title styles going, either "Brand/Company Model" or simply "Model". My vote would be for the first style. If we stick to that, various Cherry model pages would need to be renamed, i.e. "G80-5000" should become "Cherry G80-5000".
On the other hand, there could be redirects.
Another advantage: IBMs list under I, Cherrys under C and Key Tronics under K.
In other words:
-
- Location: Germany
- DT Pro Member: -
Hi I'd like your thoughts on a "Terminology Topic/category/article"
not sure yet how to realise it.
It could be done by using a main Category with a subcategory for each term
or one Article with each term sortet alphabetically
Edit: The main priority would be be to give a short basic explanation of each term that could refere to a more elaborate article where necessary/available.
not sure yet how to realise it.
It could be done by using a main Category with a subcategory for each term
or one Article with each term sortet alphabetically
Edit: The main priority would be be to give a short basic explanation of each term that could refere to a more elaborate article where necessary/available.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
Yes, that sounds good. So to rephrase, we need an article with the top terms and a short explanation for each, linking to articles for each term when necessary/available, which are part of a terms category.
- Ascaii
- The Beard
- Location: Berlin, Germany
- Main keyboard: CM Novatouch, g80-1851
- Main mouse: Corsair M65
- Favorite switch: Ergo clears, Topre
- DT Pro Member: 0019
im a complete noob to mediawiki but im eager to learn and have lots of shit to post...someone give me some more rights, cant have enough.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
You have the right to remain silent!
Wait..I'm not doing this right. Motivate, motivate. Let's see, I'm not the wiki expert here, but I think you can do almost anything concerning content by default, it's an open thing, so my guess is it's best to go ahead and see where it brings you. My strategy so far has been to copy wiki codes and structure from other pages, and google for anything I didn't know how to do
Wait..I'm not doing this right. Motivate, motivate. Let's see, I'm not the wiki expert here, but I think you can do almost anything concerning content by default, it's an open thing, so my guess is it's best to go ahead and see where it brings you. My strategy so far has been to copy wiki codes and structure from other pages, and google for anything I didn't know how to do

- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
You go to a non existing page like MyNewPage in the example and click on Create:
http://deskthority.net/wiki/MyNewPage
http://deskthority.net/wiki/MyNewPage
- daedalus
- Buckler Of Springs
- Location: Ireland
- Main keyboard: Model M SSK (home) HHKB Pro 2 (work)
- Main mouse: CST Lasertrack, Logitech MX Master
- Favorite switch: Buckling Spring, Beam Spring
- DT Pro Member: 0087
When uploading images to the Wiki using Opera 11.50, I get an "Invalid MIME Type" error. Seems to work fine with other browsers though.
-
- Location: Belgium, land of Liberty Wafles and Freedom Fries
- Main keyboard: G80-3K with Clears
- Favorite switch: Capacitative BS
- DT Pro Member: 0049
Not sure if trolling or just being silly, but ...
http://en.wikipedia.org/wiki/Wiki#Characteristics
http://en.wikipedia.org/wiki/Wiki#Characteristics
Collaboration only works well if people don't go wild on ownership - hence why "claiming" a page is frowned upon.A wiki is not a carefully crafted site for casual visitors. Instead, it seeks to involve the visitor in an ongoing process of creation and collaboration that constantly changes the Web site landscape.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
I never have a problem finding pictures in the public domain!


-
- Location: Ugly American
- Main keyboard: As Long As It is Helvetica
- Main mouse: Mickey
- Favorite switch: Wanna Switch? Well, I Certainly Did!
- DT Pro Member: -
I'd rather whine about the OCN Mechanical Keyboard Guide and these mythical 3KRO keyboards and PS/2 superiority anyway.Collaboration only works well if people don't go wild on ownership - hence why "claiming" a page is frowned upon.
- daedalus
- Buckler Of Springs
- Location: Ireland
- Main keyboard: Model M SSK (home) HHKB Pro 2 (work)
- Main mouse: CST Lasertrack, Logitech MX Master
- Favorite switch: Buckling Spring, Beam Spring
- DT Pro Member: 0087
As far as I am concerned, I write stuff to inform other people. If I wanted to "own" all that information, I'd shut up and keep it to myself.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
Reminds me of Webwit's 19th Axiom.
Beyond a certain quality level, there's no valuable knowledge on the Internet, because if someone has such knowledge, he or she will write a book about it instead.
Beyond a certain quality level, there's no valuable knowledge on the Internet, because if someone has such knowledge, he or she will write a book about it instead.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
Ah yes, see here:
http://deskthority.net/viewtopic.php?p=15506#p15506
The only workaround for now is to make a new username (just for logging into the wiki) without underscore.
http://deskthority.net/viewtopic.php?p=15506#p15506
The only workaround for now is to make a new username (just for logging into the wiki) without underscore.
- sixty
- Gasbag Guru
- Main keyboard: DKSaver
- Favorite switch: Cherry MX Black
- DT Pro Member: 0060
I fixed a bunch of articles and added pictures here and there. Also wrote a couple of new ones:
http://deskthority.net/wiki/Cherry_G80-0904
http://deskthority.net/wiki/Cherry_G80-3700
I realized we need a lot more redirects and categorizing. For example I set up redirects for stuff like:
double-shot, double shot, doubleshot -> Double-shot Molding article
access is, access -> Access-IS article
Someone should go through common spellings and variants like that and redirect them all to the main article.
http://deskthority.net/wiki/Cherry_G80-0904
http://deskthority.net/wiki/Cherry_G80-3700
I realized we need a lot more redirects and categorizing. For example I set up redirects for stuff like:
double-shot, double shot, doubleshot -> Double-shot Molding article
access is, access -> Access-IS article
Someone should go through common spellings and variants like that and redirect them all to the main article.
-
- Location: Stockholm, Sweden
- DT Pro Member: 0011
The articles around key caps are in need of organization.
The current structure is this:
Article: Keycap construction Very short, and full of opinions.
Article: Keycap printing, with sections for "Pad printing", "Dye sublimation" etc.
Article: Double-shot molding
Category: Keycap Printing Techniques
There is redundancy, and no info about different types of plastics. There is also little and spread-out description of different types of key caps manufacturers and little about different profiles.
How do you think this should be organized?
Should we divide into separate articles about each technique or consolidate into larger documents?
Option 1: Many small articles, with categories
The current structure is this:
Article: Keycap construction Very short, and full of opinions.
Article: Keycap printing, with sections for "Pad printing", "Dye sublimation" etc.
Article: Double-shot molding
Category: Keycap Printing Techniques
There is redundancy, and no info about different types of plastics. There is also little and spread-out description of different types of key caps manufacturers and little about different profiles.
How do you think this should be organized?
Should we divide into separate articles about each technique or consolidate into larger documents?
Option 1: Many small articles, with categories
- Categories for "Keycap plastic" and "Keycap printing technologies"
- "Keycap construction" reconstructed to be an index linking to categories
- "Keycap printing" reconstructed as an alias to "Keycap printing technologies"
- New articles for "ABS", "PBT", "Pad printing",
- Separate articles for "ABS", "PBT", "Double-shot molding", "Pad printing", "Dye sublimation" etc.
- "Keycap construction" reconstructed to be an index linking to articles.
- Merge "Double shot molding" into "Keycap printing". Change article into alias.
- New article "Keycap plastics"
-
- Location: Stockholm, Sweden
- DT Pro Member: 0011
I added an Amiga article. I have got the info mostly from old Geekhack threads and my old mirky memory, and there ought to be errors here and there about the various models.
I have also not added any pictures -- I don't own any of the interesting keyboards, only a yellowed A500 and A1200.
I have also not added any pictures -- I don't own any of the interesting keyboards, only a yellowed A500 and A1200.
- webwit
- Wild Duck
- Location: The Netherlands
- Main keyboard: Model F62
- Favorite switch: IBM beam spring
- DT Pro Member: 0000
- Contact:
Don't worry, I think most of us who got into wiki editing were noobs. A new page is easy, think of the url/title you want it to have and go to that page, for example:
http://deskthority.net/wiki/Blah_Blah
You'll get a blank page. Edit the page.
http://deskthority.net/wiki/Blah_Blah
You'll get a blank page. Edit the page.