Mobile Gateway/Mobile homepage formatting/zh

如果您的维基百科项目首页（主页）中尚未开启移动版视图，且您是该项目的管理员，请参照后面的说明开启.

请注意：您必须具有管理员权限才能编辑首页.

第一步
首先，确定哪些内容适合移动版首页.

评估桌面版的页面元素（如“每日图片”）并询问：


 * 它们受欢迎吗？
 * 它们正常更新吗？
 * 它们适合快速阅读吗？
 * 它们在移动屏幕上阅读舒适吗？

当您选择好了需要的元素，请继续第二步.

第二步
您必须具有管理权限且登录后才能进行以下操作. 在首页的桌面版视图中，点击 "" 并找到要在移动版中显示的元素.

所有您希望從頁面上排除的元素都需要給予「nomobile」類別或包在含有此類別的元素內.



在 div 的开标签和闭标签之间应放什么呢？大多数时候应是页面元素的模板，例如“每日图片”.

更新樣式
Certain styles are not mobile friendly. For example any css rules which make use of fixed pixel size e.g. width, height, padding. If different style treatment is needed please use the Extension:TemplateStyles or port these styles to MediaWiki:Common.css or MediaWiki:Mobile.css.

Some tips on common problems are addressed @ Making MediaWiki Mobile Friendly.

点击“”.

到这里几乎完成了.

第三步
现在打开移动版网址，通常是languagecode.m.project.org. 您可以减小桌面浏览器的宽度模拟移动屏幕，现在页面看起来如何？

如果您要调整，请回到第二步，并在它与第三步之间循环直到满意.

结束了！

MFSpecialCaseMainPage
When $wgMFSpecialCaseMainPage is enabled (which is disabled by default), it is possible to serve different content to mobile and desktop users. Use of this method is discouraged and deprecated as it only works on the Main Page, is a maintenance burden and should only be used as a stop-gap measure when transitioning your MediaWiki site to a mobile experience. 它將在2020年移除.

维基百科各种语言版以及其他所有维基媒体计划的首页是多样化的，所以无法展示统一的例子. 尽管如此，还是可以通过例子想象一下您的站点看起来会如何，下面是维基百科的德语版： https://de.wikipedia.org/ 如果您点击“Lesen”旁的查看源代码（“Quelltext anzeigen”）选项卡，您可以看到维基格式的文本，接着使用浏览器的查找功能搜索“mf-”.

在这里，mf 选择器的 div 标签是更大页面对象的一部分. 只有熟悉该项目主页格式的人才能理解它的确切含义.

现在打开： https://de.m.wikipedia.org/

最终的移动版页面出现了，与 mf 选择器对应的章节内容展示在移动版视图中.

Deprecation steps for wikis using MFSpecialCaseMainPage
MobileFrontend is in the process of deprecating the code relating to main page special casing. If you have a wiki using it you'll want to stop using it immediately. If you have any questions please don't hesitate to use the talk page!

How can I tell if I'm using it?
For projects you are users of please apply the query string " " to your main page on mobile and compare it with the main page without the query. For example users of English Wikipedia can compare https://en.m.wikipedia.org/?mfnolegacytransform=1&debug=1 with https://en.m.wikipedia.org/. If the two pages look different you must migrate ASAP.

What can I do to fix this?
Assuming you do not want to do a big redesign and just want to retain the existing main page design, you can follow this guide.

Copy the main page markup into a sandbox e.g. a sub page of the user namespace. Now switch to mobile mode. Note, the mobile site can be viewed in your desktop browser, so if you can you may want to consider using the wikitext editor of the mobile site.

You'll need the TemplateStyles extension deployed on your wiki. You can see if it's installed on your wiki by visiting Special:Version. If it's not for whatever reason please request it.

To add template styles to a page add the following line to the top of your new draft page:

You can now add CSS @media queries to your page by adding CSS inside Template:Main Page/styles.css to display different content to different device resolutions.

You can apply the "nomobile" class to any elements you wish to continue to hide on mobile. In some cases use of this class is the most straightforward way to update your page.

Known problems are listed below:

1. Stop using tables

If your main page uses table's in any way, please remove them. There are many tutorials on the web for doing column layouts. Please put "responsive column layout" into your favorite search engine. If this is confusing, you'll probably want to seek help from a CSS expert!

DivTable converter provides a way for you to convert a table HTML to divs. You should aim to put the associated CSS in MediaWiki:Common.css. This act alone should improve your rendering in mobile greatly.

2. Review any inline styles

Search for any instances of styles which make use of the css properties " ", " ", " " or " "

For example:

Move these into a TemplateStyle. Use a class and move the css declaration to css.

Example CSS:

e.g. Example - note the pre tag is only included for example purposes - this should be put into a TemplateStyle.

3. Reskin for mobile

With the above steps applied your page should look no different on a desktop browser, but as you shrink the screen (horizontal width) to under 720px - the threshold you introduced in step 2 the styles should disappear. You'll want to add new styles (outside the media query you introduced in step 3). These styles will apply to mobile devices and will be overridden.

If there is any content in the page that you do not want to render in the mobile skin you should add the class "nomobile". e.g.

4. Apply the new template

Copy and paste the sandbox page into your Main page. Refresh the browser and verify that it works as expected on both mobile and desktop.

5. Make a site request to turn off main page special casing

If your site is now no longer using the special page casing and your site appears in this config:

You'll want to let a Wikimedia site admin know that you are ready for main page special casing to be turned off. File a Phabricator ticket using this link that links to this web page and lists your wiki.

You'll be able to tell when this has been successful if you've been using the  prefixes as suddenly other content will display on your mobile site!

6. Remove any mobile specific ids.

i.e. any instance of the following:

These are not necessary any more. Previously these would choose which content to show on mobile, but now you have a new mobile first responsive design and have disabled main they will be ignored.

e.g. This example

Quick fix
The quickest possible fix for your wiki might be to fix the design for Minerva only by forcing horizontally stacking at the trade off of impacting the small amount of desktop Minerva users. To see if the quick fix works for you add the following to your Main Page:

and then inside Template:Main_Page/styles.css copy paste the following CSS:

Please be aware that this is a quick and dirty fix, which may break more complex main pages (e.g. ones that use tables within tables), and it also doesn’t improve the current situation where the main page breaks on smaller desktop screens and wastes much space on larger mobile ones. If you really don’t have time, you can use this temporarily, but you should plan to really fix the mobile (and small-screen desktop) experience using the above size-dependent methods (or completely redesign the main page, of course). If you decide to go this way, you should make sure to test the resulting main page using mobile view.