Article Help: Should I split my article?
-
:~ Apologies if this is not the right group to post. I am about to post a tutorial on programming the Windows 2000 ACL editor (in C++). However, the tutorial is running rather long, and I am wondering if I should split the article into a two or three part series. Here's what I currently have in the tutorial: 1. (optional) A brief description of
SECURITY_DESCRIPTORandSECURITY_DESCRIPTOR_RELATIVE, and their differences. 2. (optional) A description of the ACL. 3. A brief description of the ACL Editor (from the programming perspective). 4. Implementing theISecurityInformationmethods.ISecurityInformation::SetSecurity()(this is where most of my article will be focused). This has already taken up to 3500 words already (35K, excluding code), and I haven't even started talking about theISecurityInformation::SetSecurity()method (which I expect to take most of my content)! Do you think I should post this article as a two part series? Advantages if I split the article: 1. I won't need to jettison any content from my article. In fact I will be able to add in some stuff about General access control, how to enumerate them, how to build them, and include some information on the new System.Security.AccessControl classes (and maybe Keith brown's code). 2. C#/VB/.Net programmers will then find the article useful. 3. The reader won't be so intimidated by the horde of information that they have to read. 4. I will have covered everything, so the reader won't be left confused and asking "WTH is aSECURITY_DESCRIPTOR:confused:?". 5. Reviews and feedback will be easier for the reader (since you can say "the first article woz teh suck", but the "second article had teh 1337!") :-D Disadvantages if I split the article into a series: 1. It will take me longer to author. 2. Perhaps it's too long because I suck at writing (but you alrady knew that just by reading this post! :-D ;P). 3. I'm writing about two separate distinct topics (general authorization, and programming the ACLUI), and that's why my article is so long (but that means I should post 2 articles!). 4. Maybe I should redirect the users to other tutorials instead of rewriting about Access control (does anyone know any articles about the security descriptor?). If I hear no feedback, then I will go ahead and split the article in two (or 3). Tia -
:~ Apologies if this is not the right group to post. I am about to post a tutorial on programming the Windows 2000 ACL editor (in C++). However, the tutorial is running rather long, and I am wondering if I should split the article into a two or three part series. Here's what I currently have in the tutorial: 1. (optional) A brief description of
SECURITY_DESCRIPTORandSECURITY_DESCRIPTOR_RELATIVE, and their differences. 2. (optional) A description of the ACL. 3. A brief description of the ACL Editor (from the programming perspective). 4. Implementing theISecurityInformationmethods.ISecurityInformation::SetSecurity()(this is where most of my article will be focused). This has already taken up to 3500 words already (35K, excluding code), and I haven't even started talking about theISecurityInformation::SetSecurity()method (which I expect to take most of my content)! Do you think I should post this article as a two part series? Advantages if I split the article: 1. I won't need to jettison any content from my article. In fact I will be able to add in some stuff about General access control, how to enumerate them, how to build them, and include some information on the new System.Security.AccessControl classes (and maybe Keith brown's code). 2. C#/VB/.Net programmers will then find the article useful. 3. The reader won't be so intimidated by the horde of information that they have to read. 4. I will have covered everything, so the reader won't be left confused and asking "WTH is aSECURITY_DESCRIPTOR:confused:?". 5. Reviews and feedback will be easier for the reader (since you can say "the first article woz teh suck", but the "second article had teh 1337!") :-D Disadvantages if I split the article into a series: 1. It will take me longer to author. 2. Perhaps it's too long because I suck at writing (but you alrady knew that just by reading this post! :-D ;P). 3. I'm writing about two separate distinct topics (general authorization, and programming the ACLUI), and that's why my article is so long (but that means I should post 2 articles!). 4. Maybe I should redirect the users to other tutorials instead of rewriting about Access control (does anyone know any articles about the security descriptor?). If I hear no feedback, then I will go ahead and split the article in two (or 3). TiaFrom your description, I would split it into two parts: 1 - cover all the details of ACLs: definitions, structs, APIs, interfaces, etc. 2 - talk about the ACL editor That way part 2 builds on part 1, but people who already know about ACLs can jump right to part 2. --Mike-- LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ Strange things are afoot at the U+004B U+20DD
-
From your description, I would split it into two parts: 1 - cover all the details of ACLs: definitions, structs, APIs, interfaces, etc. 2 - talk about the ACL editor That way part 2 builds on part 1, but people who already know about ACLs can jump right to part 2. --Mike-- LINKS~! Ericahist | 1ClickPicGrabber | CP SearchBar v2.0.2 | C++ Forum FAQ Strange things are afoot at the U+004B U+20DD