WikiPages

This page gives common guidelines on the best practices to be followed when writing or updating FreeCAD documentation.

It also has the goal to bring together the threads that are dispersed in the forum and try to make order, being a single point of reference for FreeCAD documentation discussion and brainstorming, to better organize the wiki.

Before Starting
Editing wiki pages is easy. Before starting editing FreeCAD wiki pages, be sure to be familiar with the Wiki editing basics.

Concise Descriptions
When describing FreeCAD functionality try to be concise and to the point. Also, please describe what FreeCAD does, NOT what FreeCAD does not do. There might be exceptions for justifying why FreeCAD does not support a certain functionality, in case for instance there is a different philosophy or way to achieve the result with respect to traditional CAD systems, but these cases must be the exception.

Centralized Information
Ideally, you should try to avoid duplicating the same information in different places. While it is simple to copy & paste some text, it will eventually lead to misaligned information when a page is updated and the other not. You should insert the information in one place only, and make reference to this single point.

A possible solution for the above problem is the use of templates and transclusions (see Templates and transcluding pages if you are not familiar with this concept), but their usage for this goal is strongly discouraged. The reason is that in the printed manual created from the Wiki help you will have the same information printed over and over again; but even a reader using the Wiki can be confused by finding the same text in different pages. In case you need the same explanations in more than one point of the documentation, please consider creating a new page topic, and make explicit references (links) to this page.

Styling
Templates are heavily used, instead, for styling the text. For instance, there is a template for styling menu commands, like, another template to style keys to be pressed, like , etc.. This allows to have a consistent look and feel of the documentation, as well as to be able to update the style by simply changing the template. Please get familiar with the templates used in FreeCAD Wiki Help documentation before writing help pages.

Examples
Working by examples will help you keep the right track, and be ahead on the learning curve. So even if reading the following sections is highly recommended, you can quickly get familiar with the structure and style of FreeCAD wiki looking at the following pages, that can be considered reference for best style practices of FreeCAD documentation.

If you are consistent with this look & feel, you won't be far from a correct FreeCAD documentation page, and your contribution will blend more easily in the wiki.


 * Draft ShapeString
 * Draft Line

General
You should normally not use a =header= for a page, since the page title is automatically added.

The User's hub provides a Table of Contents. This is used as the main reference for (automatically) building the offline help you can reach from FreeCAD, as well as the offline pdf documentation. The Template:Docnav, which is used to link a page with the previous and the next page of the same section (see section below for a list of all templates, including Docnav) should be aligned with the structure in the Table of Contents.

Page Names
Page names should be short, and every word should begin with a capital letter, unless they are articles, prepositions, conjunctions (e.g. 'of', 'on', 'and')

Bad name
Working with architecture walls

Good name
Arch Wall

Workbench pages must have the format XYZ Workbench, where XYZ is the name of the referred workbench.

Pages describing the tools of a workbench must have the format XYZ MyTool, where MyTool is the name of the specific tool.

Links
You should use the original link name for the links whenever possible. This clarifies the referenced chapter in printed / pdf documentation. You must anyway avoid the usage of non-meaningful words for the link.

Bad link
For more information on this topic, click here.

So-so link
For more information on this topic, refer to drafting 2D objects.

Good link
For more information on this topic, see how to draft 2D objects in the Draft Workbench.

Workbench pages
Every page of a workbench should start with:
 * the name of the workbench
 * an image of (an example) of the look of the workbench. Not necessary to show a model (see anyway the section for rules), but the menu and toolbar should be visible, in their default position
 * a description of what the workbench is used for

Command (tool) pages
The command pages describing workbench tools should not be too long, they should only explain what a command can do and what it can't, and how to use it. You should keep pictures to a minimum, and not give too many examples - tutorials is where we should go in step-by-step details.

Restrictions should be documented right in the command page itself rather than elsewhere, possibly under a "restrictions" chapter.

Please refer to the Gui Command page for specific indications on Gui Command rules (naming, documenting, etc.).

Tutorials
Good tutorial examples are available at FreeCAD tutorial - Unofficial tutorial blog. Though they are not styled as FreeCAD wiki pages, they are a valid example of how a written tutorial should look like.

Expressions
You should avoid colloquial generic expressions as 'a couple'. Please re-phrase as 'some' if indeterminate, or with the correct cardinality.

Conciseness
Try to avoid repetitions to keep descriptions short.

Bad description
Part Design Workbench: the Part Design Workbench is a workbench for part design that aims to provide tools for modelling complex solid parts.

