Hi,
Problem: we have a naked wiki, no skins at all, and a set of images for what the wiki should look like. We have no one who knows how to make a skin.
Steps to resolve: create a skin, so that the images can just be copied to the corresponding folders.
Question: how do you make a skin for media wiki? Can an existing one be downloaded from a complete wiki, like a style for a vBulletin forum? Does it require a frontend developer?
Greetings, GIC
Hi,
how do you make a skin for media wiki?
You can create your own skin from scratch: https://www.mediawiki.org/wiki/Manual:Skinning or you can create a copy of an existing skin and modify that to look like the way you want. ( for example https://www.mediawiki.org/wiki/Manual:Skinning/Vector )
Can an existing one be downloaded from a complete wiki, like a style for a vBulletin forum?
You can only use skins created especially for mediawiki. There are a few custom skins for mw on the internet but if I understand correctly then you will need to make your own skin. ( http://www.mediawiki.org/wiki/Manual:Gallery_of_user_styles )
Does it require a frontend developer?
If you are not familiar with css (and maybe javascript or php) then I think yes.
Geri
2013.02.13. 15:14:55 dátumon GIC - Lukas gic-grepolis@gmx.de írta:
Hi,
Problem: we have a naked wiki, no skins at all, and a set of images for what the wiki should look like. We have no one who knows how to make a skin.
Steps to resolve: create a skin, so that the images can just be copied to the corresponding folders.
Question: how do you make a skin for media wiki? Can an existing one be downloaded from a complete wiki, like a style for a vBulletin forum? Does it require a frontend developer?
Greetings, GIC _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
you can install one of the existing skins as described here: https://www.mediawiki.org/wiki/Manual:Skin_configuration
If you want to create your own skin you will need a front-end developer with knowledge of html/css/js and mediawiki skinning. Commercial companies can make the skin for you or you can hire an independent developer. I think that mediawiki-enterprise mailing list is a good place to discuss that: https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
----- Yury Katkov, WikiVote
On Wed, Feb 13, 2013 at 6:14 PM, GIC - Lukas gic-grepolis@gmx.de wrote:
Hi,
Problem: we have a naked wiki, no skins at all, and a set of images for what the wiki should look like. We have no one who knows how to make a skin.
Steps to resolve: create a skin, so that the images can just be copied to the corresponding folders.
Question: how do you make a skin for media wiki? Can an existing one be downloaded from a complete wiki, like a style for a vBulletin forum? Does it require a frontend developer?
Greetings, GIC _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
I upgraded to 1.20.2 and installed the latest "Language Extension Bundle"
I set eh Accept-Header inn my browser to "fr".
By default I see the english version of my page.
If I use the ULS (universal language selector) and set to french I also by default see the english version of my page (but I do see the built-in mediawiki text in french).
I have this set in my http request: Accept-Language fr
I removed the uls-previous-languages cookie and refreshed my page. My authentication is done with a custom extension and it does not set any cookie or setting related to language (and my LocalSettings.php does not set wgDefaultLanguage.
I would like this to happen: 1) accept-language is used for mediwiki text (Im talking about the text rendered by mediawiki not by my content). If not set it defaults to $wgDefaultLanguage 2) accept-language is used to decide which translate page to render.
I dont see how it would make sense to do it any other way - and I assumed that the language bundle would just do things this way. Basically, if a french browser comes to my site, they see the french version of the page - they should not have to select the french link and wait for ye another page refresh.
Regarding point #2:
It seems the "language specific" page is the one with the /<lang> appended in the URL. And this allows a french browser to see the english page. Etc. this is all fine.
but by default, the rendering of the page with no /<lang> appended tot he URL should be based on the accept-language header. But its not.
I even use the "universal language extension" and select "french" and it STILL displays the default page never the french page.
If I fiddle with $wgLanguageCode and $wgDefaultLanguage I can get strange things to happen. I should not have to touch these, the extensions should be doing all this right?
Mike Papper
mediawiki-l@lists.wikimedia.org