Even though a very small percentage of our traffic comes from mobile devices we think that this is in part an issue created by the lack of a well integrated mobile skin for the wiki. So our goal is to create a better mobile experience and make the wiki useful to people who browse it with their various handheld devices.
We are therefore looking for a person who has experience with designing mobile versions of websites using CSS/HTML primarily. Prior experience with the mediawiki platform or php is also beneficial, since you will work with mediawiki skinning. You will be working mostly on your own and will have to come up with solutions to the problems that you might find, the rest of Liquipedia staff will of course assist as well as we can, when we can, but mobile web development is not anything any of us are good at.
This is a non-paid staff position, and there are more web designing tasks to be done after the mobile skin is as good as it can get.
Send your application to liquipedia@teamliquid.net and include:
An introduction about who you are.
At least one work sample of a mobile and desktop site that works for both with the same html.
Previous experience with the mediawiki platform and/or Liquipedia.
How many hours per week you'd be okay to work on the project(s).
Anything else you feel is relevant.
The Liquipedia wikis averages 100 000 visits per day. It is the biggest resource for following competitive StarCraft Brood War, StarCraft II, and Dota 2. Supporting Liquipedia is a great way if you want to give back to the community.
I for one appreciate this a lot. I'm doing tons of browsing forums on the mobile. The experience is solid right now but there's room for improvement. Thanks for taking these steps to make the experience even better.
On March 28 2013 08:56 Carthac wrote: Is Teamliquid on bad times? All you can offer is future unpaid work?
The site has always been based on unpaid work. The reason why this site is so great is because people contribute what they want to and so we have great content.
On March 28 2013 05:42 salle wrote: At least one work sample of a mobile and desktop site that works for both with the same html.
Unfortunately that's really not often the case. Desktop and mobile versions normally have quite different html - structure-wise. The underlying frameworks decides upon http request which version to deliver. I'm curious about a pure css/js solution
Yup, hence why we asked for a sample of it. Because while there are some things we can change from skin to skin, like for example how the sidebar is shown, the main part of a page will still be the same. Hence why we need someone who know how to do it.
On March 28 2013 05:42 salle wrote: At least one work sample of a mobile and desktop site that works for both with the same html.
Unfortunately that's really not often the case. Desktop and mobile versions normally have quite different html - structure-wise. The underlying frameworks decides upon http request which version to deliver. I'm curious about a pure css/js solution
This used to be the case, but you can now use css media queries to target specific resolutions while using one html template. I'm thinking about applying to help but I'm not sure if I will have the right amount of time since liquipedia is a pretty big website.
On March 28 2013 05:42 salle wrote: At least one work sample of a mobile and desktop site that works for both with the same html.
Unfortunately that's really not often the case. Desktop and mobile versions normally have quite different html - structure-wise. The underlying frameworks decides upon http request which version to deliver. I'm curious about a pure css/js solution
This used to be the case, but you can now use css media queries to target specific resolutions while using one html template. I'm thinking about applying to help but I'm not sure if I will have the right amount of time since liquipedia is a pretty big website.
Apply, and don't worry if you have the right amount of time or not.
Very nice opportunity! Though I am to busy programming my own work, i can't really apply for this, but I wish the best of succes/fun to the upcoming programmers.
I actually took a look at the source of the homepage for those interested in using media queries - you will have a lot of work on your hands if this is a pure css project.
A lot of tables/divs do not have ids or even classes. That means you will probably have to use n-th child selectors to find each element starting from very high up. There are a lot of other minor oddities in the page as well. With some javascript, this probably could be fixed (iterating over ever element and assigning ids), but otherwise I don't know what to say if this is a pure front end approach to solving the problem.
I was going to volunteer, and I still might but I kind of am afraid of what I will be signing up for lol.
On March 29 2013 07:16 noveyak wrote: I actually took a look at the source of the homepage for those interested in using media queries - you will have a lot of work on your hands if this is a pure css project.
A lot of tables/divs do not have ids or even classes. That means you will probably have to use n-th child selectors to find each element starting from very high up. There are a lot of other minor oddities in the page as well. With some javascript, this probably could be fixed (iterating over ever element and assigning ids), but otherwise I don't know what to say if this is a pure front end approach to solving the problem.
I was going to volunteer, and I still might but I kind of am afraid of what I will be signing up for lol.
No we can for sure give most of the tables and divs ids and classes, it's just wiki template code, very easy to do.
right also the layout isn't that "advanced" that It would be remade in proper HTML5/Divs to make it work better with media queries in less time then going thru everything and adding classes/ids
On March 28 2013 05:42 salle wrote: At least one work sample of a mobile and desktop site that works for both with the same html.
Unfortunately that's really not often the case. Desktop and mobile versions normally have quite different html - structure-wise. The underlying frameworks decides upon http request which version to deliver. I'm curious about a pure css/js solution
They can defiantely be the same. It's called responsive web design.
On March 28 2013 05:42 salle wrote: At least one work sample of a mobile and desktop site that works for both with the same html.
Unfortunately that's really not often the case. Desktop and mobile versions normally have quite different html - structure-wise. The underlying frameworks decides upon http request which version to deliver. I'm curious about a pure css/js solution
They can defiantely be the same. It's called responsive web design.
I've never said it's not possible. I know it is. But I've been working on different mobile views using jQuery mobile - otherwise I would have already gladly applyed to help out TL
Why would anyone do this for free? And yes, all CSS would be the way to go with this. Anyone who argues this fact really isn't knowledgeable on how requests are sent. Furthermore the difficulty isn't very high, but rather time consuming looking at the source.
On April 04 2013 22:34 StevenWang wrote: Why would anyone do this for free?
I think there are many reasons why people would do this for free but I can only speak about why I've contributed to Liquipedia "for free". I got into esports pretty late, around the beta for Wings, and after a few months I found out about TeamLiquid and soon realized that the whole of TL is essentially built up around volunteers. People write for free, people contribute to Liquipedia for free, people write great regular forum posts that get people appreciate the competitions more, or enjoy being part of the community even more, people volunteer to make regular online tournaments, people volunteered in making good looking graphics for the news posts and the site at large. And realizing this I felt that I wanted to contribute too. To help build this community, make it grow, get more people into it, with a very low threshold of entry—monetarily speaking. If we, as a community, want people to get paid for the things they contribute we need to start to pay more.
I know the applications are closed. But I would like to say to the current developers that making a responsive design on this template is not easy. You should remove all those table structures in the code... Also you don't need Html5, CSS3 only can make a responsive website.
On July 08 2013 03:52 AJ Leadz wrote: Not sure if I am too late on this. I would like to apply. Are you all still looking for some help in this area?
Sorry, but yeah you're way too late. The warning of bumping an old thread could have been indicative of this... but thanks for showing interest in this area. There are other ways that Liquipedia could use help from people that know HTML/CSS though.
EPT
