linking back to plan
This commit is contained in:
@@ -1,14 +1,18 @@
|
||||
{% load rowerfilters %}
|
||||
<div class="grid_2 alpha">
|
||||
<p>
|
||||
{% if timeperiod and rower %}
|
||||
<a class="button gray small" href="/rowers/sessions/{{ timeperiod }}/rower/{{ rower.id }}">Plan Overview</a>
|
||||
{% elif timeperiod %}
|
||||
<a class="button gray small" href="/rowers/sessions/{{ timeperiod }}">Plan Overview</a>
|
||||
{% else %}
|
||||
<a class="button gray small" href="/rowers/sessions">Plan Overview</a>
|
||||
{% endif %}
|
||||
</p>
|
||||
<div class="grid_2 dropdown alpha">
|
||||
<button class="grid_2 alpha button gray small dropbtn">Overview</button>
|
||||
<div class="dropdown-content">
|
||||
{% if timeperiod and rower %}
|
||||
<a class="button gray small" href="/rowers/sessions/{{ timeperiod }}/rower/{{ rower.id }}">Sessions Overview</a>
|
||||
{% elif timeperiod %}
|
||||
<a class="button gray small" href="/rowers/sessions/{{ timeperiod }}">Sessions Overview</a>
|
||||
{% else %}
|
||||
<a class="button gray small" href="/rowers/sessions">Sessions Overview</a>
|
||||
{% endif %}
|
||||
<a class="button gray small" href="/rowers/plan/{{ plan.id }}">Plan Overview</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_2">
|
||||
<p>
|
||||
|
||||
@@ -20,16 +20,6 @@
|
||||
<h1>Training Plan - {{ plan.name }}</h1>
|
||||
<p>This plan starts on {{ plan.startdate }} and ends on {{ plan.enddate }}. The training plan target is: {{ plan.target.name }} on {{ plan.target.date }}.</p>
|
||||
<p><a href="/rowers/editplan/{{ plan.id }}">Edit the plan</a></p>
|
||||
<p>Click on the plan cycles below to edit their names, start and end dates. The gray "filler"
|
||||
cycles are generated, adjusted and deleted automatically to ensure the entire plan
|
||||
duration is covered with non-overlapping cycles.
|
||||
Once you edit a filler cycle, it become a user-defined cycle, which cannot be deleted
|
||||
by the system.</p>
|
||||
<p>A good way to organize the plan is to think of micro cycles as training weeks. Macro cycles
|
||||
are typically used to address specific phases of preparation and to indicate the racing
|
||||
season and may span several months.
|
||||
Meso cycles can be used to group sequences of three to five light, medium and
|
||||
hard weeks. It is recommended to work from left to right, starting with the macro cycles.</p>
|
||||
</div>
|
||||
<div class="grid_4 alpha">
|
||||
<h2>Macro Cycles</h2>
|
||||
@@ -55,7 +45,12 @@
|
||||
{% if todays_date <= macrocycle.0.enddate|date:"Y-m-d" %}
|
||||
<p><a href="/rowers/macrocycle/{{ macrocycle.0.id }}">edit</a>
|
||||
/
|
||||
<a href="/rowers/deletemacrocycle/{{ macrocycle.0.id }}">delete</a></p>
|
||||
<a href="/rowers/deletemacrocycle/{{ macrocycle.0.id }}">delete</a>
|
||||
/
|
||||
<a href='/rowers/sessions/{{ macrocycle.0.startdate|date:"Y-m-d" }}/{{ macrocycle.0.enddate|date:"Y-m-d" }}'>sessions</a>
|
||||
</p>
|
||||
{% else %}
|
||||
<p> </p>
|
||||
{% endif %}
|
||||
</div>
|
||||
</div>
|
||||
@@ -72,8 +67,14 @@
|
||||
{% if todays_date <= mesocycle.0.enddate|date:"Y-m-d" %}
|
||||
<p><a href="/rowers/mesocycle/{{ mesocycle.0.id }}">edit</a>
|
||||
/
|
||||
<a href="/rowers/deletemesocycle/{{ mesocycle.0.id }}">delete</a></p>
|
||||
<a href="/rowers/deletemesocycle/{{ mesocycle.0.id }}">delete</a>
|
||||
/
|
||||
<a href='/rowers/sessions/{{ mesocycle.0.startdate|date:"Y-m-d" }}/{{ mesocycle.0.enddate|date:"Y-m-d" }}'>sessions</a>
|
||||
|
||||
</p>
|
||||
{% endif %}
|
||||
{% else %}
|
||||
<p> </p>
|
||||
{% endif %}
|
||||
</div>
|
||||
</div>
|
||||
@@ -91,8 +92,13 @@
|
||||
<p>
|
||||
<a href="/rowers/microcycle/{{ microcycle.id }}">edit</a>
|
||||
/
|
||||
<a href="/rowers/deletemicrocycle/{{ microcycle.id }}">delete</a></p>
|
||||
<a href="/rowers/deletemicrocycle/{{ microcycle.id }}">delete</a>
|
||||
/
|
||||
<a href='/rowers/sessions/{{ microcycle.startdate|date:"Y-m-d" }}/{{ microcycle.enddate|date:"Y-m-d" }}'>sessions</a>
|
||||
</p>
|
||||
{% endif %}
|
||||
{% else %}
|
||||
<p> </p>
|
||||
{% endif %}
|
||||
</div>
|
||||
</div>
|
||||
@@ -102,5 +108,23 @@
|
||||
</div>
|
||||
</div>
|
||||
{% endfor %}
|
||||
</div>
|
||||
</div>
|
||||
<div class="grid_12">
|
||||
<p>Click on the plan cycles to edit their names, start and end dates. The gray "filler"
|
||||
cycles are generated, adjusted and deleted automatically to ensure the entire plan
|
||||
duration is covered with non-overlapping cycles.
|
||||
Once you edit a filler cycle, it become a user-defined cycle, which cannot be deleted
|
||||
by the system.</p>
|
||||
<p>Filler cycles which have a filler cycle as a parent cannot be edited
|
||||
or deleted. You have to edit the parent cycle first. The reason is
|
||||
that children of filler cycles are not safe. They are deleted when
|
||||
their parent is deleted by the system.</p>
|
||||
<p>Click on "Sessions" in the cycle of your interest to see details
|
||||
of the individual training sessions planned for this period.</p>
|
||||
<p>A good way to organize the plan is to think of micro cycles as training weeks. Macro cycles
|
||||
are typically used to address specific phases of preparation and to indicate the racing
|
||||
season and may span several months.
|
||||
Meso cycles can be used to group sequences of three to five light, medium and
|
||||
hard weeks. It is recommended to work from left to right, starting with the macro cycles.</p>
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
Reference in New Issue
Block a user