Good description
Part Design Workbench: aims to provide tools for modelling complex solid parts.

Templates
Styling of FreeCAD Wiki pages is mainly achieved through the usage of templates. The table here below reports the templates that should be used in FreeCAD Wiki pages. Please use the templates listed below as much as possible, since these allows to re-style the whole Wiki in one shot by updating the template, and is the preferred method in the Wiki. For special cases only you can resort to direct HTML tags.

Remark: you can see the complete list of defined templates accessing Special:PrefixIndex/Template:. However, not all the templates defined here are used for styling the text, and others are deprecated. Please refer to the table below for the list of templates you should use when documenting FreeCAD in the Wiki.

To have a global view on the chromatic aspect, see Basic Graphic Template.

Code
Code must be styled using the Code template.

Code description should follow the text box generated by the Code template, so that the description is structured according to the content. Accentuation should be strictly used only on the word or lines that must be accentuated.

Example of good code description

 * Creates an angular Dimension from the given center, with the given list of angles, passing through p3.
 * Returns the newly created object.

General
Avoid thumbnails whenever possible. Pictures should be shown in their original size, to avoid the need for the user to continuously navigate back and forth between different pages. Most important even, in the automatically generated printed manual (e.g. pdf version), thumbnails may not be readable. Thumbnails should be used only as last resource.

For the same reason, you should avoid animated pictures (i.e. gif). Animation should be reserved for tutorials not intended to be read as static content (e.g. video).

Pictures must be uploaded through the Special:Upload page.

Screen capture
Recommended size for screen captures, to avoid any resizing when showing the picture, should be:
 * native 400x200 (or width=400 and height<=200), for Gui Command pages, to allow the picture to fit in the left part of the page, and for other standard snapshots
 * native 600x400 (or width=600 and height<=400), for Gui Command pages, when you really need a bigger picture, and still allow the picture to fit in the left part of the page, and for other standard snapshots
 * native 1024x768 (or width=1024 and height<=768), only for full screen images
 * Smaller sizes are possible when showing details, however use native resolution, not resizing or thumbnails, unless you have a very good reason to do so.
 * Avoid larger resolutions, as they won't be much portable to any kind of display or in printed (pdf) documentation.

If possible, you shouldn't depend too much on any OS. While of course achieving 100% independency from the underlying OS is not possible, you should use visual defaults whenever possible.

Text
To ease documentation translations, if you put a screenshot showing the interface, you should not show the 3D model view in the same screenshot. In this way, the translator will not have to hunt for the model used to create the screenshot, and can simply take a screenshot of the localized interface. If there are drop down menus in the taskbar, the options should be listed in the text content.

If your screen capture contains text (e.g. a menu), use the same resolution of the original interface item in FreeCAD. This avoids to have images containing very large or very small text, and keeps the same look and feel of the FreeCAD native interface.

Bad picture text dimension


In this picture, note that the text dimension is acceptable, but there still are visual artifacts due to rescaling (the original width is 307px, rescaled to 190px) You should use native resolution to avoid visual artifacts due to rescaling.

Icons and graphics
Refer to this page for ready-to-use Artwork and Icon creation rules.

Models
The following pages contain models for FreeCAD documentation.


 * GuiCommand_model
 * Boiler_NonCommand

Translations
As per general consensus, the reference page is the English page, that should be created first. Moreover, if you want to change or add content in a page, you should do it in the the English page first, and only once the update is completed, port the modification to the translated page.

The FreeCAD wiki supports a Translation plugin which allows to manage translations between pages.

For details on translation, see FreeCAD Wiki Translation Process under Localisation.

Other useful resources are:
 * Language Codes: http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
 * Country Flags: http://en.wikipedia.org/wiki/Gallery_of_sovereign_state_flags
 * Google Translate: http://translate.google.com/

Setting Docnav
See this link in the forum: http://forum.freecadweb.org/viewtopic.php?f=21&t=6716

