制作 EPiServer 站点移动版本的策略
我即将帮助客户开发其 EPiServer 网站的移动版本。移动版本应具有与常规版本不同的功能，但某些内容可能会共享，这样就不必维护两次。
我正在考虑使用 jQuery Mobile 作为用户界面系统，以使用相同的解决方案覆盖尽可能多的用户，并且可能51 Degrees.mobi 用于移动设备的最佳检测。
有谁有如何使用 EPiServer 执行此操作的经验吗？如何构造？我正在考虑使用隐藏在常规站点上的子节点（/mobile），但我不确定这是最好的解决方案。
I am about to help a client develop a mobile version of their EPiServer site. The mobile version should have different functionality than the regular but some content might be shared so that it won't have be maintained twice.
I'm thinking about using jQuery Mobile as the user interface system to reach as many users as possible with the same solution and possibly 51degrees.mobi for best detection of mobile devices.
Does anyone have any experience in how to do this with EPiServer? How to structure? I'm thinking of using a sub-node (/mobile) that gets hidden on the regular site but I'm not sure it's the best solution.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
看看下面的博客文章：
iPhone 优化变得简单
它演示了如何使用 HTML、条件 CSS 和 jquery 构建适合移动设备的网站 - 全部都在 EPiServer 中
Take a look at the following blog post:
IPhone Optimalization Made Easy
It demonstrates how to build mobile-friendly websites using HTML, conditional CSS and jquery - all in EPiServer
看看这个： http://www.epinova.no/blog/Anders-Mrel/dates/2012/5/flexible-episerver-mobile-content-strategy-with-epinovamobiletemplateprovider/
Have a look at this: http://www.epinova.no/blog/Anders-Murel/dates/2012/5/flexible-episerver-mobile-content-strategy-with-epinovamobiletemplateprovider/
如果您希望内容集中在一处而不让编辑器使用“从中获取数据”，则子节点将不起作用。
最好的选择可能是“一个内容服务于所有人”，并有一个 cookie 标明“移动”或“完整网站”。默认模式可以通过检测来确定。如果选择移动设备，那么您可以提供不同的 CSS/JS 甚至其他页面属性或功能。
另一种选择是利用全球化机制并添加“Mobile”作为语言。这可能是编辑者在需要时创建单独的移动内容并保留其他页面的原始内容的简单方法。我记得您可以在不违反许可协议的情况下为不同的语言添加不同的顶级域，这样您就可以为移动“语言”拥有一个 .mobi 名称。
If you want content in one place without having your editors work with "Fetch data from" a sub-node won't work.
The best option is probably to have "one content serve all" and have a cookie that says "mobile" OR "full site". The default mode can be determined by detection. If mobile is selected then you serve different CSS/JS or even other page properties or functionality.
Another option is to make use of the globalization mechanism and add "Mobile" as a language. This could be an easy way for editors to create separate mobile content if needed and keep the original content for other pages. I recall you can add different top domains for different languages without violating the license agreement so you could have a .mobi-name for the mobile "language".