8893d483bc
giscus settings in `_config.yml` had al-folio repo specified by default. many users kept these defaults in their own repos, which resulted in getting comments from blog posts of different users posted to al-folio discussions. this is undesirable, since users lose control over the discussions in their blogs. this PR solves the issue: - first, we set `giscus.repo` to blank in `_config.yml`. if the field is kept blank, when the website is built locally, the user will see a warning saying that giscus comments are misconfigured. - second, we add a step to the `deploy` workflow that writes repository name to `giscus.repo` in `_config.yml`. that way, even if `giscus.repo` field is left black or set to an incorrect repo, it gets correctly populated at deployment time. other small changes in this PR are small stylistic adjustments.
28 lines
716 B
HTML
28 lines
716 B
HTML
---
|
|
layout: default
|
|
---
|
|
<!-- page.html -->
|
|
<div class="post">
|
|
|
|
<header class="post-header">
|
|
<h1 class="post-title">{{ page.title }}</h1>
|
|
<p class="post-description">{{ page.description }}</p>
|
|
</header>
|
|
|
|
<article>
|
|
{{ content }}
|
|
</article>
|
|
|
|
{%- if page.related_publications != null and page.related_publications.size > 0 -%}
|
|
{% assign publications = page.related_publications | replace: ", ", "," | split: "," | join: "|" %}
|
|
<h2>References</h2>
|
|
<div class="publications">
|
|
{% bibliography -f {{ site.scholar.bibliography }} -q @*[key^={{ publications }}]* %}
|
|
</div>
|
|
{%- endif %}
|
|
|
|
{%- if site.giscus and page.giscus_comments -%}
|
|
{% include giscus.html %}
|
|
{%- endif -%}
|
|
</div>
|