Using special pages

 * Orphaned pages list those pages that are not linked from or transcluded into other pages in FreeCAD Documentation. These pages are not accessible via links (no one sees them). If you find in your native language, try to create the connection that exists in the English page, otherwise no one can read them.
 * Uncategorized pages pages without category. They do not appear when you browse the categories. Assign a category.
 * Wanted pages pages that are called, but that do not exist. Red link in the texts. Deprecated and very annoying.
 * Others Wanted (files and templates)
 * Wanted categories they exist always, not only has been edited text. Skip.
 * Categories allow you to compare the number of pages of a given type of the original version with those translated into the specified language.
 * List of redirects allows you to control the correct redirection pages. If there are any red links, something does not work well. Investigate. Light blue links lead to pages outside the site, no problem.
 * Recent changes track the most recent changes to the wiki.
 * Language statistics shows translation statistics for all message groups for a language. Shows the parts not translated in a given language, only for those pages marked for translation. To see what has not been translated, set the language code and press Show statistic. It also contains the link to see what has been recently translated into that language. Note: If entering code en pages appear, it is likely that the original page contains markup errors (Sidebar apart).
 * Page translation allows you to see all the pages marked for translation, but also the updated and unmarked pages. Only administrators can mark pages for translation.
 * Category:Pages to delete: list of pages to be deleted, created by mistake or unnecessary.

Robots
At the page WikiRobots you can find instructions on how to set-up and use robots to automate repetitive tasks on the FreeCAD Wiki.

Discussion
The Forum provides a dedicated section for discussing documentation wiki topics. Direct your questions there.

Workflow, Roadmap
Organize pages in the wiki

Content and Appearance:

 * Renato: width of the page, now much space is unused (only for monitor 16:10)
 * Renato: white background, text more readable
 * Renato:  links to similar commands, similar tools, scripts, examples, discussions, insights, forum, other... On all pages or only on some pages?

Templates
I think the things like this are also templates? This template contains headlines, icons, short textual description, long textual description, list elements. May be easier to handle when splitted in pieces (at least: icon list, description list, "full featured": array of someWorkbenchTools[icon|description,{2-4}]...) ?


 * Basic Template that would be useful

* PartDesignTools * _______________
 * Other Template

Forum
Some useful examples taken from the forum
 * Reflect on requests for help made ​​in the forum and use the given examples (if it is required an aid often means that the manual is not exhaustive, in the forum there are good examples, but hard to find)
 * Renato: Insert a link on the document page or insert the example or insert nothing?
 * Ralf: insert link(s) always in a field/area which is always there on every page. If there is nothing to link, there should be a text in this area as "There is currently no link to forum examples."
 * Ralf #2 examples: no examples at pages which are describing more than exactly the use of (probably mostly) a tool. If there would be examples (at different pages) which differ in various ways and are not comparable are confusing.
 * Ralf #3 examples: But beside of existing examples: defining a "standard model" (or some of them if needed for fairly different tasks as p.e. Part-Design vs. Arch) for really every example would promise a lot of advantages. The first one: if one like to try an example the related model file is available right there with the next click. Whatever the "standard model" could be - the most important condition it have to be usable for all examples/task from to simplest up to the most complex (FEM,assembly?!)
 * May be such an standard model and his incarnations could be also a kind of a "figurehead" for FC.
 * Ediloren (talk) 18:01, 3 September 2013 (CEST) : looks like a good idea but not too practical; I expect that the burden of adding examples for everything would be very high. I would prefer to resort on tutorials, videos, and forum unless somebody has really the time and commitment to follow this part (me not, sorry :) )

