OPENSOURCE . COM {}

Detected CMS Systems:

Drupal (182 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Opensource.com Make Money
Keywords
Topics
Questions
External Links
Libraries
Hosting Providers
CDN Services

We are analyzing https://opensource.com/business/15/5/write-better-docs.

Title:
RTFM? How to write a manual worth reading | Opensource.com
Description:
Patience and empathy are the basis of good documentation, much as they are the basis for being a decent person. Here
Website Age:
27 years and 5 months (reg. 1998-01-08).

Matching Content Categories {📚}

Education
Books & Literature
Careers

Content Management System {📝}

What CMS is opensource.com built with?

Opensource.com employs DRUPAL.

Traffic Estimate {📈}

What is the average monthly size of opensource.com audience?

🌟 Strong Traffic: 100k - 200k visitors per month

Based on our best estimate, this website will receive around 100,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Opensource.com Make Money? {💸}

We can't see how the site brings in money.

The purpose of some websites isn't monetary gain; they're meant to inform, educate, or foster collaboration. Everyone has unique reasons for building websites. This could be an example. Opensource.com might be making money, but it's not detectable how they're doing it.

Keywords {🔍}

documentation, people, readers, write, writing, open, good, source, make, manual, great, technical, part, project, examples, things, tech, problem, work, article, read, community, error, software, reply, engineer, person, youre, document, easy, rikki, endsley, red, audience, python, english, writer, rocket, rtfm, rich, years, programming, docs, writers, point, dont, users, time, scope, written,

Topics {✒️}

linux-operating-user-manual-252543-17 assume viewers gnu/linux operating systems hardware-centric high tech higher-quality talent contributing /manuals/intel-oam-api generating end-user documentation numerous command-line applications written beginner-friendly step free/libre software project creative commons license linux operating manual red hat logo apache web server writing end-user documentation compassionate tech support programming perl book perl programming language additional aptitudes involved open source revolution open source advocate open source architect watching monty python development-related documentation modernizing enterprise java double-edged sword experienced public speaker perform physics calculations programming language books end-user doc open source projects open source engineer monty python references earlier persona phase open source documentation open source world native english speaker f'ing manual original skill-set skill set reserved aspiring technical writers de facto documentation budding technical writer anne gentle categorizes version control repositories unlike writing fiction native english speakers english-speaking men pretty nasty documentation internal social site learning/understanding

Questions {❓}

After all, we walked uphill in the snow to school, and back, with bare feet, remember?
All of this, for what?
And laziness?
But how do we go about doing that?
Have you noticed that the more frequently a particular open source community tells you to RTFM, the worse the FM is likely to be?
How does documentation get generated in hardware-centric high tech?
If you cannot effectively communicate your thought, idea, or concept to someone else then how far do you think you are going to be able to go with advancing your position?
In another vein, is actually the worst of FM, even worse than none?
In reply to All of this, for what?
That is: What topics are you willing to cover?
The first of these is who?
The next question to ask is where?
What can be applied to open source?
What is good documentation?
What should you be writing?
What would motivate an open source project manager to generate a requirements spec, an open source architect to generate design doc, and an open source engineer to generate implementation doc?
Where?
Who are you writing to?
Why do you focus on the command-line instead of telling people to click on button 'XYZ'?
Why should we make it any easier for these kids?
Why was a certain decision made?
Yes, you need to have documentation on your project website, but where else is the conversation already happening?

External Links {🔗}(26)

Libraries {📚}

FontAwesome
Foundation
Video.js

Emails and Hosting {✉️}

Mail Servers:

mx1.redhat.com
mx2.redhat.com

Name Servers:

dns1.p01.nsone.net
dns2.p01.nsone.net
dns3.p01.nsone.net
dns4.p01.nsone.net

CDN Services {📦}

Cloudflare
Redhat

3.35s.