After a quick scan of this thread, I see that a lot of people are attempting to isolate the demographic using Actinic.
Really, you have a much broader scope of people using the software. Its difficult to pidgonhole them.
As a designer, consultant and coder, I have encountered myriad types of people, but the majority of problems boil down to this:
Actinic is a package that lets people open a shop, without any web skills. As soon as they want to think outside the box, then its more a problem with designing websites, NOT with Actinic itself.
This, in conjunction with the 'blocks' syntax used by Actinic Catalog, means that they have to learn something to get the job done. I can tell you from experience, that the blocks language is probably the simplest scripting language I have ever seen. The problem is, I think this way, because I use PHP every day.
ChrisBarling:
Would you be able to tell us, roughly what percentage of support calls are html/css and generally unrelated to Actinic?
If this thread is about getting better support out of Actinic, then I'd suggest the following things:
- Actinic provides an Actinic related crash course in html and css.
- Your document people make some screencasts about blocks.
- Your document people come up with some 'checklists' and include them in error documentation.
This is merely about stemming the flow of questions that can be answered elsewhere, for I really think that people who want 'out of the box' elements in Actinic are trying to run before they can walk.
Really, you have a much broader scope of people using the software. Its difficult to pidgonhole them.
As a designer, consultant and coder, I have encountered myriad types of people, but the majority of problems boil down to this:
Actinic is a package that lets people open a shop, without any web skills. As soon as they want to think outside the box, then its more a problem with designing websites, NOT with Actinic itself.
This, in conjunction with the 'blocks' syntax used by Actinic Catalog, means that they have to learn something to get the job done. I can tell you from experience, that the blocks language is probably the simplest scripting language I have ever seen. The problem is, I think this way, because I use PHP every day.
ChrisBarling:
Would you be able to tell us, roughly what percentage of support calls are html/css and generally unrelated to Actinic?
If this thread is about getting better support out of Actinic, then I'd suggest the following things:
- Actinic provides an Actinic related crash course in html and css.
- Your document people make some screencasts about blocks.
- Your document people come up with some 'checklists' and include them in error documentation.
This is merely about stemming the flow of questions that can be answered elsewhere, for I really think that people who want 'out of the box' elements in Actinic are trying to run before they can walk.
Comment