Documentation structure:

 * Links between pages (tree and hierarchy linear, orderly, full)
 * Renato: If there is an index the docnav does not serves.
 * Page titles descriptive
 * Renato: Translated or not translated? With the new translator seems outdated
 * Structure of the documentation (depending on the type of user and the type of documentation). Group some things? - If possible in any way: group everything to maximal seven (7) entrys (per group)(Ralf).:
 * Reference (needs indicate precise criteria) (Ralf: for me for advanced users/using, #3)
 * How to (Ralf: additional, #4)
 * Tutorial (Ralf: additional, #5)
 * External links
 * Themed (Ralf: 1st thing / start point while using the documentation? - for me #1)
 * examples - in relevant cases - the most basic example for using the tool / workbench /feature (is that possible with complex tools?) ; may be one "standard" example case for the most examples, if possible (so the fcstd file can be supplied and re-used for a lot of uses) for me #2 or to #1
 * linear (all, as now)
 * structured with sub-structures (very clear if there are no more than 5..7 entrys per structure layer)
 * task - specific (features is other than transform than handle mouse etc.)
 * FAQ
 * Books
 * Plugins
 * Macro

Documentation schemes
See Documentation schemes

Repository

 * fcstd file
 * pics, images
 * icons (there are almost all)
 * "Show your FreeCAD projects here!" archives

Who are the users:

 * New users FreeCAD:
 * Users without CAD experience -> not the job of the FreeCAD doc to teach them CAD - the job to teach them how to use FreeCAD? Renato: I think that FreeCAD is currently the only free CAD program with a professional approach. Many people exactly look for this to begin.
 * Users with CAD experience (2D/3D/parametric); users with 3D experience - no CAD
 * Users who know how to program (version?)


 * Users who know FreeCAD:
 * Users
 * Advanced users
 * Developers

What the users needs:

 * According to the category of the previous point they need different things (to be determined).
 * Renato: In my opinion the beginners to FreeCAD (or to CAD?) needs:
 * find the information immediately + Ralf: in the expected, consistent way
 * know what are the workbenches, when and how to use them, + Ralf: is this one workbench all I need or do I need more than one?
 * the commands that are available, + Ralf: in the workbench - for the task - all
 * the workflow to use, - Ralf: workflow sounds specific - may be the most basic way to use this - may be especially for tools there could be more than page per tool (as above: basic for beginners, extended use for advanced users)

Translations
''- The wiki, is the best way to create documentation FreeCAD? Would not it be better to reserve it for some issues and create a comprehensive manual for each version?'' ''- About updates, this is a crucial point, I've seen that you do not like docboock, and I do not intend to return to this theme, but docboock allows translators to easily work on documents. Allows you to download the entire document and compare it with the previous one. With this way changes are made always and only in the original document. Then the translators periodically (even daily if they want) downloading the document and compares with an earlier version and update it indicating the upgrade version. I've experienced that this procedure is very good. Can I do a similar thing with the wiki? In this way there is no need to continuously monitor Recent Changes and updates are easier to control.''
 * Consistent (the reference page is the English page, see the various discussions regarding the rules in the forum)
 * Updated (how?) + Ralf: 1st: Version, 2nd: frozen state of doc page - "this is the actual version of the documentation of ... for FC version xxx"; 3rd linked archiv pages of other versions (and maybe other frozen states), all with corresponding "tags" / marks
 * Use a document type that including at least one complete section of the manual (not just one page at a time). Comparable off line with an previous version. With "Recent changes" is difficult to follow all the changes, when they are frequent.
 * FCSTD files for Documentation (wandererfan wrote: It would be nice to have a repository for the fcstd files +Ralf and it would be very helpful - used to generate screenshots, etc. Then the 2nd author/translator could just open the fcstd with a different locale to generate the new screenshot. This would also for standardization of background colours, font sizes, etc. )
 * Renato. My personal:

Some notes taken from the forum
yorikvanhavre wrote: Actually we could do a little brainstorming, see things that should be changed on the wiki... I already thought of a couple of things: - a new wiki homepage with a clear view of the contents - better formatting of the 3 principal sections, for user (basically the command pages), for power users (everything about python) and the higher-level stuff (compiling, etc) - more professional aspect of the wiki pages - build a better and more strict model for command pages - find a good system to handle translations

gdo wrote: But maybe a survey to freecad users could help to understand precisely what is the beginners needs.

Ralf wrote: Even for the ones who are trying FreeCAD the first times, it's essential to find a consistent documentation otherwise they weren't motivated to give even some first tries.

And many more ... dispersed and mixed in:
 * SF hosted app retairement & call for help
 * doc - some detail questions about changing, display, structure: Misalignment of ToC (left menu vs. ToC and page titles), links should be called as the pages
 * wiki pages: Best pages examples (long) discussion, propose to establish clear rules, minimize screenshots, don't use thumbnails, English pages are master, Navigation bar at the bottom like in Sketcher_Point (my view: no; use ToC), image dimensions, misalignment of ToC (Each information is linked to an index directly from the main page. The main menu expands into sub-menu. You can clearly see the hierarchy of the entire document. The documentation must be so.), how to manage docs for different FC versions, (OT: is there a timeout for editing a post? On-again some of my posts are lost in space)
 * Online Help (Wiki) TODO List: Misalignment and importance of ToC (it is what gets in FreeCAD Help), grouping of workbenches (alphabetically says normandc) topic left in April 10
 * Wiki for New Functions?: How to mark versions in the Wiki
 * Règles a suivre pour le nouveau wiki
 * Tutorials auf Deutsch für FreeCAD

Examples of CAD documentation
http://help.solidworks.com/2013/English/SolidWorks/sldworks/c_Sketch_Fillets.htm?id=cb1f4dfbe23245aeb58d17af808ee10c#Pg0

Ralf: good: you can see where you are ; bad: a huge lot of entrys in the navigation / summary at left - the opposite of structured; sorry: pieces of the forum at the documentation page: what is the documentation page good for than? (but the link to the forum / forum search - ok.) http://www.gcad3d.org/ Ralf: thumbs up. clear, well structured. sometimes long but I don't know how to avoid that at some themes. Maybe the tree structure layers could be separated in two directions at the page for more place for the content. They have "last updates" I prefer "this version of the documentation is xxx and depend the program version xxy"

Reported by wandererfan guidelines for wiki authors: http://wiki.blender.org/index.php/Meta:Guides/Writer_Guide http://wiki.blender.org/index.php/Meta:Guides/Style_Guide Manual TOC: http://docs.gimp.org/2.8/en/ http://wiki.blender.org/index.php/Doc:2.6/Manual

Reported by Ralf: http://opensourceecology.org/wiki/FreeCAD

For the Italian translation also: http://tp.linux.it/

Next actions

 * 1) gather ideas
 * 2) build Table of Contents
 * 3) build good models (in the template created by Wandererfan)
 * 4) edit the master page in English (updated until a new FreeCAD version is released then freeze the document in pdf or doc or other)
 * 5) translate (updated until a new FreeCAD version is released then freeze)
 * 6) continue to develop the documentation for the new version of FreeCAD (repeats 4)
 * 7) continue to develop the translation for the new version of FreeCAD (repeats 5)

