Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 65 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@ Interlisp and how to access and use the restored Medley system.
- [Content Authoring](#content-authoring)
- [Editing Existing Pages](#editing-existing-pages)
- [Adding New Pages](#adding-new-pages)
- [Social Share Images and Metadata](#social-share-images-and-metadata)
- [Structured Data (JSON-LD)](#structured-data-json-ld)
- [Meta Descriptions](#meta-descriptions)
- [Adding or Updating the Comments Page](#adding-or-updating-the-comments-page)
- [Bibliography Data](#bibliography-data)
- [Local Development](#local-development)
Expand Down Expand Up @@ -120,6 +123,63 @@ type: docs

The content follows the preamble and is written using [Markdown](https://www.markdownguide.org/tools/hugo/).

### Social Share Images and Metadata

When a page is shared on social platforms (Bluesky, Mastodon, Facebook, LinkedIn, Slack, etc.), the preview card is built from the page's Open Graph metadata. Docsy generates these tags automatically, so authors normally don't need to do anything.

- **Default image:** `config/_default/params.yaml` sets `images: [images/og-default.png]`, which is used for every page that does not specify its own. The image lives at `static/images/og-default.png` and is 1200x630 px.
- **Per-page override:** add an `images` list to the page front matter. Place a 1200x630 px image under `static/` and reference it site-relative:

```markdown
---
title: Medley Goals
weight: 10
type: docs
images: ["images/medley-goals-share.png"]
---
```

- **Alt text:** the `og:image:alt` and `twitter:image:alt` values are generated from the page title automatically (see `layouts/_partials/hooks/head-end.html`).
- **Mastodon attribution:** `config/_default/params.yaml` sets `fediverse_creator: "@interlisp@fosstodon.org"`, which is emitted as a `fediverse:creator` meta tag so Mastodon (4.3+) credits the project account on shared links. Override per page with a `fediverse_creator` front matter value if needed.

Bluesky and Mastodon build their previews from Open Graph tags only (they ignore `twitter:*`). Mastodon caches a card per status, so edit or repost to refresh it. Bluesky generates the card when a post is composed, so metadata changes only affect new posts.

### Structured Data (JSON-LD)

The site emits [schema.org](https://schema.org) JSON-LD so search engines can show rich results (article cards, breadcrumbs). The partials live in `layouts/_partials/` and are wired into `layouts/_partials/hooks/head-end.html`; each one guards itself, so authors normally don't need to do anything.

| Schema | Where it appears | Source partial |
|--------|------------------|----------------|
| `Organization` | Home page only | `schema-organization.html` |
| `Article` | Every content page (not bibliography entries or sections) | `schema-article.html` |
| `BreadcrumbList` | Every page except the home page and 404 | `schema-breadcrumb.html` |
| Bibliography types | `content/en/history/bibliography/**` | `bibliography-json-ld.html` |

- **Article metadata** is derived automatically: `headline` from the title, `description` from the page description, `datePublished` from `date`, `dateModified` from the file's last git change (`enableGitInfo: true`), and `author`/`publisher` from `site.Params.author`.
- **Validate locally** with the test suite (`tests/test_site_jsonld.py`) and, before release, with Google's [Rich Results Test](https://search.google.com/test/rich-results).

### Meta Descriptions

The `<meta name="description">` tag is generated for every page by `layouts/_partials/page-description.html`. It is what search engines may show beneath a page title in results, so it should be a clear, compelling summary that includes the page's main topic.

**Authoring rules:**

- Add a `description:` field to a page's front matter. Aim for **150–160 characters** (about one to two sentences).
- Make it **unique** — avoid reusing the same text across pages.
- Describe what the reader will find and include the primary keyword naturally. Do not stuff keywords or simply repeat the title.

```markdown
---
title: History
description: "Explore the history of Interlisp, the pioneering Lisp software development environment born at Xerox PARC in the 1970s and 1980s."
---
```

**Fallback behavior** (when a page has no `description:`): the partial uses, in order, the page's `description`, then its auto-generated summary, then a generated description (for bibliography, taxonomy, and term pages), and finally the site-wide default from `config/_default/params.yaml`. Any description longer than 160 characters is truncated at a word boundary. Relying on the fallback is fine for minor pages, but hand-written descriptions are strongly preferred for anything in the navigation.

- **Bibliography entries** are described automatically from the entry's title and abstract (or authors); you do not need to add `description:` to generated entries. Hand-written pages that merely live under the bibliography tree (e.g. `intake/`, `zotero-resources/`, which set `type: docs`) are *not* generated entries and still need their own `description:`; the test identifies generated entries from the rendered `class="bibliography-entry"` marker rather than the URL.
- **Validate locally** with `tests/test_meta_descriptions.py`.

### Adding or Updating the Comments Page

The *comments* page ("What people are saying") collects quotes and screenshots that discuss Medley Interlisp. We preserve Twitter and Mastodon posts as images along with links to the post to protect against content being deleted from social platforms.
Expand Down Expand Up @@ -460,6 +520,11 @@ gcs_engine_id: 33ef4cbe0703b4f3a

Search results are rendered using the `search.html` layout template.

The search page is intentionally kept out of search-engine indexes: `robots.txt` disallows
`/search/`, and `content/en/search.md` sets `robots = "noindex"` (which also excludes it from the
sitemap). The page is a thin wrapper around the Google Custom Search widget with no content of its
own.

**Updating Search:**

Modifying search scope requires updating the Google Custom Search engine settings via the [Programmable Search Engine Dashboard](https://programmablesearchengine.google.com). Access is restricted. To suggest changes, open an issue: [Search Engine Issue](https://github.com/interlisp/medley/issues/new?template=bug_report.md&title=Search_Engine_Issue)
Expand Down
5 changes: 5 additions & 0 deletions archetypes/default.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,10 @@
title: "{{ replace .Name "-" " " | title }}"
date: {{ .Date }}
draft: true
# Optional: override the default social share image (Open Graph / Twitter Card).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the AI policy should state something like "PRs that include either text or code that was generated by AI or LLM should state clearly and plainly at the top that they were AI generated. No PR that was AI generated should be approved by anyone without explicit accomodation for review for slop. "

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a draft PR because I'm not comfortable with the content yet - but, by pushing it and creating a draft PR I can leverage the staging site and see and kick the tires. That said, comments are welcome, it will help me focus my efforts and test my assumptions.

As far as AI policy - you're welcome to use my draft PR to poke at what it should be. But, I suspect the audience is much more limited than we need to define the actual policy.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As an aside, one of the things I try to do when using AI is have it create an implementation plan. Something I can review prior to doing any actual work, modify or ask clarifying questions. And, as I proceed with AI assisted implementation, I have it update the document with the completed work and any findings. My selfish goal is to keep enough of a record so when I put things aside for multiple weeks I can quickly reset my context -- and the AI's context.

I currently keep those local. I've wondered if it might be worthwhile adding them to the repo. For instance all the work in this PR represents one phase of a plan. There is additional work that can be done to improve SEO, but the effort vs payoff is less clear. This is all low effort, low risk work that ideally improves the site.

That would help provide more context to the work - allow others to comment or provide direction and create a history of how we've used AI (hopefully for better).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idea: for AI work, instead of putting into the repository the "implementation plan" (or even just the sequence of input "prompts"), requiring that information to be documented in the PR might be sufficient, and avoid repo-clutter.
In any case, the PR must describe how AI was used, e.g.:

  1. AI just for debugging handwritten code
  2. AI for analysis, but no AI code in final deliverable
  3. Full AI implementation from prompts
  4. AI translation of (external) existing code from another programming language
  5. etc.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really want to allow merging AI content to the core Medley repos? As this article notes from the experience of open source projects, the only effective AI policy is totally restrictive, as allowing any form of AI (disclosure, human review, and so on) inevitably leads to AI contributions dominating the project and fundamentally changing the nature of the system.

I also think allowing AI code in Medley is not a good fit for a history project, for the reasons I explained in issue Interlisp/medley#2612. The reason I suggest such caution is that, while a permissive policy is largely irreversible, a restrictive one has essentially no drawbacks.

@stumbo stumbo Nov 13, 2026 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MattHeffron I think just listing the input prompts is oversimplifying the interaction. Currently, I've been experimenting with OpenCode as a tool to wrap my AI interactions, Big Pickle and Claude as models. I also have a couple plugins and one MCP server to assist the AI. One provides rules that limit what the AI can do or access, one helps clean the context and limit token usage and the MCP server uses mermaid for diagramming. This piece of work started with one simple prompt:

Review Interlisp.github.io. It is a Hugo website. I'd like to put together a list of task to improve Search Engine Optimization.

Followed by:

Let's write out the plan so we can tract progress against it. Place the plan in the docs folder.

I gave those prompts to Claude. I then switched to Big Pickle and asked it:

Review the SEO_Improvement_Plan in the docs folder. Validate that the plan is correct.

Which yielded a few points where it pointed out issues in the plan - mostly things that already existed that Claude neglected to catch.

Yes, revise the Specification.

The resulting plan has four phases: Phase 1 (social share images, JSON-LD, meta descriptions, robots.txt), Phase 2 (content/keyword strategy), Phase 3 (technical / Core Web Vitals), and Phase 4 (monitoring).

This PR is all centered around Phase 1 - the social share is the most iffy part of this PR, is it really necessary? My social media usage is minimal so I am a poor judge. The JSON-LD and meta descriptions are important, I want to do as much as I can to make the website more usable in searching (this ties directly to my long term interest of AI assisted search) and the robots.txt is a minor cleanup issue.

What I will include in the PR once I move it out of draft is a much more verbose description of the changes. I'm fine with specifying that this work was greatly assisted/driven by AI. I also know that in the end, the responsibility for the code falls on my shoulders.

# Place the file under static/ and reference it site-relative, e.g.:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean? "Optional"? FOr what? For whom?
What is an Open Graph / TWitter Card?

Is this just a comment?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open Graph and Twitter Card -- these are tags that get inserted into the pages html that are supposed to help improve the appearance of the page IF it is shared via Twitter/X (Twitter Card), LinkedIn, BlueSky (Open Graph).

The comments allude to being able to redefine default values - likely of little interest, I wasn't sure I wanted to delete them yet. The potential interplay with params.yml isn't clear to me and I left these here until I better understand it.

# images: ["images/my-share-image.png"]
# Optional: override the Mastodon fediverse:creator attribution for this page.
# fediverse_creator: "@interlisp@fosstodon.org"
---

12 changes: 10 additions & 2 deletions config/_default/params.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,16 @@
# Set Google Analytics to use GA4
disableGtagForUniversalAnalytics: false

# First one is picked as the Twitter card image if not set on page.
# images = ["images/project-illustration.png"]
# Default social share image (Open Graph / Twitter Card).
# The first entry is used when a page does not set its own `images` front matter.
# Recommended size: 1200x630 px. Served from static/, so the path is site-relative.
images:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we were not going to support twitter anyway

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We aren't -- one of the updates is to add support for Twitter/X users that share our pages. While this may be a tails case, I thought the overhead was small. The goal is that when an Interlisp.org site is shared it that instead of just a url, you get an image, which should look like this:

image

There is supposed to be a way of testing -- one of the reasons I wanted to stage this, so I can give the test tools real live websites and see what really happens.

- images/og-default.png

# Mastodon (4.3+) attribution for shared links. Emitted as
# <meta name="fediverse:creator"> by layouts/_partials/hooks/head-end.html.
# Override per page with a `fediverse_creator` front matter value.
fediverse_creator: "@interlisp@fosstodon.org"

# Menu title if your navbar has a versions selector to access old versions of your site.
# This menu appears only if you have at least one [params.versions] set.
Expand Down
1 change: 1 addition & 0 deletions content/en/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Medley Interlisp Project
description: "Reviving Interlisp-D, the pioneering Lisp software environment created at Xerox PARC. Explore Medley's history, documentation, and how to run it today."
aliases:
- /hugo
---
Expand Down
1 change: 1 addition & 0 deletions content/en/history/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: History
description: "Trace how Interlisp evolved from an interactive programming tool into Interlisp-D and Medley, and the research fields it helped pioneer, from AI to GUIs."
weight: 500
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/history/bibliography/intake/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Interlisp Bibliography Intake Guide
description: "Not sure whether a document belongs in the Interlisp Bibliography? This guide explains the collection's scope, how to submit an item, and what to include."

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where else could it go? Who isn't sure?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a description of the Intake Guide page - whose explicit purpose is to help answer those questions. The goal of the description is to help provide context for search engines that index our site. I believe this description fits in with the role of the Intake Guide. This wasn't meant as a comment for someone editing the website.

weight: 1
type: docs
# Explicitly visible in the sidebar: the parent bibliography section's
Expand Down
2 changes: 1 addition & 1 deletion content/en/history/bibliography/zotero-resources/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Zotero Type Mapping Reference"
description: "How Interlisp Zotero bibliography types map to CSL JSON and Schema.org vocabulary"
description: "For Interlisp Zotero contributors: how each bibliography item type is classified and mapped through the processing pipeline to CSL JSON and Schema.org."
type: docs
toc_hide: false
---
Expand Down
1 change: 1 addition & 0 deletions content/en/history/glossary/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Glossary
description: "Confused by the many names used for Interlisp over the decades? This glossary untangles Medley, Interlisp-D, and related terms with clear definitions."
aliases:
- /glossary/
- /medley/project/vocabulary/
Expand Down
1 change: 1 addition & 0 deletions content/en/history/in-memoriam.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: In Memoriam
description: "A tribute to the people whose work shaped Interlisp, remembering their contributions to the language, its development tools, and the community around it."
weight: 100
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/history/links.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Interlisp History Resources
description: "Where to find Interlisp artifacts online: a curated set of archives, collections, and computing-history resources the Medley team draws on for research."
weight: 95
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/history/timeline/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Interlisp Timeline
description: "Follow the milestones of Interlisp's development year by year, from its earliest experiments through the rise of Interlisp-D and the Medley era, and beyond."
type: docs
weight: 50
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/privacy.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Interlisp.org Privacy Statement
description: "What data Interlisp.org collects and why, how cookies and Google Analytics are used, and the choices visitors have about their information and privacy."
url: /privacy/
type: docs
weight: 30
Expand Down
1 change: 1 addition & 0 deletions content/en/project/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
Title: The Medley Interlisp Project
description: "Why we are bringing Medley back to life, what we hope to accomplish, and the state of the work: an introduction to the project and its ambitions for the future."
weight: 2
type: docs
aliases:
Expand Down
2 changes: 1 addition & 1 deletion content/en/project/comments/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: What people are saying
weight: 20
type: docs
description: Comments on Interlisp and this project
description: "How people talk about Interlisp online: a running collection of blog posts, social media threads, and reflections, with a way to submit new links of your own."
aliases:
- /medley/about/comments/
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/credits.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Credits
description: "Acknowledging the many people who built Interlisp over the decades, and the challenge of crediting work that spanned several companies across many years."
weight: 80
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/donate.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Donate
description: "Help sustain the Interlisp revival. See why your gift matters, what it funds, and the different ways you can contribute to keeping Medley available to everyone."
weight: 15
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/faqs.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: FAQs
description: "Straightforward answers to the questions people ask most often when getting started with Medley Interlisp or working in it day to day, from editors to printing."
weight: 20
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/getInvolved/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Get Involved
description: "There is a place for every skill level in the Interlisp revival. Find the route that fits you, whether you code, test, document, or help spread the word."
weight: 11
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/project/organization.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Organization
description: "Who runs the project and how it is structured, including the non-profit that holds its charitable mission and supports its scientific and technical goals."
weight: 1000
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/partners/SHFT.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Software History Futures and Technologies SHFT
description: "A University of Alberta research group studying software history partners with us to make Interlisp's innovations and context easier to explore and understand."
weight: 20
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/partners/SPN.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Software Preservation Network
description: "Why we joined a network of libraries, archives, and universities working to keep software usable for the long term, and what that partnership involves."
weight: 20
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/partners/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Organizational Partners
description: "The organizations and academic groups collaborating with the Medley Interlisp Project, and how these partnerships advance software preservation and research."
weight: 18
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/project/partners/educopia.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Educopia
description: "The non-profit behind the Software Preservation Network, and the governance and community-building resources it offers to preservation projects and communities."
weight: 20
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/project/partners/interlisporg-inc.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: InterlispOrg
description: "The non-profit corporation that funds and steers the revival, including its tax-exempt status, how it is governed, and how to support it financially today."
weight: 25
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/project/reviving.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
Title: Reviving Medley
description: "The technical decisions behind the revival: what it takes to bring a decades-old system forward, and the areas of work the project is tackling now and next."
weight: 80
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/status/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: News and Status Reports
description: "The latest news from the project — reports, interviews, and announcements — with an archive of how the revival has progressed year by year since 2020."
type: docs
weight: 2
outputs:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: 2021 Medley Interlisp Annual Report
description: "The report on the project's founding year: early decisions, initial milestones, and the groundwork laid for restoring Medley and making it usable again."
weight: 10
type: docs
aliases:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: 2022 Medley Interlisp Annual Report
description: "A year of milestones: what the team accomplished in 2022, the collaborations it formed, and how the preservation work advanced over the course of the year."
weight: 9
type: docs
aliases:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: 2023 Annual Report
description: "The 2023 report details the year's achievements and the continuing effort to keep Interlisp usable, documented, and available to new audiences around the world."
weight: 8
type: docs
aliases:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: 2024 Medley Interlisp Annual Report
description: "The 2024 report covers another year of porting, documenting, and improving Medley, along with the project's goals and priorities for the year ahead of us."
weight: 7
type: docs
aliases:
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: 2025 Medley Interlisp Annual Report
description: "Five years in: the 2025 report looks back at how far the revival has come and the work still ahead to keep Medley thriving on modern systems and gaining users."
weight: 1
type: docs
aliases:
Expand Down
1 change: 1 addition & 0 deletions content/en/project/status/reports/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Annual Reports
description: "Browse every annual report in one place and follow the project's progress from its first year through the present day, with a link to each year's report."
weight: 1
type: docs
---
Expand Down
1 change: 1 addition & 0 deletions content/en/project/stories.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Our Stories
description: "First-hand accounts from people who used Interlisp in its prime, recalling what made the environment special and why it still matters to them and to computing."
weight: 40
type: docs
---
Expand Down
2 changes: 2 additions & 0 deletions content/en/search.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
+++
title = "Search Results"
description = "Search Interlisp.org to find documentation, history, software guides, and bibliography entries about Medley Interlisp and the historic Interlisp-D system."
layout = "search"
robots = "noindex"
+++
1 change: 1 addition & 0 deletions content/en/software/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Software
description: "Everything you need to start using Medley: choose between running it in your browser or installing it locally, then dig into the guides and documentation."
type: docs
aliases:

Expand Down
1 change: 1 addition & 0 deletions content/en/software/access-online/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Access Medley Online
description: "Try Medley instantly without installing anything. Learn what the online environment is suited for and what to keep in mind while you experiment with it."
weight: 10
type: docs
aliases:
Expand Down
3 changes: 2 additions & 1 deletion content/en/software/install-and-run/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Install and Run
description: "Choose your platform and follow the guides to get Medley running on your own machine, with notes on supported systems and architectures, from x86_64 to ARM."
aliases:
- /medley/using/build/
- /medley/using/running/
Expand Down
3 changes: 2 additions & 1 deletion content/en/software/install-and-run/linux/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Install and Run on Linux
description: "Get Medley running on your Linux machine, including what the system requires and how to handle the most common distributions and desktop environments."
linkTitle: Linux
weight: 20
type: docs
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Download WSL (Local Installation) Install Files from Github
description: "Follow step-by-step instructions to download the local-installation Medley Interlisp release files from GitHub and install Medley on your Linux system."
weight: 40
toc_hide: true
hide_summary: true
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Download WSL (Standard Installation) Install Files from Github
description: "Follow step-by-step instructions to download the standard Medley Interlisp release files from GitHub and install Medley on your most recent Linux system."
weight: 40
toc_hide: true
hide_summary: true
Expand Down
3 changes: 2 additions & 1 deletion content/en/software/install-and-run/macos/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Install and Run on MacOS
description: "Set up Medley on your Mac, including the X11 software you will need first and a pointer to the download steps, for both Apple silicon and Intel systems."
linkTitle: MacOS
weight: 30
type: docs
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
---
title: Download MacOS Install File from Github
description: "Follow the instructions to download the Medley Interlisp macOS install file from GitHub Releases and set up Medley on your Apple silicon or Intel Mac."
weight: 40
toc_hide: true
hide_summary: true
Expand Down
Loading
Loading