FANDOM


(创建或更新的博客。)
(Fix a typo)
第71行: 第71行:
 
* 在这过程中,脚本会检查wiki内容的结构,让它看起来像全新的UCP wiki一样(但wiki内容丶编辑历史等会保留)
 
* 在这过程中,脚本会检查wiki内容的结构,让它看起来像全新的UCP wiki一样(但wiki内容丶编辑历史等会保留)
 
* 在新平台上会针对wiki的关键页面发出多项请求来检查错误,像是内容显示不正确丶数据库异常等等。
 
* 在新平台上会针对wiki的关键页面发出多项请求来检查错误,像是内容显示不正确丶数据库异常等等。
* 最後wiki的网域会连到UCP的版本,并解除wiki的唯状态
+
* 最後wiki的网域会连到UCP的版本,并解除wiki的唯状态
   
 
We will have alerts set for error spikes after your wiki transitions to the new platform and, if something goes wrong that cannot be fixed quickly, we’ll be able to revert your wiki back to the legacy platform.
 
We will have alerts set for error spikes after your wiki transitions to the new platform and, if something goes wrong that cannot be fixed quickly, we’ll be able to revert your wiki back to the legacy platform.

2020年6月1日 (一) 15:19的版本

本頁使用了標題或全文手工轉換

48px-Emblem-notice.svg.png

待翻譯頁面

本頁面尚未翻譯完成,歡迎使用者協助翻譯。更多

本文翻译自2020年5月26日的英文社区中心博客(有改动)。

如果这是您第一次看到有关统一社区平台项目的信息,请在评论之前阅读本文以了解有关项目整个范围的更多信息。

嘿大伙们!

我们很高兴地宣布,统一社区平台正在进入推出的第二阶段——将没有复杂扩展或功能集的wiki移动到新平台上!

这意味着什么呢? It means that the Unified Community Platform has reached the point where a number of existing wikis on the legacy Fandom platform can now move over to take advantage of new and improved tools like mobile editing and the 2017 Editor from the Wikimedia Foundation, just like the one used on Wikipedia.

You’re probably wondering how wikis will be selected. That’s covered later in the blog, but first I want to walk you through some major features released recently or soon to be released.

What’s new since UCP initial release and coming soon?

移动版编辑器

As mentioned last year, a survey of Gamepedia editors revealed that 34% of editors on that platform had their first edit experience on mobile. It is a massive opportunity for engaging new editors and also providing a better option for editors from countries where a smartphone is more likely to be their primary device for accessing the internet. Mobile Editor was added to the UCP a few weeks ago. You can learn more here.

文章评论

Redesigned to run on the same technology as Discussions, Article Comments will perform the same role as before and existing content will be transferred over. This does mean that, while the new Article Comments system will not support the use of wikitext, it will have the most common formatting options. Additionally, we are looking at trends in wikitext use from legacy products like Forums, old Message Wall, and old Article Comments to see if there is a better way forward for advanced formatting. We’ll have more info on that in the coming months.

自定义JavaScript

With the deployment of the CodeEditor solution in the last few weeks, we were able to support local custom CSS and global user CSS. With the release of the JS Review process in the near future, we will be able to support custom JavaScript for UCP wikis. Global personal JavaScript from the legacy platform will not carry over yet, as Community Central will be among the final wikis on Fandom migrated over to the new software.

Discussions enhancements from Forums feedback

Thanks to fantastic feedback and input from our Forums power users, we will be deploying the first round of enhancements to Discussions to make it friendlier for communities moving over from Forums. The first enhancements focus on making the Discussions feed more user-friendly for fans of a more traditional forum experience, with an optional condensed post list view and more emphasis on categories. Here are some design illustrations of these enhancements. They do not reflect the final implementations.

当前视图

Desktop feed now

精简视图(可选)

Desktop Feed

Disregard the mismatch of content. It’s just a design system thing.

Thanks to the results of a User Experience Research (UXR) study we conducted recently, you can expect further enhancements in the future. More on the upcoming enhancements and the UXR findings soon in a blog!

我们如何选择wiki?

For the first batch, our Product and Search Engine Optimization (SEO) teams looked at wikis based on the availability of features on the Unified Community Platform which they need to succeed. We considered wikis with different levels of traffic, to best understand how well they migrate onto the platform. Wikis were disqualified if they had any of the following:

  • 尚未迁移的论坛
  • MediaGallery
  • 成就
  • 博客
  • 自定义JavaScript
  • Semantic MediaWiki(SMW)
  • Shared uploads configured with a wiki that would also not be migrated in this round

The wiki teams then double-checked the list against their own knowledge of the individual communities, to ensure that wikis slated for migration are well-suited to thrive on the new platform. For example, wikis that have new content rolling out might be excluded from this initial wave so that there is no disruption to the ongoing discussion of said content.

Additionally, we have a process available for wikis that have not yet been selected by staff for migration to volunteer themselves. You can find information on that process and how to use it on this blog.

迁移会如何进行?

预定迁移的wiki会在最上方显示横幅通知(就像我们过去用来推播重要平台的通知那样),而您可能就是因为横幅通知的链接而看到这篇文章的人!

在迁移的当天,您所有wiki的内容都将导入到新的平台上。

以下是迁移进行的方式:

  • 您的wiki将设为唯读
  • 备份wiki内容
  • 制作备份的复本并保留在旧平台上
  • 原始的备份会透过自动更新流程运行并在新平台上进行设置
  • 在这过程中,脚本会检查wiki内容的结构,让它看起来像全新的UCP wiki一样(但wiki内容丶编辑历史等会保留)
  • 在新平台上会针对wiki的关键页面发出多项请求来检查错误,像是内容显示不正确丶数据库异常等等。
  • 最後wiki的网域会连到UCP的版本,并解除wiki的唯读状态

We will have alerts set for error spikes after your wiki transitions to the new platform and, if something goes wrong that cannot be fixed quickly, we’ll be able to revert your wiki back to the legacy platform.

If the import does not work correctly for some reason (i.e. the content does not transfer accurately or the import service fails) or another issue comes up with your migration, we will be able to point your URL back to the copy on the legacy platform. The reason that the SEO team has been involved in curating the first batch of migrations is to make sure we get good data on how the SEO for wikis changes. We are anticipating a net benefit to SEO as a result of the performance improvements on the new platform.

下一步

This stage is the second step in our process to get all the wikis in good standing onto a single codebase running a modern version of MediaWiki. As the process goes on, more and more features from the legacy Fandom and Gamepedia platforms will be added onto the new platform.

In the meantime, we’re happy to take your questions and answer what we can. To keep an eye on the details of what is released week to week, including bugs fixes and new feature additions, be sure to read the Release Highlights posts in the Technical Updates forum.


机智的小鱼君

机智的小鱼君@fandom

EdEx(IVT) - ZH | 国际志愿者团队中文助手

机智的小鱼君,Fandom编辑者体验与用户反馈团队成员,负责中文社区中心的维护与一般性用户支持。如果您有任何问题,可以在评论区告诉我们,获取最新Fandom官方资讯,请关注社区中心博客

除了特别提示,社区内容遵循CC-BY-SA 授权许可。