English
See Glossary

Other languages

 * Italiano

proposal to create the page:

Start Center
When you start FreeCAD for the first time, you are presented with the start center:



The Start Center allows you to quickly jump to one of the most common workbenches, open one of the recent files, or see the latest news from the FreeCAD world. You can change the default workbench in the preferences.

Use this part of Getting started then add more information

=Sandbox Macros recipes=

Geometries

 * Rectellipse
 * Circle 3 Points
 * Draft Circle 3 Points
 * Draft Circle 3 Points 3D
 * Ellipse Center+2Points
 * Line Length
 * Circle
 * Triangle AH
 * Bounding Box
 * Involute Gear
 * Wire XYZ
 * Helix Variable
 * Repro Wire
 * Apothem Based Prism GUI

Solids

 * Make Cube

Shapes

 * Solid Sweep
 * Screw Maker 1_2
 * BOLTS
 * Parts Library
 * Stairs
 * Gear

Support

 * Arch Axis System Repartition
 * Work Features

Other

 * Geodesic Dome
 * Airfoil Import & Scale
 * Texture
 * Circular Text
 * Geneva Wheel
 * Geneva Wheel GUI
 * Cabinets 32
 * Half-Hull

Geometries

 * Cut Line
 * Cut Circle
 * Repro Wire

Transformation/conversion

 * Array Copy
 * Flatten Wire
 * Mesh To Part
 * Joint Wire
 * Remove History
 * Super Wire
 * Heal Arcs
 * Face to Sketch
 * Edges to Arc
 * Clone Convert
 * Faces from DXF

3D View operations

 * Rotate View
 * View Rotation
 * Texture Objects
 * Mouse Cross
 * Align View to Face
 * Align Object to View
 * Align Face Object to View
 * Camera
 * Select Visible

Wizards

 * Sheet Metal Unfolder
 * Unroll Ruled Surface
 * Unfold Box
 * Geneva Wheel GUI
 * Apothem Based Prism GUI

Info

 * Message Box
 * Info
 * Info Linux
 * Info Glass
 * Delta XYZ
 * Center Face
 * Object Info
 * Macro Menu
 * Dump Objects
 * Highlight Common
 * Highlight Difference
 * Select Visible

Multifunction

 * Work Features

System

 * Force Recompute
 * Remove History
 * 3D Printer Slicer
 * Shake Sketch
 * Replace Part
 * Manage Navigation Style
 * Toggle Views Visibility
 * Python Assistant Window
 * Build Utility
 * Global Variable Watcher
 * Property Memo
 * Plugin Manager

Import/Export

 * Airfoil Import & Scale
 * Faces from DXF
 * Export to Kerkythea

Mathematical functions

 * 3D Parametric Curve
 * Draw 2D Function
 * Draw Parametric 2D Function

Animation

 * Crank Simul
 * Spring
 * Hinge
 * Assembly
 * Animated Constrain
 * Assemblage Imprimate 3D

Arch

 * Arch Axis System Repartition

Raytracyng

 * Export to Kerkythea

FEM

 * GMSH

Drawing

 * Automatic Drawing
 * Corner Shapes Wizard
 * Cartouche
 * Cartouche Full
 * Cartouche 2
 * Get Normal Vector of Face

Workbenches experimental

 * Lattice
 * DDim

Creation
= Sandbox for Macro Dimensions =

Description
Macro for easy add dimension to Draft ... objects ...



Links

 * Discussion in the forum