[drupal-docs] Difference between a "story" and a "page"

[Gabor Hojtsy]

>>"Stories are posts which appear on the default home page of a Drupal 
>>site, akin to a community weblog or Slashdot-like site where all site 
>>members can post. Or, the regular site users can be denied the ability 
>>to post to the front page using stories, allowing the site 
>>administrators to use the front page as an announcement board."
>>
>>"Static pages are a way for a site administrator to create pages which 
>>are not included in one of the other node displays and could be used 
>>instead of the Books for additional resource pages."
> 
> actually I don't get this at all.  If I setup stories and pages in 
> Drupal and give them the same node defaults - they operate the same.  I 
> think that the distinction you are making is arbitrary from the point of 
> view of what the features actually are.  While this is a reasonable 
> "best practice" - it is not "codified" - is this correct?

True, this is not codified.

> well we could also call them HTML_CONTENT_1 and HTML_CONTENT_2, and I 
> "get" that it is useful to have different node types to develop 
> different work flows - but I would want to have _3, _4, yada yada.   
> (and as was pointed out you can use flexinode or build your own node 
> type to do this).

Keeping story and page is an important legacy feature for those 
migrating. Until Drupal core provides an easy way to migrate workflows 
and permissions for these types to something else, they will not go. 
This was discussed on the devel list. Introducing other arbitrary named 
basic content types is not a good idea now. Story and page are just 
artifacts, their existance are not a proper representation whatsoever of 
the capabilities of the powerful node type system built in.

Goba