技术

技术类文章。

“分类”学习材料:分类是网站的基础

 
  1. 分类学和存在论是其他用以描述安排类别的工作的词语。发展一个类别结构的目标是为了创作一个使人容易找到材料的系统。
  2. 一般来说,当一个类别有超过20个条目时,子类别可能会对用户带来方便,但当类别包括少于20个连接时,建立分类很可能会妨碍用户找出所需要的资料。当一个类别有超过20或更多的条目时,编辑员应该可以见到可以容易被分为不同的专题的连接组合。
  3. 有用的类别名称的特性

    有用的类别名称

    • 除非有关的缩写或简称是常见的话,否则请不要使用它们。
    • 不要重复上级类别的名称

      在商业类别下关于商业新闻的网站
      请勿使用:商业新闻
      可以使用:新闻与媒体

      在艺术/电视类别下的节目制作公司网站
      请勿使用: 电视节目制作公司
      可以使用: 制作公司

    • 不应被称为“综合”、”一般性“、“其他”或其他让人觉得它包括一系列一般性或没有关连的网站的连接。在一般性或隶属很多类别的网站应该登录在最适当的类别的顶级或被移动到一个合适的专题分类 里 。
      范例
      Recreation: Outdoors: Backpacking: General_Sites 的网站条目都应该被移动到Recreation: Outdoors: Backpacking类别中。所有一般性关于 以背包客形式旅游 的网站都应该在一个科目的最低级的有关专题类别中被登录。例如,如果在General Sites中有一个背包生产商的网站的话,它应该被登录在Recreation: Outdoors: Backpacking: Manufacturers类别而不是Recreation: Outdoors: Backpacking的主类别。
    • 不要用简写或符号(例如&、+、`n或etc.)代表词语 。

      请勿使用: 期刊、杂志等
      可以使用: 杂志

      请勿使用: Resources `n Directories
      可以使用: Directories

      请勿使用: 新闻+媒体
      可以使用: 新闻与媒体

    • 不要使用可以使人误认为类别中有非法内容的连接(例如:Warez或私货)
发布于 由 dongwei0 篇评论

WWF(Windows Workflow Foundation)的简介[翻译]

Windows Workflow Foundation简介(翻译): 
     Windows Workflow Foundation是帮助您在Windows平台上快速建立工作流应用程序的编程模型、引擎和工具。
——翻译自:http://msdn.microsoft.com/windowsvista/building/workflow/workflow_overview/

     Windows Workflow Foundation为开发和执行各种基于工作流的应用程序提供了编程框架和工具。 
     Windows Workflow Foundation是一个开发框架,允许你在.NET应用程序中嵌入工作流。WWF本身不是一个可执行的软件或程序,WWF主要是帮助你创建自己的工作流应用程序。
——翻译自:Windows Workflow Foundation SDK文档

     Windows Workflow Foundation是一个帮助你开发基于Windows平台的工作流解决方案的可扩展的框架。作为将来Microsoft WinFX的一部分,Windows Workflow Foundation提供一组API和工具以支持基于工作流的应用程序的开发和执行。Windows Workflow Foundation为创建跨越不同应用程序的端到端解决方法提供了一个简单、统一的模型。 
      Windows Workflow Foundation是一个通用的工作流框架。基于Windows Workflow Foundation的解决方案由相互链接的.NET组件构成并运行在宿主程序中。就像你在一个特定的设计环境下创建ASP.NET页面一样,Windows Workflow Foundatio也为你提供了一个良好的设计环境,在可视化设计器中,你可以创建特定的流程、在工作流组件中增加代码、定义商业过程, 
      Windows Workflow Foundation提供了工作流引擎、.NET-managed API、运行时服务、与Visual Studio 2005集成的可视化编辑器和调试工具。你可以使用Windows Workflow Foundation创建和执行运行在客户端和服务器端的工作流,并且可以运行在所有的.NET应用程序中。
——翻译自:Getting Started with Microsoft Windows Workflow Foundation: A Developer Walkthrough

其他Windows Workflow Foundation相关文章:
http://blogs.msdn.com/ccboy/archive/2005/09/20/471700.aspx
http://blogs.msdn.com/ccboy/archive/2005/09/19/471079.aspx
http://www2.ccw.com.cn/05/0541/a/0541a12_1.asp

发布于 由 dongwei0 篇评论

The 8 Types of Navigation Pages

The 8 Types of Navigation Pages

November 28th, 2005 by Jared Spool

When users are searching for content on a site, each page they encounter must do one of two things. Either the page provides the content they are seeking or it delivers them closer to the page that does.

As we’ve watched users search for their desired content, we’ve realized there are patterns to the pages we see. We’ve started to catalogue these patterns and have concluded there are essentially 8 types of pages a user can run into, when searching content-rich sites.

These different page types turned out to be important as we discovered users behave differently as they encounter each one. If the design of a given type doesn’t support the user’s behavior, then the user is less likely to succeed in finding their target content. Often, pages fail because designers don’t realize they were designing for the wrong type.

The eight types (in a loose most-to-least importance order) are:

  • Content Pages: The most important page on your site, assuming it contains the content the user seeks at that moment. Also known to contain lateral navigation, allowing users to jump from content page to content page to gather more information to support their activity.
  • Galleries: A listing of links to content pages, this page is the most critical “link in the chain” of pages. Most navigation failures we see are due to poorly-designed gallery pages. Users want to decide on the content page from within the gallery, to eliminate pogosticking.
  • Departments: Sites that have too many links for a single gallery need to have a Department page, which lists all the galleries. While you’d think these would work the same as galleries, users somehow understand that a list of galleries is different from a list of content pages and use these pages more for winnowing their selection down.
  • Stores: Really large sites (such as those with more than 50,000 content pages) find that they need multiple departments. If they have enough departments, they’ll need multiple pages to describe them–we call those store pages. News sites, for example, often have store pages (such as US, World, Business, Sports, and Weather). Stores are segmented content areas that users rarely bounce between, therefore requiring everything that user needs in one location.
  • Gallery-level Search Results: The most common of search result pages, the Gallery-Level Search Results page are similar to plain-old galleries, except they contain the search engine generated results. This means they don’t benefit from the handcrafted selection process of real galleries, but instead are computer-generated and, therefore, have a harder time presenting the necessary information for choosing.
  • Department-level Search Results: On really large sites, it’s not uncommon for the search engine to try to divide the results into departments, creating what we call Department-level Search Results. These results are presented to assist in the winnowing process.
  • Search Entry Page: The page where the user enters their search query. (Sometimes it’s a standalone page, but frequently it’s just a section of a larger page, such as a gallery or a department.)
  • Home Page (Landing pages): The least important page on the site (unless it contains the user’s content), the home page (which, in this day of Google & Yahoo is often a landing page and not the top-level URL page) is tasked with orienting users in the right direction–sort of a Munchkinland at the start of the yellow-brick road. Depending on the size of the site, it’s like the home page will also be a content, gallery, department, or store page.

These different pages are very important to understanding how the Scent of Information works. It’s something you’ll find us talking about a lot over the next few months.

For those of you who love to see these thing demonstrated live, Christine and I will be sharing a lot of our research on the eight types at the Web Design Foundations Roadshow, showing examples from dozens of sites, such as Lands’ End, the Bureau of Labor Statistics, Ericcson, and others.

发布于 由 dongwei0 篇评论

为什么 IT 规划必须由专业人士制订?

这是我有时候需要向客户说明的一个问题。这不是三言两语能够说清楚的,往往涉及一些敏感的事情,而且容易沦为自卖自夸式的“叫卖”,所以这里只打算说一个意思:

IT 规划必须由专业人士来制订,是因为内部人受视野所限,谁都不可能做好这项工作。

有一个外国佬叫做 John Zachman,提出一个东西叫做 Zachman Framework。这个框架得到广泛的认同,Zachman 自然而然就成为 Zachman Framework 之父。其大意是说,对同一个信息系统,不同的人看同一个问题,其结果是不同的。

Zachman 框架按 5W1H 的六个侧面来考察信息系统(或企业架构,这个词现在更时髦些),分别对应数据(What)、行为(How)、位置(Where)、人员(Who)、时间(When)与动机(Why)。规划者能够看到企业的方向和业务宗旨,包括对系统边界范围;企业所有者能够用企业术语定义企业的本质,看到的是企业的结构、处理、组织等;体系结构师能够用更严格的术语定义企业的业务,看到的是每项业务处理所要完成的功能;设计师使用技术模型来解决企业业务的信息处理需求;而构建者则需要去解决关于特定语言、数据库存储表述及网络状况等具体细节。

由此可见,不同的人员看问题的视角不同,包括企业所有者在内的所有内部人员的视角都有局限性,唯有规划者能够看到企业的本质问题。

Zachman Framework 如下图所示(点击可放大)。

点击放大


Trackback: http://tb.donews.net/TrackBack.aspx?PostId=628155

发布于 由 dongwei0 篇评论

个人信息云与个人Web门户

更正:
- 社交网络部分,更准确的应该是LinkedIn这样的。
- 更外围,也就是last.fm、flickr、seehaha等发展出的信息社会性网络构成人的第二层信息云(个人私有信息云,个人社会信息云,最外是公共信息云)

这就是Web2.0时候的个人信息状况。人们的各种数据可以在不同的服务平台上以微内容的方式发布并分享。

这些信息借助Tags/Folksonomy,各自衍生出和个人兴趣高度相关的个人社会性网络。

但是有个问题,个人的内容被分散到各个不同的平台。

还好,我们有RSS以及聚合机制。

那么,应当会出现这样的个人Web门户服务:

我可以把我分享在不同地方的微内容聚合到一起,并且我能选择那些可以被公开,那些只能对朋友分享,那些对家人,这个选择的数据来源于社交网络的服务,通过APIS调用。

不仅是个人数据的集中展现。更重要的,应该是个人所兴趣的信息社会网络的聚合。这么一来,它就成了我上网的入口。

(email和bbs也应当被纳入)

发布于 由 dongwei0 篇评论