Changes between Version 163 and Version 164 of ImprovingBoostDocs

Timestamp:

Jul 23, 2007, 8:59:32 PM (15 years ago)

Author:

Matias Capeletto

Comment:

Add Helping Boost Authors description and STL docs help request

ImprovingBoostDocs

@@ -160 +160 @@
   * Boost-specific WikiMacros ( [http://tinyurl.com/346vdh more information], [BoostSpecificWikiMacros project wiki page] )
   * Quickbook as a [WikiProcessors WikiProcessor] for our Trac ( [http://tinyurl.com/2l9qfy more information], [QuickbookWikiProcessor project wiki page] )
-  * Trac Syntax Coloring for Boostbook, Quickbook and Jamfiles. ( [http://tinyurl.com/2myjp5 more information], [BoostTracSyntaxColoring project wiki page] )
   * Google Search Box project ( [http://tinyurl.com/2mfobx more information], [GoogleSearchBoxProject project wiki page] )
   * Syntax-highlighting project ( [http://tinyurl.com/35g4fv more information], [SyntaxHighlightingProject project wiki page] )
@@ -166 +165 @@
 Other ways to help us
 
-  * Volunteer as a browser tester ( More information in the [BrowserTestingChart browser testing chart] page )
-  * Document translator ( More information in the [DocsTranslationsProject docs translations project] page )
+  * Help building the Standard C++ Library Boosted Documentation ( More information in the [StandardCppLibraryDocumentation Standard C++ Library Docs page] )
+  * Volunteer as a browser tester ( More information in the [BrowserTestingChart browser testing chart page] )
+  * Document translator ( More information in the [DocsTranslationsProject docs translations project page] )
   * Comment on our work. We need constant feedback. Please offer your opinion on the [https://lists.sourceforge.net/lists/listinfo/boost-docs boost-docs list].
   * A lot of the documentation on this wiki is being written by a non-native English-speaker. Just reading and correcting typos and grammar will be appreciated.
@@ -222 +222 @@
   * '''[UnifiedLookAndFeelProject Unified look-and-feel project]'''[[Br]]
     Although Boost libraries are independent entities, together they build a superb, unified library. If we want people to understand this, we must provide an unified style for our docs and resources. This project will define the guidelines for the new look and feel of Boost.
-  * '''[DocsTranslationsProject Doc Translations]'''[[Br]]
-    If we want to have an unified look and feel in Boost docs, we need all documentation to be in a standard format. We are translating HTML-based docs to Docbook format. There are a lot of documents to translate and we need more volunteers to help in the process. If you want to participate, go to the doc translations project page. (We now have a bunch of tools that make the process painless, so please jump in!)
+  * '''[HelpingBoostAuthors Helping Boost Authors]'''[[Br]]
+    This section is a bazaar of friendly hands. We are teachers, experience users, native English speakers and artists. We want to offer our help to Boost authors to improve their documentation.
+    The main objective of this resource is to act as the main connection between Boost authors and some of IBD folks that are eager to help them. We hope this will make healthier the relation between Boost authors and our project. Authors will get helped, and have more time to improve and add new features to their libraries. We will get in touch with you and hopefully learn enough to become a boost author someday. It is a win-win situation. 
   * '''[GlueDocsProject Glue Docs]'''[[Br]]
     Documentation for Boost libraries is an impressive tool for learning about how individual libraries work. However, we are missing integration documentation that sees Boost as a whole. How we do common tasks, which libraries are powerful when combined, and real-life examples are important documentation that we cannot expect Boost authors to provide. The objective of the Glue Docs project is to build the necessary meta-library documentation for Boost.