github/repo2html
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
repo2html/assets/templates/default.html

60 lines
2.5 KiB
HTML
Raw Normal View History

enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
<!DOCTYPE html>
<html lang="en">
<head>
remove some env vars; make output land in html/ CLONE-URL, TITLE, and H1 are no longer processed. instead, the user should modify the templates/default.html to their liking. the output used to be structured like this: target-html-directory/ +-- index.html +-- files.html +-- README.md.html +-- (all the other files) the output is now structured like this: target-html-directory/ +-- index.html +-- html/ +-- files.html +-- README.md.html +-- (all the other files...) this makes it so people who are hosting bare repos for cloning on static webservers will have only two new directory entries (index.html and html) in the bare repo directory, reducing the risk of clobbering something. finally, i tried something hacky with gitattributes to get an automatic version idenifier to show up. but it turns out this is not the git hash of the commit, but instead the hash of the blob for main.scm, which could remain the same across releases. doesn't hurt, so i'll look for a better approach in the future.
2022-12-18 12:59:59 -05:00
<title>git.example.com - {{ repository_name }}</title>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale-1.0, user-scalable=yes" />
<link rel="icon" href="data:," />
<meta name="description" content="{{ repository_description }}" />
<style>
body { margin: 0 auto; max-width: 700px }
pre, code { background-color: #ffd9df }
pre { overflow: scroll; padding: 15px 20px; white-space: pre }
a { color: blue }
nav a { margin-right: 10px }
hr { border: 0; border-bottom: 1px solid black; margin-top: 16px }
td { padding: 0em .5em; vertical-align: top }
footer { font-size: small; text-align: right }
add ¶ markers on hover on titles to make it easier to grab the permalink
2022-12-25 18:40:45 -05:00
/* permalinks */
only permalink-ify those that have links to interior ids
2022-12-26 11:09:48 -05:00
h1 a[href^="#"]::after, h2 a[href^="#"]::after, h3 a[href^="#"]::after, h4 a[href^="#"]::after, h5 a[href^="#"]::after, h6 a[href^="#"]::after { content: "¶"; opacity: 0; margin-left: .5em; }
h1:hover a[href^="#"]::after, h2:hover a[href^="#"]::after, h3:hover a[href^="#"]::after, h4:hover a[href^="#"]::after, h5:hover a[href^="#"]::after, h6:hover a[href^="#"]::after { opacity: 100; }
h1 a[href^="#"], h2 a[href^="#"], h3 a[href^="#"], h4 a[href^="#"], h5 a[href^="#"], h6 a[href^="#"] { text-decoration: none; }
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
</style>
</head>
<body>
remove some env vars; make output land in html/ CLONE-URL, TITLE, and H1 are no longer processed. instead, the user should modify the templates/default.html to their liking. the output used to be structured like this: target-html-directory/ +-- index.html +-- files.html +-- README.md.html +-- (all the other files) the output is now structured like this: target-html-directory/ +-- index.html +-- html/ +-- files.html +-- README.md.html +-- (all the other files...) this makes it so people who are hosting bare repos for cloning on static webservers will have only two new directory entries (index.html and html) in the bare repo directory, reducing the risk of clobbering something. finally, i tried something hacky with gitattributes to get an automatic version idenifier to show up. but it turns out this is not the git hash of the commit, but instead the hash of the blob for main.scm, which could remain the same across releases. doesn't hurt, so i'll look for a better approach in the future.
2022-12-18 12:59:59 -05:00
<h1>git.example.com</h1>
improved template variables for working with ForgeRoot
2023-01-08 12:27:39 -05:00
<h2>{{ repository_path_parent }}
{% if repository_path_parent %} / {% endif %}
{{ repository_name }}</h2>
<p>clone url: git://git.example.com/{{ repository_path }}</p>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
<nav>
{% if readme_file %}
remove some env vars; make output land in html/ CLONE-URL, TITLE, and H1 are no longer processed. instead, the user should modify the templates/default.html to their liking. the output used to be structured like this: target-html-directory/ +-- index.html +-- files.html +-- README.md.html +-- (all the other files) the output is now structured like this: target-html-directory/ +-- index.html +-- html/ +-- files.html +-- README.md.html +-- (all the other files...) this makes it so people who are hosting bare repos for cloning on static webservers will have only two new directory entries (index.html and html) in the bare repo directory, reducing the risk of clobbering something. finally, i tried something hacky with gitattributes to get an automatic version idenifier to show up. but it turns out this is not the git hash of the commit, but instead the hash of the blob for main.scm, which could remain the same across releases. doesn't hurt, so i'll look for a better approach in the future.
2022-12-18 12:59:59 -05:00
<a href="{{ relative_root }}{{ readme_file }}.html">about</a>
whoops forgot relative_root in the ersatz template
2022-12-16 12:58:30 -05:00
<a href="{{ relative_root }}files.html">files</a>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
{% else %}
remove some env vars; make output land in html/ CLONE-URL, TITLE, and H1 are no longer processed. instead, the user should modify the templates/default.html to their liking. the output used to be structured like this: target-html-directory/ +-- index.html +-- files.html +-- README.md.html +-- (all the other files) the output is now structured like this: target-html-directory/ +-- index.html +-- html/ +-- files.html +-- README.md.html +-- (all the other files...) this makes it so people who are hosting bare repos for cloning on static webservers will have only two new directory entries (index.html and html) in the bare repo directory, reducing the risk of clobbering something. finally, i tried something hacky with gitattributes to get an automatic version idenifier to show up. but it turns out this is not the git hash of the commit, but instead the hash of the blob for main.scm, which could remain the same across releases. doesn't hurt, so i'll look for a better approach in the future.
2022-12-18 12:59:59 -05:00
<a href="{{ relative_root }}files.html">files</a>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
{% endif %}
{% if license_file %}
whoops forgot relative_root in the ersatz template
2022-12-16 12:58:30 -05:00
<a href="{{ relative_root }}{{ license_file }}.html">license</a>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
{% endif %}
{% if issues_file %}
whoops forgot relative_root in the ersatz template
2022-12-16 12:58:30 -05:00
<a href="{{ relative_root }}{{ issues_file }}.html">issues</a>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
{% endif %}
whoops forgot relative_root in the ersatz template
2022-12-16 12:58:30 -05:00
<a href="{{ relative_root }}commits.html">commits</a>
<a href="{{ relative_root }}contributors.html">contributors</a>
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
</nav>
<hr />
move the decision about where to render the filename into the template
2022-12-26 13:38:04 -05:00
{% if source_file %}
<p id="file-path">{{ source_file }}</p>
{% endif %}
enable customizable jinja-like templates via ersatz! well this was a journey :) behavior when running `repo2html <output directory>` remains the same; we apply our internal sxml template as usual. to use ersatz templates, run like this: `repo2html <output directory> <template directory>` the program will look for a "default.html" file in that directory.
2022-12-16 12:28:55 -05:00
{{ content|safe }}
<hr />
<footer>
remove some env vars; make output land in html/ CLONE-URL, TITLE, and H1 are no longer processed. instead, the user should modify the templates/default.html to their liking. the output used to be structured like this: target-html-directory/ +-- index.html +-- files.html +-- README.md.html +-- (all the other files) the output is now structured like this: target-html-directory/ +-- index.html +-- html/ +-- files.html +-- README.md.html +-- (all the other files...) this makes it so people who are hosting bare repos for cloning on static webservers will have only two new directory entries (index.html and html) in the bare repo directory, reducing the risk of clobbering something. finally, i tried something hacky with gitattributes to get an automatic version idenifier to show up. but it turns out this is not the git hash of the commit, but instead the hash of the blob for main.scm, which could remain the same across releases. doesn't hurt, so i'll look for a better approach in the future.
2022-12-18 12:59:59 -05:00
<p>Generated by
<a href="https://git.m455.casa/repo2html/"
title="the repo2html git repo static renderer by m455 and pho4cexa">repo2html</a>
{{ repo2html_version }} using
<a href="http://wiki.call-cc.org/eggref/5/ersatz"
title="the ersatz Jinja2-like templating library by Ivan Raikov"
>ersatz</a> templates</p></footer></html>
Reference in a new issue Copy permalink