社区中心

欢迎来到社区中心!欢迎查看中文区及中文社区中心的公告
歡迎來到社群中心!歡迎查看中文區及中文社群中心的公告

了解更多

社区中心
Advertisement

正在翻译的页面

本页面尚未翻译完成,欢迎使用者协助翻译。更多正在翻译的页面

随着我们不断将平台上的社区迁移到全新的统一社区体验 (UCX),若想知道您的社区会变成甚么样子,您现在已经得到了设计与测试的机会

对于大多数人来说,除了 wiki 的基本主题与颜色样式,还会有其他需要测试与重新设计的元素。调整后的 wiki 外观通常可以超越预设外观,使客制化深入契合所及领域。

正如我们会解释的那样,随着 UCX 的推出,我们今天也要推出更新的客制化原则,规定您如何客制化社区,以及可以客制化甚么。基于你们对上一个版本的客制化原则的回馈,我们相信有一些区域可以提供更开放的原则。无论如何,我们还是必须设计一些一成不变、黑白分明的规则。请继续阅读,深入了解。

权衡轻重[]

客制化与社区辨别度向来都是 Fandom 体验的核心。所以,为了让使用者进一步客制化,Fandom 开发了 UCX。在我们不断地对“预设”外观测试、探索,并如此循环往复的时候,我们还考察了高度客制化的社区,尝试去理解使用者建立的客制化额外图层会怎样影响最终外观。

客制化固然重要,但是必须制定逻辑限制甚么可以发生,甚么不可以发生。随着人们从一个社区去往另一个社区,在从读者到编辑者再到创办者的道路上前进,重要的是他们能将从一个 wiki 上学到的,用于建设另一个。这次学到的重要经验是,要让使用者界面与功能一致,要让访客能够依赖于界面,即浏览 Fandom 时,功能都放在垂手可得的地方。

于是我们制定了下方的“客制化原则”用于权衡两个方面:一方面是客制化与创新表达,另一方面是一致性与可用性。特别是,新版本的客制化原则将非常注重社群的可用性。而相较于这个原则的先前版本,我们正在允许修改设计的更多部分,我们会更积极的确保不同技术水平及身体能力水平的读者能够使用您的社区。

基本方针[]

只因为您“可以”做不意味著您“应该”做。在页面下面的内容中列出了一些我们允许和不允许的指定事项,在近一步客制化之前,再三考虑一下总是个好主意。

  1. 主题设计器 - We’ve built a lot of customization options into our Theme Designer tool. It’s designed to allow you to quickly and easily make changes to your design without having to mess with complicated CSS/JS code. It’s best to use a tool purpose-made for site design rather than having to configure the code manually, which could have unexpected consequences.
  2. Discuss changes with your community. - It’s always important to ensure your community is on board with a site design change. What looks good to you may look bad to others. It’s also important to consider if the proposed change solves a problem or limitation with your current design. If it doesn’t, is the change actually necessary?
  3. Consider usability. Critically, remember there are individuals that use your site that may have physical limitations that could make a customization detrimental to their reading or editing experience. Avoid a reliance on color coding to be inclusive of colorblind individuals. Make sure any custom fonts or font-sizes can be read by those with poor eyesight - test on a screen reader when possible. And opacity can be taxing on even those who have normal vision.
  4. Consider screen sizes. Remember that the UCX desktop design has a fluid width, so how a customization appears on your screen may look different on others. This is especially true if you have a larger-than-average monitor. Hardcoding a CSS change to space things out a certain way on your screen may unexpectedly compress or distort the viewing experience for other users.
  5. Consider performance. It’s also important to consider the CSS & JS files take up computational and rendering time, especially if you are loading up an image. Poor speeds can hurt your SEO. It can also affect users with lower-bandwidth connections. If you must load images using CSS or JS, make sure they are as small and compressed as possible.

What Is & Is Not Permitted[]

It is important to note that all the following policies apply to site-level JavaScript & CSS (i.e. code stored on your wiki’s MediaWiki namespace). You may continue to use your personal JavaScript/CSS however you would like as long as it does not affect any other user. Also please note that, as noted in a previous section, if a customization makes a part of the community unusable, regardless of what “area” that customization affects, we will ask you to modify or remove it.

Noteworthy changes from the previous customization policy are italicized.

页面内容区域 - Communities may customize the content area of their community (that is to say the area of the page where user-submitted content is displayed) as desired.

Basic Interface Elements & Advertisements - The user interface and advertisements are the basic, expected functions of the site, and must remain in place. For example, a visitor should always see the “Edit” button or the "Recent Changes" button in the same place, and it should work as they expect. Additionally, custom cursors are not permitted. Some features are optional, but these should be managed via the settings or with staff help, rather than being removed via CSS. This helps us to track the features and get accurate data on how they are being used across Fandom.

网站背景图片 - The complete background of the page may be modified using CSS to override or complement the “page header”-type image. Other changes to the background may not force the site to be rendered in a certain width or otherwise modify the fluidity of the layout.

全域导航栏 - We consider this a core element of the site due to both its value to cross-wiki discovery and as the entry point to the user’s personalized experience. As such, the left hand global navigation bar may not be altered, repositioned, obscured, or otherwise affected in any way.

本地导航栏 - Additional top-level menus may not be added to the local navigation beyond the functionality allowed through the navigation tool. Additional items on all other child menus may be appended as necessary.

页面各级标题 - The page header may be modified through the use of properly licensed fonts. However, Fandom staff will be particularly proactive in addressing any issues that negatively impact the usability of this part of the page and will ask you to change it if we deem it unusable.

右侧栏(Right Rail) - Additional elements and modules are allowed to be placed in the right rail, below the default elements. However, they may not push down the placement of the advertisement module in that space.


想要掌握Fandom的最新功能与新闻动态吗?
点击这里关注Fandom网志。
想要与编辑者和职员取得即时通讯吗?
加入我们为已注册编辑者开放的官方Discord伺服器吧!
想要与中文社群的编辑者取得即时通讯吗?
加入中文社区中心团队运营的交流群吧!
Advertisement