pk/atst
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove hello template

Browse Source
This commit is contained in:
Brian Duggan 2018-05-25 13:42:31 -04:00
parent b9de54d211
commit 7d9d61598d
1 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
templates/hello.html.to
View File

@ -1,37 +0,0 @@
{% extends "base.html.to" %}
{% block title %}
AT-AT
{% end %}
{% block content %}
<main class="usa-grid usa-section usa-content usa-layout-docs" id="main-content">
<h1>New JEDI Request</h1><br>
{% include 'nav-side.html.to' %}
<div class="usa-width-three-fourths usa-layout-docs-main_content">
<h2 id="details-of-use">Details of Use</h2>
<p class="usa-font-lead">
To use JEDI, we want to know more about your needs for cloud services. Please fill out the form regarding computation, storage, and usage.
</p>
<h3 id="application-details">Application Details</h3>
<p>These headings introduce, respectively, sections and subsections within your body copy. As you create these headings, follow the same guidelines that you use when writing section headings: Be succinct, descriptive, and precise.</p>
<h3 id="application-details">Computation</h3>
<p>These headings introduce, respectively, sections and subsections within your body copy. As you create these headings, follow the same guidelines that you use when writing section headings: Be succinct, descriptive, and precise.</p>
<h3 id="application-storage">Storage</h3>
<p>The particulars of your body copy will be determined by the topic of your page. Regardless of topic, it’s a good practice to follow the inverted pyramid structure when writing copy: Begin with the information that’s most important to your users and then present information of less importance.</p>
<p>Keep each section and subsection focused — a good approach is to include one theme (topic) per section.</p>
</div>
</main>
{% end %}