Skip to primary content

Blog Fiasco

The world's only(?) FOSS/weather/sports/marketing/high-performance computing blog

Search

Main menu

Home
About

Post navigation

← Previous Next →

5 reasons to use a rendered language for your documentation

Posted on June 5, 2015 by Ben Cotton

Over at OpenSource.com, I have a follow up to my wiki post telling you why you should use a rendered language for your open source project’s documentation.

Share this:

Click to share on Mastodon (Opens in new window)
Click to share on Facebook (Opens in new window)
Click to share on LinkedIn (Opens in new window)
Click to share on Reddit (Opens in new window)
Click to email a link to a friend (Opens in new window)
Click to print (Opens in new window)
More

Click to share on Tumblr (Opens in new window)
Click to share on Pinterest (Opens in new window)
Click to share on Pocket (Opens in new window)
Click to share on Telegram (Opens in new window)
Click to share on Twitter (Opens in new window)
Click to share on WhatsApp (Opens in new window)

This entry was posted in FLOSS, Project Management and tagged docbook, documentation by Ben Cotton. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment *

Name *

Email *

Website

Notify me of follow-up comments by email.

Notify me of new posts by email.

Δ

License

Posts on Blog Fiasco are shared under the Creative Commons Attribution-ShareAlike 4.0 International license except as noted.

Membership

Tags

Proudly powered by WordPress