So you’re interested in
Go ahead and take a look at these guidelines.
The introduction for your guide should focus on two things:
Example use case scenarios are great introductory material. Here’s an example of an article with a great introduction.
As technology moves forward and becomes the domain of the common individual, Object Oriented Programming has also gained a considerable amount of popularity. CodeIgniter is a great example of a program gaining such popularity, and to make it even better, it is a lightweight PHP web application framework. What does that mean for you exactly? Because CodeIgniter IS in fact a PHP application, it does not necessarily need to be installed on your personal/local machine. Instead, it will be installed on a server that utilizes a PHP plugin, meaning it can be used remotely or locally, depending upon the level of skill you have as well as your preferences.
In addition to using a Model-View-Controller for better presentation, CodeIgniter uses Clean URLs, meaning you won’t have to worry about those disaster URLs from the 90’s. All of this, of course, depends upon your ability to install the program. Most tutorials would work under the assumption that you have already installed the program, but we are going to cover all the bases so that you don’t have to hunt for installation tutorials around the web.
After the introduction, your guide should be 90% instruction and 10% explanation. Jump into the nitty-gritty, and provide just enough “Hmm, what’s this?” for people who aren’t familiar with the technology. If you want to, you can add an About Technology X section that goes into more theory and background, but the majority of the article should be free from tech rambling.
Aim for an appropriate level of technical difficulty. For example, an article about mail clients should be beginner-friendly, while an article about load-balancing across multiple servers can assume more sysadmin experience. Still, even in a more advanced article, don’t skimp on the instructions. You can always link to a different article for those who need it, so you don’t end up on a rabbit trail away from your main topic.
Instructions should be straightforward, technically accurate, and thoroughly tested. Skip shortcuts and err on the side of clarity, security, and best practices.
The tone we use in the Library is friendly and informational — the kind of tone you would use to explain something to a friend, while still getting down to business. A little informality is encouraged, but make sure you use proper spelling and grammar.
Use short, direct sentences, especially when you’re writing a single step in a set of instructions.
First, a few housekeeping points about file types:
Section titles should provide an at-a-glance outline of the article. Just by reading the table of contents, a reader should be able to grasp all the topics in the article, and click to jump to the most relevant section. If you use subsections, make sure you have at least two titles that belong in the lower level.
Create section titles like this:
When you provide step-by-step instructions, list them as numbered steps. Each task, even small ones, should get its own number.
Use bold text for the names of links, buttons, variables, and other text you point out to the user. Use italic text to introduce new terms. Use
If you’re writing about software with a GUI (graphical user interface), please include images (.png or .jpg). The maximum width for an image is 650 pixels. If you have a larger image, send the original and the resized version. The text for including an image is as follows:
If you reference outside materials, provide a link:
You can find more formatting instructions and detailed examples on the PHP Markdown Extra website, but the tips above should be enough to get you started!
Topic List and Submission Instructions
Thanks for writing for us! We hope to hear from you soon.