--- a/index.html
+++ b/index.html
@@ -8,7 +8,7 @@
<body>
<div id="site-header">
<div class="wrapper">
- <a href="opensourceprojects.eu" id="header-logo"><img src="logo.png"></a>
+ <a href="http://opensourceprojects.eu" id="header-logo"><img src="logo.png"></a>
</div>
</div>
@@ -31,7 +31,7 @@
login-link and insert your username and password.
</p>
- <h2>Creating a Project</h2>
+ <h2>Project Management</h2>
<p>You can create new projects from the projects list (from the top menu under <b>Projects</b>)
This opens a list of projects available to you. To create one of your
@@ -53,20 +53,53 @@
</ul>
<p>
- With exception to the project name/url all these settings can be added at a later time. Afte creating you new project, you will be redirected to the project administration page.
- </p>
-
-
-
- <h2>Project Management</h2>
+ With exception to the project name/url all these settings can be added at a later time. After creating you new project, you will be redirected to the project administration page.
+ </p>
+
+ <h3>Installing new Tools</h3>
+
+ <p>
+ You can install new tools in your project from the <b>Admin/ Tools</b>
+ and clicking on the tool you want to install. The new instance will
+ need a Label (that shows up in the sidebar), and a Mount point (a path
+ in the URL)
+ </p>
+
+ <img src="img/itickets.png"/>
+
+ <h3>Creating subprojects</h3>
+
+ <p>
+ Sub projects are a common part of large projects that require
+ maintaining several tools and source code under a common group, such as
+ an ICT project. You can create sub-projects under the <b>Admin/ Tools</b>
+ selection.
+ </p>
+
+ <p>
+ You will be given two choices to create a sub-project: associate a sibling
+ project or create a new project as sub-project of the main one.
+ To achieve either of available options, it is necessary to navigate to
+ the main project's tools page
+ </p>
+
+ <p class="hint">Projects > ProjectName > Admin > Tools</p>
+
+ <p>and click to add a new Subproject tool. A form will pop up for you
+ to fill in the sub-project's information, such as its Label and its
+ Mount Point. The platform checks if the mount point already exists and
+ either associates the existing point as the main one, or creates a new
+ project with the specified title in Label and URL name. This
+ information is saved with the save button.</p>
+
+ <p>After the pop-up window is dismissed, the new Subproject tool will
+ be listed along with the other installed tools.</p>
<h2>Git</h2>
<h2>SVN</h2>
<h2>Issue Tracker</h2>
-
-
<div class="col1">
<p>
@@ -76,7 +109,6 @@
this section you get a rough overview of how tickets are configured in a
specific project and how end-users can take advantage of them.
</p>
-
<p>
Tickets are specific items that correspond to problems identified in the
@@ -102,8 +134,82 @@
<img src="img/feature-tickets.png"/>
</div>
+ <h3>Installing the Issue Tracker</h3>
+
+ <p class="col1">
+ You can install a new issue tracker instance from the <b>Admin/ Tools</b> and
+ clicking on the <b>Tickets</b> tool. The new instance that will need a Label (that shows up in the sidebar), and a Mount point (a path in the URL)
+ </p>
+
+ <p class="nocol">
+ After the tool is installed, you should see a new tool in the
+ <b>Tools</b> page and in the project sidebar.
+ Once installed, some configuration options become available in the Tool page.
+ </p>
+
+ <ul>
+ <li>Field Management
+ <ul>
+ <li>Allows administrators to configure how the fields in the ticket tracker appear.</li>
+ <li>There are several fields you can select from, that are most well suited for your project needs.</li>
+ </ul>
+ </li>
+ <li>Edit Searches
+ <ul>
+ <li>If you have a search that you want all users of the tracker to be able to share, you can save that search with a name and it will be placed in the left navigation bar of the tracker for everybody to use.</li>
+ <li>You can use these saved searches to watch the flow of tickets through the system and make it easier for your development team to focus on groups of active tickets.</li>
+ </ul></li>
+ <li>Permissions - Allows you to define the permissions for viewing and resolving tickets.
+ </li>
+ <li>Options
+ <ul>
+ <li>The default behavior of the Tickets tool can be modified here</li>
+ <li>Allows for voting tickets up/down, email notifications, and setting up customized help texts</li>
+ </ul>
+ </li>
+ </ul>
+
+ <h3>Using the issue tracker</h3>
+
+ <p>
+ With the appropriate permissions, users can create a new ticket using
+ the Create Ticket link in the left sidebar. At the new ticket form,
+ fill in a title, and any other appropriate fields, and an issue
+ description. To edit the main ticket description or fields on an
+ existing ticket, providing you have the permissions to do so, select
+ the EDIT button in the upper right of a ticket. If further discussion
+ about a ticket is needed, use the comment field at the bottom.
+ </p>
+
+ <p>
+ You can also move and delete tickets. This again depends on your
+ permissions on the particular instance.�� To move a ticket, select the
+ Move option in the upper right of the ticket view. To delete a ticket,
+ select the Trash Can icon in the upper right of the ticket view. This
+ ticket will now be "deleted", however it may still be "undeleted" if
+ you select the + icon which replaces the Trash Can icon. If a deleted
+ ticket matches a list view, there will be a "Show deleted tickets" link
+ which will allow you to see them.
+ </p>
+
+ <p>
+ Searching a ticket is also possible. The search uses Solr Lucene query
+ syntax. On any search page you will see a Help button that will show
+ the different searches available and some exact examples.
+ </p>
+
+
<h2 class="nocol">Wiki</h2>
+
+ <p>The wiki is a collaborative document editor which is easily edited
+ and can be used for various documentation needs, both internal and
+ external. By default any project developer can edit the project wiki,
+ but permissions can be regulated as you wish them to be available to
+ different user groups. Like most modern wikis, all edits are
+ non-destructive and a copy of every version is stored.</p>
+
+
<h2 class="nocol">Forum</h2>