Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 411553
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T17:59:53+00:00 2026-05-12T17:59:53+00:00

Currently the documentation where I work is in a bit of a state. There

  • 0

Currently the documentation where I work is in a bit of a state. There isn’t anywhere near enough of it, and the documentation that does exist is spread out over many word documents making it hard to find anything.

I’m trying to take some initiative and get it improved, and I figure the first thing is to find a better format to write the documentation in:

  • My thoughts are that the documentation should be structured in a series of short articles (MSDN / Html Help style) and structured in a suitable tree:
    • It would be good to be able to produce a standalone Html-Help style package to be shipped with the application
    • As well as being able to produce a MSDN-style website as a reference for those who are too lazy to look at the CD.
    • Search is of course a must-have
  • It needs to be at least reasonably easy to update – if there is a 17 step process to update the published documentation then it makes it seem like too much work to do simple changes, and nobody can ever be bothered to update it.
  • The documentation is technical in nature, and so ideally it would be nice to be able to include generated documentation from things like the Xml documentation embedded in C# code. This is however definitely a side-requirement – currently very little useful Xml documentation exists, its just that in the future I plan to fix that.
  • For the same reason it is often good to be able to handle things like attachments (code samples etc…) I’m not expecting anything fancy, but this is something I need to bear in mind to make sure that its at least not handled badly.

Are there any projects or languages that are suited to this sort of documentation?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T17:59:54+00:00Added an answer on May 12, 2026 at 5:59 pm

    I’ve started using DokuWiki. Its not exactly what I was originally looking for (I think I was really looking for a CMS), but it does the job and some respects its better than what I originally had in mind (in particular its a wiki – I’ve not yet gotten as far as publishing this to our customers however so I’m not sure how well thats going to work out)

    I’m using the IndexMenu plugin and the Arctic template to get a navigation tree on the left, and if I publish the wiki itself I’ll use the discussion plugin to allow users to post feedback.

    Currently my method of handling generated content is to use xslt templates to produce dokuwiki syntax, and write that output directrly to files / folders in the “data/pages” folder.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there anywhere that I can find documentation on the scope of the XML
Is there a library out there that will get you your approximate location using
I am currently using MediaWiki as a documentation website, with login authenticated by LDAP.
I'm required to write documentation for my current project that lists all .c files
Currently, I am writing up a bit of a product-based CMS as my first
This RFC mentions Unlike many programming languages Perl does not currently implement true multiline
Currently plugins I write seem to work or not in random ways. Some do
I am attempting to work with Google Checkout on Google App Engine. Currently, I
Currently, I don't really have a good method of debugging JavaScript in Internet Explorer and
Currently my workflow with Emacs when I am coding in C or C++ involves

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.