Add public-facing Forestry form for submitting a new link #10

New Issue

2026-10-05T05:09:13+02:00

adam commented

2026-10-05 05:09:13 +02:00

Members of the public will be encouraged to submit links for all content types except blog posts. To achieve that, we'll need a form with the following fields:

Link
Title
Date (auto-filled to current date)
Card image (optional)
Tags (optional)
Short description (optional)
The result should be a PR that a core team member can modify and/or merge.

When this is done, add a link to the form at the top of the main blog page as indicated in the wireframe.

Members of the public will be encouraged to submit links for all content types _except_ blog posts. To achieve that, we'll need a form with the following fields: - Link - Title - Date (auto-filled to current date) - Card image (optional) - Tags (optional) - Short description (optional) The result should be a PR that a core team member can modify and/or merge. When this is done, add a link to the form at the top of the main blog page as indicated in the [wireframe](https://ipfs-ia-scratchpad.netlify.app/blog-news.html).

adam closed this issue

2026-10-05 05:09:13 +02:00

adam commented

2026-10-05 05:09:15 +02:00

Doing some research on this issue this week: Forestry isn't the right tool for publicly accessible submission form, so looking into whether other tooling can turn a questionnaire into a PR (probably one submitted by a bot). Watch this space.

Doing some research on this issue this week: Forestry isn't the right tool for publicly accessible submission form, so looking into whether other tooling can turn a questionnaire into a PR (probably one submitted by a bot). Watch this space.

adam commented

2026-10-05 05:09:15 +02:00

Update: #64 closes this issue in favor of (for now) the following workflow:

User submits Airtable survey form with relevant information
Airtable automatically emails blog admin with relevant details
Blog admin copy-pastes from email into Forestry, using the opportunity to correct any typos, assure link validity and image size, etc
Blog admin PRs Forestry's staging branch to main per usual

We'll revisit automating this more if the process becomes burdensome due to volume of submissions. In that event, suggest continuing with developing a workflow similar to what's been researched to this point:

Airtable survey is converted to a bot-submitted GitHub issue containing a link to the image (if it exists), plus the necessary JSON to add to the individual .md frontmatter in question (this can be done via Zapier or similar means, and @autonome has the "zap" recipe from my experiments in his archive)
GitHub actions are used to convert issue into a reviewable PR: adding the JSON snippet, uploading the image to the blog's public directory, etc

Update: #64 closes this issue in favor of (for now) the following workflow: - User submits [Airtable survey form](https://airtable.com/shrNH8YWole1xc70I) with relevant information - Airtable automatically emails blog admin with relevant details - Blog admin copy-pastes from email into Forestry, using the opportunity to correct any typos, assure link validity and image size, etc - Blog admin PRs Forestry's `staging` branch to `main` per usual We'll revisit automating this more if the process becomes burdensome due to volume of submissions. In that event, suggest continuing with developing a workflow similar to what's been researched to this point: - Airtable survey is converted to a bot-submitted GitHub issue containing a link to the image (if it exists), plus the necessary JSON to add to the individual .md frontmatter in question (this can be done via Zapier or similar means, and @autonome has the "zap" recipe from my experiments in his archive) - GitHub actions are used to convert issue into a reviewable PR: adding the JSON snippet, uploading the image to the blog's public directory, etc

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/ipfs-blog#10