I would also add to your list the following.
categorization of content
taxonomy management
syndication management
inbound syndication
outbound syndication
workflow
-Matt
-----Original Message-----
From: Steven Brownlee [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 12:22 PM
To: CF_OpenSource
Subject: RE: Next step
Robert, I would like to help out on this project. My Sourceforge name
is orbwave.
While coding standards are being tossed about, perhaps it would be
beneficial to develop some functional specifications so that everyone is
perfectly clear on what the goal is and tasks can be assigned more
easily. Since this is a CMS, you could start off with major sections.
As always, proper planning wins the war.
I. User management
Ia. Content author(s)
Ib. Content owner(s)
Ic. Site manager(s)
Id. Site owner(s)
II. Asset/content management
IIa. Properties
IIb. Rules
IIc. Types
IId. Constraints
IIe. Owners
III. Process management
IIIa. Authoring
IIIb. Validation
IIIc. Approval
IIId. Staging
IIIe. Publishing
IIII. Site management
IIIIa. Architecture
IIIIb. Object definitions
IIIIc. Backup plan
IIIId. Archiving plan
IIIIe. Recovery plan
As far as coding standards, I think most people use a variation of the
classics. Here's what I use for my team:
- If you insist on using Fusebox, good luck and I'll work with you. I
strongly suggest that you don't. Fusebox is fine for web site
development. This isn't a web site. It's an application.
- Descriptive naming conventions (strWhatThisVariableContains)
- Three letter [or more] prefix (str, int, lng, sng, struct, cur, arr,
dbl, etc..) Even though this is not always necessary since CF doesn't
have all of these variable types, it still helps when debugging and
scoping.
- Proper scoping. Even though I rarely use the variables scope prefix,
I think that an initiative like this should be as rigorous as possible
to ensure minimal errors. Every variable should be properly scoped.
(variables, this/self, request, cgi, caller, application, session,
etc..)
- Proper locking. All access to application/session variables should be
locked and duplicated locally before use.
- Avoid the use of CFMODULE wherever possible. Whenever variables must
be passed to other modules send them to the request scope, CFINCLUDE the
required file and have it access the variables from the request
structure. Little trick I picked up from one of the cfObjects guys.
Noticeably speeds up applications. You won't be able to completely
avoid using it, but it can be kept to a bare minimum.
- Use CFSCRIPT when defining structure or arrays. Also long chunks of
code should be converted to CFSCRIPT whenever possible. Allaire always
said that CFSCRIPT would execute faster when there is complex looping.
I never saw any significant difference, but it sure looks better :)
There's my three cents.
-----Original Message-----
From: Robert Everland [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 12:59 PM
To: CF_OpenSource
Subject: Next step
Ok now that I have just about everyone signed up on the list we
have to come up with coding standards sheet. This should include, how
variables are named, flow of the program, pretty much anything you can
think of. Can anyone start suggesting some sheets they may have already
come up with or anything they would like to suggest?
Robert Everland III
Dixon Ticonderoga
Web Developer Extraordinaire
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
