Skip to content

Add an "Acknowledging or Citing SCALE" page - #18

Open
atsetilam wants to merge 5 commits into
masterfrom
docs/how-to-cite-scale
Open

Add an "Acknowledging or Citing SCALE" page#18
atsetilam wants to merge 5 commits into
masterfrom
docs/how-to-cite-scale

Conversation

@atsetilam

@atsetilam atsetilam commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

What

Adds an Acknowledging or Citing SCALE page, modelled on scikit-rf's equivalent page, and links it in the sidebar nav.

Notes for reviewers

  • ⚠️ The macros plugin runs pages through Jinja2 before Markdown, so the BibTeX block must stay wrapped in {% raw %} or the build breaks on the braces.
  • The BibTeX fields come from the publisher's Crossref metadata; page range uses LaTeX -- and S{\o}ndergaard is escaped for non-UTF-8 bibliographies.
  • Copy-to-clipboard comes free: the theme already enables content.code.copy, so every snippet gets a button.

Verification

  • mkdocs build --strict: clean.
  • The BibTeX entry as it appears in the rendered HTML (i.e. exactly what a reader copies) was parsed with a real BibTeX parser earlier in this branch's life and is byte-identical now; brace balance re-checked after the restructure.
  • No draft banner, TODO marker, or raw Jinja leaks into the built page.

Adds a citation page giving ready-to-copy BibTeX for the two SCALE
papers (HCDS '25 and Middleware '24, fields taken from Crossref) and for
the software itself, plus plain-text forms. Copy-to-clipboard comes free
from the theme's existing content.code.copy feature.

The page is a DRAFT: the proposed values are pending answers from the
team, and every open decision is marked with a TODO(cite-N) comment
matching the questions asked internally. It is therefore kept out of the
nav for now; re-enable the nav entry in mkdocs.yml once the TODOs are
resolved and the draft banner is removed.

Note for future editors: the macros plugin runs pages through Jinja2
before Markdown, so the {{...}} in BibTeX corporate-author fields must
stay wrapped in {% raw %} or the build breaks.
Use the tracked Discord short link and the .com contact address.
Keeps a single source of truth for the Discord URL.
@atsetilam
atsetilam force-pushed the docs/how-to-cite-scale branch from 0fc13c8 to 95553ff Compare July 15, 2026 10:48
Restructure along the lines of scikit-rf's "Acknowledging or Citing"
page, with "In Presentations or Apps" first: we care more about people
acknowledging that they use SCALE than about formal citations.

- Academic citations now point at the latest paper (HCDS '25) only.
- Drop the @software/@misc entries: the paper is the citation.
- Offer suggested "powered by" wording and invite people to ask us
  for logo assets.
- Remove the draft banner and the TODO markers; re-enable the nav
  entry and drop the page from not_in_nav.
@atsetilam atsetilam changed the title DRAFT: Add a "How to Cite SCALE" page Add an "Acknowledging or Citing SCALE" page Jul 15, 2026
@atsetilam
atsetilam marked this pull request as ready for review July 15, 2026 11:17
SCALE targets NVIDIA GPUs too, and portability is only one reason to
use it, so the example should not presume AMD or a porting use case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant