| Article marketing is just like a real business; there | | | | engines. In which case it could be possible that a |
| are the employees or freelancers (authors), the | | | | client hits an article that is one in the middle of a |
| publishing system and the editors (together the | | | | series - for example the reader gets article two |
| internal organization) and there are ... the clients | | | | (2) not knowing that there are many more |
| (the readers). The goal is to get satisfied clients. | | | | articles. In this case, the reader is in the middle of |
| And there is always a problem. For example the | | | | a short story, that is to be continued, but he |
| article-parts-problem. This is a normal business | | | | would not know where to follow it. |
| problem. An organization should arrange its | | | | The solution |
| business between internal efficiency requirements | | | | What you normally see in business is that the |
| and external (client) demands. | | | | employees are guided by the limitation of the |
| The employee (the author) | | | | system. In many cases there is some kind of an |
| Certain authors write their articles in parts, for | | | | information system and as any system these are |
| example - "How to color your presentation (1)," is | | | | always limited in their functionality, because it |
| the first part, followed by "How to color your | | | | would make these systems too expensive to |
| presentation (2)," the second part. There could | | | | solve all possible exceptions. The system is leading |
| also be a third part. This is what I personally like | | | | the organization in these (and many other) cases. |
| about these sequels; that when I think there is | | | | The author in this situation should learn to cut his |
| something more to tell about the subject, I just | | | | or her articles up in autonomous parts with a |
| add another article in the same sequence. At | | | | singular start and end. That requires training, but |
| whatever moment. | | | | would also require that "broken" articles get |
| The problem | | | | rejected by the editors. This will diminish the |
| The problem is however that there could be a | | | | internal efficiency. |
| time lag between article part one and part two. | | | | Or, the system should be tailored to the needs of |
| The article system is placing the articles in a | | | | both the employee and the client. In this case the |
| sequential order. Like a normal library, the article | | | | system should search for a sequel and present a |
| directory is ordering the articles per author and on | | | | little button with the text - "continue reading next |
| an alphabetical order, but (unlike a normal library) | | | | part," or "read previous part." This is a more |
| this is not visual for the reader, nor are the | | | | expensive solution. |
| different parts linked together. | | | | To solve issues like these you need to balance |
| The client (the reader) | | | | between internal efficiency and external client |
| It appears that articles - as they are pure content | | | | demands. Most of the time you will end up |
| - are most of all retrieved through the search | | | | somewhere in the middle. |