公司网站 - 设计定制解决方案还是基于现有服务？
我被要求为一个小型组织（资金有限）设计一个网站 - 具有内部和外部面向。
在内部它允许共享文档、博客、目标设定等等？
在外部，它将提供一个简单但设计精美的关于公司服务的公开声明。
它可能会随着时间的推移而演变。
这应该是一个定制的解决方案，还是在提供此类服务的平台之上（例如？）更有意义？
如果它是一个自定义的内置解决方案，我正在考虑在 Rails 中执行此操作 - 是否已经为 Rails 构建了类似的东西？
I've been asked to devise a website for a small organization (with limited funding) - with internal and external facing sides.
Internally it would allow sharing of documents, a blog, goal setting, more?
Externally it would provide a simple but nicely designed public statement about the company's services.
It may evolve over time.
Should this be a custom-built solution or does it make more sense to ride on top of a platform that provides this type of service (such as?)?
If it's a custom built-solution, I'm considering doing this in Rails - would there be something like this already built for Rails?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我总是发现在现有平台上构建是令人沮丧的，尤其是在扩展功能时。 如果由您决定，我建议您自己构建。 选择一个框架并专门围绕公司的需求进行设计。
如果您熟悉 Ruby 编程，Rails 是一个不错的选择。 不过，任何现代 MVC 框架都一样好。
I've always found it frustrating to build on top of pre-existing platforms, especially when it comes time to extend the functionality. If it's up to you, I'd suggest to build it yourself. Pick a framework and design specifically around the needs of the company.
Rails is a nice choice if you're comfortable programming Ruby. Although, any modern MVC framework would be just as good.
我是 Hobo 的忠实粉丝。 位于 Rails 之上并延伸。 提供大量标准脚手架、管理功能和部分，并允许您发布静态页面。 您可以在任何和所有控制器上粘贴“before_filter :login_required”，以防止随机访问者看到某些内容，或者扩展用户模型以具有角色或其他基于访问控制的功能。
我从未使用 Hobo 为少数用户完全构建规模化服务。 但在小型环境中，通过访问控制来整合资源的速度非常快。
I'm quite a big fan of Hobo. Sits on top of and extends Rails. Provides a lot of standard scaffolding, an admin function and section, and lets you publish static pages. You can stick a "before_filter :login_required" on any and all controllers to prevent random visitors from seeing things, or extend the user model to have role or other based access controls.
I've never used Hobo to fully build out a scaled service for more than a handful of users. But in a small environment, it's awesomely fast to put together resources, with access controls.
Django 框架中已经内置了令人惊叹的管理功能。 它可能会处理所有内部事务，并且外部视图可以向任何不导航到管理员的人显示。
如果您正在考虑制定自定义解决方案，那么这至少是一个考虑因素（如果您认为该网站最有可能发展，我可能会建议您这样做。）
Django has an amazing admin function already built into the framework. It could potentially take care of all of the internals, and the external view can be shown to anyone who doesn't navigate to the admin.
It's at least one consideration if you're thinking of making a custom solution (which I might suggest if you believe the site will most likely grow.)
根据您的资源，我将从允许定制的“原样”解决方案开始。 从公司的角度来看，这将为您带来最快的“胜利”。 一旦组织和您开始使用并了解其好处，您就可以开始定制部件。
Depending on your resources, I would start off with an "as-is" solution that allows customization. This will give you the quickest "wins" from the company standpoint. Once the organization, and you, start to use and understand the benefits, you can start customizing pieces.
Windchill 会根据您的预算执行此操作。 我相信它曾经被称为 GlobalVault（一个更好、更具描述性的名称）。
Depending on your budget Windchill does this. I believe it was once called GlobalVault (a much better, and more descriptive, name).