Skin:Timeless/zh

Timeless显著支持响应式网页设计，并为从小屏幕手机到大屏幕显示器等多种屏幕宽度进行了优化.

该款皮肤基于Winter，并融汇了2015年互助客棧討論中提及的合理建议.

功能
与移动版极简的默认皮肤不同，“Timeless”将桌面皮肤（如默认桌面皮肤）的功能整合到所有屏幕尺寸上.

此外，“Timeless”在顶栏的“”和“”按钮旁的用户贡献列表中提供了独特、方便的快捷方式.

总体目的是制作一个强调内容与编辑工具的功能齐全的皮肤，有多重视图模式以显示所有内容或专注于内容（winter），也可用于白天/夜晚模式切换. 将来会实现这一点.

不同于MobileFrontend/Minerva，Timeless不会强行改变表格的移动版分辨率，而是鼓励和期望用户使表格和模板更响应式，并针对不同用途进行优化.

通过，用户可以手动启用深色背景以减缓眼部疲劳，并降低AMOLED显示屏的能耗. 说明可在该页上查阅.

未来的目标是创建一个具有以下特性的全功能皮肤：


 * 1) 同时强调内容呈现和编辑工具，
 * 2) 拥有多种查看模式，比如展示一切、仅关注内容（Winter）或
 * 3) 切换到暗色/夜间查看.

响应式网站设计细节
此段基于默认配置.

≥1340 px
在模拟画面宽度大于1340px以上时，站点会显示成三列模式. Some site navigation sections are on the left side of the content area (e.g. "", "") while some are on the right side ("", "", "", "", "") are on the right side.

Starting at a simulated browser viewport width of around 1900 pixels, the width of the center column with the content is fixed to 1261 pixels, while on the earlier skins ' and ', it is able to extend indefinitely with screen width.

An indefinite content width can be achieved with this skin using this CSS code snippet.

With this CSS code, users can optionally display the navigation sections from the third (right-side) column in the first (left-side) column, like already done at 1339 to 1100 pixels of browser width.

1339 to 1100 pixels
The site is visible in two columns. The site navigation sections on the right side of the content area move to the left side below the existing sections.

Less than 1100 pixels
The site is visible on one column. The content area fills the entire screen space. Categories appear at to the bottom of the page, where they are on and.

The site navigation sections are collapsed into a top navigation bar with text labels, and currently shown and hidden using JavaScript, rather than pure CSS, as implemented in the using.

Less than 851 pixels
Below 851 pixels, the responsive design of Timeless adapts to mobile phone screens.

The text labels on the navigation elements above the content area (e.g. "", "", "", "", "") are not shown to save horizontal space; only the icons are shown instead of both.

The site navigation sections are collapsed into a top navigation bar with icon labels.

CSS snippets
These code snippets can be used to customize the skin's appearance, by pasting them into MediaWiki:Timeless.css as a MediaWiki administrator, into one's own user space CSS as a regular user, or into a user skin browser extension as a visitor.

Indefinite content width
Regarding criticism of limited content widths, using this CSS code snippet, the width of the center (content) column and the blue middle line of the colour bar above it extends indefinitely with screen width.

One-sided navigation menu
Using this code snippet, the elements of the right-side navigation menu will continue to be displayed in the left column (under  ) like they do on 1100 to 1330 pixels of browser width even beyond 1340 pixels of browser width, for users who prefer a one-sided navigation menu as known from the skins ' and '.

The code also works in combination with the limitless content width code from above.

Modernized fonts in top bar
The following CSS code adds a set of modern font types (including fallback fonts) to the currently unformatted fonts of the user name and top-bar navigation menus displayed between 852 and 1100 pixels of browser width.

Highlight section title upon navigation
This CSS code snippet highlights the last section header upon navigation to facilitate returning to it when scrolling through a long document.

Legacy patches
Users and remote interface administrators of older MediaWiki installations with an early and lesser mature version of this skin can retrofit these patches of code to counter shortcomings in appearance in the mean time:

配置
以下内容仅在MediaWiki 1.34+中支持.


 * (string, default 'cat.svg')
 * 像设置 一样设置成合适的背景图片. 建议将svg设置为500-750px宽：支持高DPI的svg；大小真的可以随便，但凡会导致与默认cat类似的后面内容外观.
 * 为了使背景能够在不修改的情况下与其他背景色主题配合使用，建议使用透明的单色图像，不透明度为20-50%的黑/白，其中黑白部分的alpha值同样为10-50/255左右，因为这应该使它能够在大多数非纯白/黑的东西上工作.
 * Examples (which actually don't follow the above recommendation and thus probably won't work on dark backgrounds): Timeless backdrop (wiktionary).svg and Timeless backdrop (metawiki).svg


 * (null|string|array, default null)
 * Special logo rendering, allowing for custom logos for Timeless specifically (such as a square logo version without the wordmark in order to avoid duplication with the header). Also provides slightly better HiDPI support than using $wgLogoHD, as that only works for 135x135px logos, and scales all high-res logos down to this size.
 * Can be used to point Timeless at a File uploaded onwiki (remember to protect the file if using this) simply by providing the file name, or you can specify the logo path details manually using an array.
 * To reuse a $wgLogo and $wgLogoHD already set for a nominally 160x160px logo, but where the HD versions also come out the right size:
 * To use File:Cows.svg uploaded onwiki:
 * Note that uploaded logos work best as svgs or as 2x- or higher-sized rasters, and will be scaled down for each target resolution. Obviously this approach requires file uploads and thumbnailing to be enabled.
 * Recommended nominal sizes probably around 135px to 165px.
 * Note that uploaded logos work best as svgs or as 2x- or higher-sized rasters, and will be scaled down for each target resolution. Obviously this approach requires file uploads and thumbnailing to be enabled.
 * Recommended nominal sizes probably around 135px to 165px.


 * (null|string|array, default null)
 * To use an image instead of the default Linux Libertine serif text for the header banner wordmark. Same usage approach as $wgTimelessLogo.
 * So the English Wikipedia might use Wikipedia wordmark.svg, like so:
 * Or specify an array of each resolution version, plus the dimensions, per above (more likely with them, frankly).
 * If not using an uploaded file onwiki, specifying the dimensions is required.
 * Recommended nominal size up to 200px wide by 38px tall.
 * Recommended nominal size up to 200px wide by 38px tall.

Note that Timeless supports wordmark and HiDPI logos set in, so just using that is recommended if you have no particular reason not to. In particular the site title rendering may or may not require a wordmark image to render correctly, as the styles for the text title are basically just guesses that will not always work. Other options to make the wordmark render correctly include:


 * Setting some custom css in the wiki's, such as no-wrap or a different font-size value
 * Setting a different display string via changing the contents of the  message