mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 15:22:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update wikipage How to contribute to documentation. (Signed-off-by:jocelyn).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1593 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2016-06-20 12:22:39 +00:00
parent 98aa52dd1c
commit a66715a719
1 changed files with 44 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

86
documentation/trunk/contribute/documentation.wiki
View File

@@ -1,42 +1,44 @@
[[Property:title|How to contribute to documentation]] [[Property:title|How to contribute to documentation]]
[[Property:link_title|To documentation]] [[Property:link_title|To documentation]]
[[Property:weight|2]] [[Property:weight|2]]
[[Property:uuid|A2DED192-B50A-4E59-B214-FDC3FEDC7A44]] [[Property:uuid|A2DED192-B50A-4E59-B214-FDC3FEDC7A44]]
= Current documentation system = = Current documentation system =
* The documentation is written using wikitext syntax (similar to wikipedia). * The documentation is written using wikitext syntax (similar to wikipedia).
* Each documentation page is stored in a wiki file on disk. * Each documentation page is stored in a wiki file on disk.
* Those files come from the subversion repository: [https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk] . * Those files come from the subversion repository: [https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk] .
* The outline of book are following the underlying directory structure, and each wiki file can have properties that hold metadata such as: * The outline of book are following the underlying directory structure, and each wiki file can have properties that hold metadata such as:
:<nowiki>[[Property:title|The page title]]</nowiki> <code>
:<nowiki>[[Property:link_title|short title]]</nowiki> [[Property:title|The page title]]
:<nowiki>[[Property:weight|5]]</nowiki> [[Property:link_title|short title]]
** '''link_title''' is used to have a short title in menu, or various links. [[Property:weight|5]]
** '''weight''' is used to order sibling pages (lower weight goes before, upper weight goes after). </code>
** '''link_title''' is used to have a short title in menu, or various links.
= To contribute = ** '''weight''' is used to order sibling pages (lower weight goes before, upper weight goes after).
* First, you can post comment on any page (see comment form at the bottom of each page).
* As one would contribute to any source maintained on a subversion repository, one can contribute via the repository [https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/] and provide patch. = To contribute =
* Note there is also a git mirror at [https://github.com/eiffelsoftware/eiffel-org] so you can also contribute via github by sending pull request. * First, you can post comment on any page (see comment form at the bottom of each page).
* As one would contribute to any source maintained on a subversion repository, one can contribute via the repository [https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/] and provide patch.
= Step by step with git = * Note there is also a git mirror at [https://github.com/eiffelsoftware/eiffel-org] so you can also contribute via github by sending pull request.
* Go to [https://github.com/eiffelsoftware/eiffel-org] for the project, then git clone on your machine.
* create a git branch. = Step by step with git =
* add or edit the files locally. * Go to [https://github.com/eiffelsoftware/eiffel-org] for the project, then git clone on your machine.
* once you want to share your changes. * create a git branch.
** git commit your changes. * add or edit the files locally.
** git push them to your github repository. * once you want to share your changes.
** then create a pull request so that the Eiffel.org documentation team can review and integrate the changes. ** git commit your changes.
* See current pull requests at [https://github.com/EiffelSoftware/eiffel-org/pulls]. ** git push them to your github repository.
** then create a pull request so that the Eiffel.org documentation team can review and integrate the changes.
= Step by step with subversion = * See current pull requests at [https://github.com/EiffelSoftware/eiffel-org/pulls].
* <code>svn checkout https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/</code>.
* add or edit the files locally. = Step by step with subversion =
* once you want to share your changes. * <code>svn checkout https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/</code>.
** svn update. * add or edit the files locally.
** Send the patch via [https://codereview.appspot.com/]. (note: follow the instructions from codereview site, you will need to use a python script "upload.py" distributed by the codereview site). * once you want to share your changes.
* See current patches at [https://codereview.appspot.com/search?base=https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/]. ** svn update.
** Send the patch via [https://codereview.appspot.com/]. (note: follow the instructions from codereview site, you will need to use a python script "upload.py" distributed by the codereview site).
= Live editing on this site = * See current patches at [https://codereview.appspot.com/search?base=https://svn.eiffel.com/eiffel-org/trunk/documentation/trunk/].
* If you are a trusted editor, you can edit the documentation directly.
* To be a trusted editor, please request it via the [/contact] page (do not forget to mention who you are and why you think you should be a trusted editor). = Live editing on this site =
* If you are a trusted editor, you can edit the documentation directly.
* To be a trusted editor, please request it via the [https://www.eiffel.org/contact contact] page (do not forget to mention who you are and why you think you should be a trusted editor).