Merge pull request #38 from dod-ccpo/requests-persistence

Hook ATST up to the requests-queue
This commit is contained in:
richard-dds
2018-06-19 16:14:31 -04:00
committed by GitHub
14 changed files with 163 additions and 54 deletions

View File

@@ -5,8 +5,8 @@
<p class="usa-font-lead">Lorem ipsum dolor sit amet, consectetur adipisicing elit. Natus error omnis a, tenetur similique quo officiis voluptates eum recusandae dolorem minus dignissimos, magni consequatur, maxime debitis reprehenderit sint non iusto?</p>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form',next_screen) }}'>New Application</a>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form',next_screen) }}'>Existing Application</a>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form',next_screen) }}'>Sandbox Environment</a>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form_new',next_screen) }}'>New Application</a>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form_new',next_screen) }}'>Existing Application</a>
<a class='usa-button usa-button-secondary' href='{{ reverse_url('request_form_new',next_screen) }}'>Sandbox Environment</a>
{% end %}
{% end %}

View File

@@ -92,29 +92,25 @@
<h4 id="application-storage">Storage</h4>
<p>The particulars of your body copy will be determined by the topic of your page. Regardless of topic, its a good practice to follow the inverted pyramid structure when writing copy: Begin with the information thats most important to your users and then present information of less importance.</p>
<label for="">Object storage</label>
<input id="" name="" type="text" placeholder="Total object storage">
<label for="">Server storage</label>
<input id="" name="" type="text" placeholder="Total server storage">
{{ f.object_storage.label }}
{{ f.object_storage(placeholder="Total object storage") }}
{{ f.server_storage.label }}
{{ f.server_storage(placeholder="Total server storage") }}
<!-- Application Usage -->
<h4 id="application-usage">Estimated Application Storage</h4>
<p>The particulars of your body copy will be determined by the topic of your page. Regardless of topic, its a good practice to follow the inverted pyramid structure when writing copy: Begin with the information thats most important to your users and then present information of less importance.</p>
<label for="">Expected active users</label>
<input id="" name="" type="text" placeholder="Total active users">
{{ f.total_active_users.label }}
{{ f.total_active_users(placeholder="Total active users") }}
<label for="">Expected peak concurrent users</label>
<input id="" name="" type="text" placeholder="Total peak users">
<label for="">Expected requests per minute</label>
<input id="" name="" type="text" placeholder="Total requests">
<label for="">Number of application environments</label>
<input id="" name="" type="text" placeholder="Total number of environments">
{{ f.total_peak_users.label }}
{{ f.total_peak_users(placeholder="Total peak users") }}
{{ f.total_requests.label }}
{{ f.total_requests(placeholder="Total requests") }}
{{ f.total_environments.label }}
{{ f.total_environments(placeholder="Total number of environments") }}
{% end %}

View File

@@ -2,7 +2,7 @@
{% for i,s in enumerate(screens) %}
<li>
{% if i+1==current %}
<a class="usa-current" href="{{ reverse_url('request_form',i+1) }}">
<a class="usa-current" href="{{ reverse_url('request_form_update', i+1, request_id) if request_id else reverse_url('request_form_new',i+1) }}">
{{ i+1 }}. {{ s['title'] }}
</a>
{% if s.get('subitems') %}
@@ -14,10 +14,10 @@
{% end %}
{% else %}
<a href='{{ reverse_url('request_form',i+1) }}'>
<a href="{{ reverse_url('request_form_update', i+1, request_id) if request_id else reverse_url('request_form_new',i+1) }}">
{{ i+1 }}. {{ s['title'] }}
</a>
{% end %}
</li>
{% end %}
</ul>
</ul>