User blog:KuroUrufu/I have added and structured more content, what are the next advanced steps?

You read the blog "I have added some content, what is next?" and you want more advanced advices? This is the right place! We are going to see some best practices for articles and how to use the source editor for adding and editing an infobox.

Content: SEO and best practices
As with everything, there are things that are good to do and things that are best avoided. You must always take into account the experience of the readers and the SEO: your personal preference is not always the best choice.

Avoid hiding parts of text or dividing it into subpages: prefer a single long page to many short subpages. Use clear and consistent titles to avoid possible duplicate pages (classic negative examples are mixing the various possible versions of names and using capital letters for the initial of words that are not proper names). Avoid using redirects instead of real pages for links: for example, if "Whitebeard" is a redirect to "Edward Newgate", write  and not.

In general, try to avoid adopting complicated solutions when there is a simpler version: Community Central is a good place to ask for help and opinions and where you can find more efficient solutions to get the result you want.

Article structure
The most important part of a content page is precisely the content: each page should be as comprehensive as possible. Before thinking about anything else, make sure that the page contains all the information it needs: think about what you would like to read on a similar page and put yourself in the shoes of who will read the page you are creating. For example, a page that talks about a character will describe their physical appearance, personality, particular abilities, history, various curiosities and trivia that may interest the reader. In addition to the information you know yourself as a fan, be sure to consult all available sources: chapters and episodes, official sites, extra volumes, special editions, interviews, etc...

Cons of the Visual Editor
The visual editor inserts the code all on the same line (unless you break lines when filling in the fields) and totally ignores the empty fields. This is what you see in the source editor after you added the infobox using the visual editor:

As you can see, this is not ideal when you come back to edit the infobox again with new information or simply check it's all correct. It's true that visual editor is easy to use for new editors but you want to be a pro so you'll find more useful to use the source editor.

Adding an infobox with the source editor
To use the source editor, we click the "EDIT" button if it is the default editor in our preferences, otherwise on "Edit source" in the drop-down menu to the right or by adding  at the end of the url.

Then we copy the code showed in the documentation and paste it into the article - the documentation is always present in the default infoboxes and you should always add it to your infobox templates. Fill in the parameter fields ("title", "image", etc) and then, if the rest of the page suits our needs, click on "SAVE CHANGES". Note: the source editor leaves the code as you entered it, including empty fields and indentation:

Isn't this easier to read and edit? .