-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
33 lines (32 loc) · 1.78 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<!DOCTYPE html>
<html>
<head>
<title>UFS Public Release Documentation</title>
<!-- link to main stylesheet -->
<link rel="stylesheet" type="text/css" href="/css/main.css">
</head>
<body>
<div class="container">
<div class="blurb">
<h1>UFS MR Weather App Documentation</h1>
<p>Here you can find Users's Guide for various applications, links to external documentation,
links to the development repository, and access to the UFS Portal</p>
</div><!-- /.blurb -->
</div><!-- /.container -->
<p>In the list below, you see 3 types of links: 1) from HTML stored in ufs-weather model-repository, branch gh-pages;
2) from HTML stored in github.io; 3) link to external documentation.</p>
<p> At this time, my recommendation is is to put the documentation close to the code,
so put the HTML in ufs-weather model-repository, branch gh-pages.
If we want to have different versions of documentation (e.g., release 0.1, 1.0, etc.,
we put the HTML in different subdirectories).
Note that he branch must be called gh-pages (we cannot change this name). The other alternative is to put
the HTML in ufs-weather-app master, subdirectory docs. But I think the gh-pages branch may be a better solution".
At any rate, the source code for documentation will be in the ufs-weather-app repo".</p>
<li><a href="/ufs-weather-model/index.html">User's Guide from HTML in ufs-weather-model repo, gh-pages branch</a></li>
<li><a href="/UsersGuide_MRWapp_v0.1/index.html">User's Guide from HTML in github.io/UsersGuide_MRWapp_v0.1</a></li>
<li><a href="https://dtcenter.org/community-code/common-community-physics-package-ccpp/documentation">CCPP</a></li>
<li><a href="https://ufscommunity.org">Portal</a></li>
<footer>
</footer>
</body>
</html>