定义 GWT 边界
我有一个 GWT 应用程序，我想将其作为软件即服务 (SAAS) 在网络上发布。我在 SliceHost 上有一个 Linux 实例，已全部预热并准备好接收大量注册。
但现在我想我必须提供一个网站来发起这场洪水。它将有可爱的图标、顾客欣喜若狂的认可、我的生活故事，以及所有常见的欢乐和轻浮。还有一个指向注册表单的链接（不，是几个链接）。 :-)
那么您认为：我是否需要向我的应用程序中添加更多自定义小部件以使营销口号成为应用程序的一部分？或者，当用户无法再抗拒那个漂亮的绿色大按钮时，我是否单独开发一个非 GWT 网站并重定向到我的应用程序？
编辑：需要明确的是：从用户的角度来看，两种情况下的网站看起来都是一样的。我只是在思考如何实现它。
I have a GWT application that I want to release as software-as-a-service (SAAS) on the web. I have a Linux instance at SliceHost all warmed up and ready to receive a flood of sign-ups.
But now I suppose I've gotta provide a web site to initiate that flood. It'll have cute icons, ecstatic endorsement from customers, my life story, all the usual joy and frivolity. And a link - no, make that several links - to the sign-up form. :-)
So what do you reckon: do I add some more custom widgets to my app to make the marketing gumph part of the app? or do I develop a non-GWT web site separately and redirect to my app when the user can no longer resist that nice big green button?
Edit: Just to be clear: from the user's point of view, the web site would look the same in both cases. I'm just musing over how to implement it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
将其保留在您的应用程序之外，以便搜索引擎能够抓取您的营销宣传并将大量新用户从他们的搜索中重定向:-) 此外，将营销和可能的博客与您的 Web 应用程序分开，以便更轻松地拥有不同的内容发布周期，因此您不必在自己的 Web 应用程序中构建 CMS（当然，除非它是 CMS 管理工具:-)
我建议仅在用户可以的情况下在 Web 应用程序和营销宣传之间进行更紧密的集成无需注册或登录即可使用部分（或全部）网络应用程序。
Keep it outside your app, to make it possible for search engines to crawl your marketing pitch and redirect those floods of new users from their searches:-) Furthermore, separate marketing and possible a blog from your web application to make it much easier have different release cycles, and so you don't have to build a cms in your own web applications (unless it's a CMS management tool of course :-)
I would suggest to only make a tighter integration between web application and marketing pitch if the user can use part(or all) of your web application without having to register or login.
现在，我们的应用程序是两个独立的东西，一个简单的 HTML 营销页面，里面充满了人们对着屏幕微笑的人，其中有转到该应用程序的绿色大注册按钮。它工作得很好，对我们来说，很高兴拥有一些非 gwt 的东西，让我们的设计师可以在不与编码器合作的情况下制作和维护。这是无缝的，我推荐它。
不过，我可以想象有一天我们想要将它们联系起来。假设我们想用实时嵌入的小部件替换屏幕截图，或者让登录按钮神奇地用应用程序替换页面的内容，等等。在制作多个 GWT 模块之前，我会切换到单个应用程序将其分开。
祝你好运！
PS：直到现在我才想到的是，保持营销页面纯 HTML 可以减少下载大小和预热时间。下载 GWT 应用程序还不错，但单独的页面是最简单的代码分割形式；）
Right now our app is two separate things, a plain HTML marketing page full of people beaming at their screens with big green signup buttons that go to the app. It works great, and for us it was nice to have something non-gwt that our designer could make and maintain without working with the coder at all. It's seamless, and I recommend it.
I can imagine a time, though, when we'll want to connect them. Say we want to replace the screenshots with live embedded widgets, or make the login button magically replace the contents of the page with the app, etc. I'd switch to a single app before I would make, for example, multiple GWT modules to keep it separate.
Good luck!
PS: Something I didn't think of until just now is that keeping the marketing page plain HTML reduces the download size and warmup time. It's not too bad to download a GWT app, but a separate page is the easiest form of code splitting ;)