[FEATURE]: Add a backend server so articles can be submitted from the website

Open
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active

Research direction

Start by reading the existing /submit page, lib/markdown-renderer.tsx, articles-index.json, and the GitHub Actions workflow to understand the current formats and deployment flow. Then decide where the separate API will run and how it will authenticate with GitHub; the issue leaves both decisions open. Done means validated submissions create a PR with the article, images, and a valid index entry, with clear errors and updated README and submission docs.

Written by the indexing model from the issue text.

Description

documentation enhancement
Feature and its Use Cases

Title: [Feature] Add a backend server so articles can be submitted from the website (no manual PR)

Problem

Contributors currently have to fork the repo, add a .md file and images, hand-edit articles-index.json and open a PR. This is a barrier for non-developers, and mistakes in the index (a bad comma, a slug that doesn't match the filename) break the build.

Proposal

Turn the submission flow into a small client-server app:

  • Client (existing Next.js site, /submit): a form with title, author, date, excerpt, header image, a Markdown editor with live preview (reusing lib/markdown-renderer.tsx) and image upload. It also does basic client-side validation.
  • Server (new Node.js/Express API, hosted separately): the site is a static export on GitHub Pages, so it can't handle uploads itself. The server:
    1. receives and re-validates the submission (fields, date format, image type/size, slug uniqueness),
    2. generates the slug and the articles-index.json entry (featured: false),
    3. uses the GitHub API to create a branch, commit the .md and images, and open a PR for maintainer review.
  • On merge, the existing GitHub Actions workflow deploys the site as it does now.

Key requirements

  • No GitHub account needed to submit.
  • Keep the current file and index format, so nothing else changes.
  • Enforce the existing image rules (JPG/PNG/WebP, max 2 MB, hyphenated lowercase names).
  • The GitHub token stays server-side only.
  • Rate limiting, CAPTCHA or honeypot, and sanitization of submitted content.
  • The manual PR route keeps working, and the docs are updated.

Open questions

  • Where should the server be hosted, and who owns the GitHub bot token or app?
  • Is it OK to keep maintainer review via PR as the approval step?

Acceptance criteria

  • A user can submit an article from /submit without using Git.
  • Submission creates a PR with the .md, images and a valid index entry.
  • Invalid input is rejected with clear errors.
  • README and /submit docs are updated.

I'd like to work on this if the approach looks good.

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Dominant language
TypeScript
Stars
9
Forks
35
Avg merge
4d 15h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StabilityNexus/StableViewpoints

All issues in StabilityNexus/StableViewpoints

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.