[development] Story vs Page - Again
cog.rusty at gmail.com
Tue Dec 26 15:59:53 UTC 2006
They only "work the same" from a developer's perspective. For an end user
who will be using them to submit content, different workflows can make a
huge semantic difference. 'Page' (or 'static page' or 'site page', if you
prefer) is for building your site while 'story' (or 'user posting' or
'posting') is for adding daily content. Of course if the developer's
perspective was what mattered most, then both these default content types
could be scrapped.
On 12/26/06, Chris Johnson <cxjohnson at gmail.com> wrote:
> Would I be insane to suggest that 2 node types which work the same,
> but have different default work-flow / comment settings, should not
> have names as different as "story" and "page"? How about naming them
> "storytype1" and "storytype2" or the semantic equivalent? (I'd prefer
> to not use "page" since it collides with multiple nodes appearing on a
> themed page.)
> On 12/22/06, Dries Buytaert <dries.buytaert at gmail.com> wrote:
> > On 22 Dec 2006, at 05:28, Boris Mann wrote:
> > > On the flexibility angle, I'm going to propose a patch with two/
> > > three changes:
> > > * page not promoted by default
> > > * page with comments off by default
> > > * (don't know if we can easily do this) page with "submitted by"
> > > turned off by default
> > 3 x YES, and I'd like to go one step further. Add a parent ID to
> > pages (or nodes in general) so we can create content trees with
> > proper breadcrumbs (eg. Home >> About us >> Management >> Joe Boss
> > (CEO)) and navigation links. We might be able to deprecate
> > book.module in the long run.
> > I'd accept patches for all of that so make sure to submit it to core
> > rather than keep it in your install profiles. Thanks.
> > Maybe create an issue for it already? ;-)
> > --
> > Dries Buytaert :: http://www.buytaert.net/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development