[FEATURE]: Add a backend server so articles can be submitted from the website
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- express, github, next.js, node.js, typescript
- 领域
- api, backend, content, full-stack, security
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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 (reusinglib/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:
- receives and re-validates the submission (fields, date format, image type/size, slug uniqueness),
- generates the slug and the
articles-index.jsonentry (featured: false), - uses the GitHub API to create a branch, commit the
.mdand 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
/submitwithout using Git. - Submission creates a PR with the
.md, images and a valid index entry. - Invalid input is rejected with clear errors.
- README and
/submitdocs 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
- 主要语言
- TypeScript
- 星标
- 9
- 派生
- 35
- 平均合并
- 4 天 15 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
StabilityNexus/StableViewpoints 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 57/100
StabilityNexus/StableViewpoints#105 · 1 条评论 ·
-
[FEATURE]: SEO & SEM optimization sitemap, robots.txt, per-article metadata, and structured data未关闭enhancement
难度 4/5 3-5 天 新手友好度 48/100
StabilityNexus/StableViewpoints#103 · 1 条评论 ·
-
Dark Mode: Article title becomes invisible on hover inside Article Cards可能重新可做 @SOGeKING-NUL 于 352 天前认领,目前没有进行中的 PR。 未关闭good first issue
StabilityNexus/StableViewpoints#29 · 11 条评论 · 已指派 1 人 ·
查看 StabilityNexus/StableViewpoints 的全部 Issue
相似的 Issue
-
[BUG]: Shared links drop the configured basePath on GitHub Pages可能已有人在做 @anshulchikhale30-p 今天认领。 未关闭bug
难度 1/5 1 小时以内 新手友好度 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 条评论 ·
维护者通常 1 天内回复
-
Add: GTrekker未关闭check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
维护者通常 1 天内回复
-
area: ui Bug Payload OSS
难度 1/5 1 小时以内 新手友好度 88/100
payloadcms/payload#19839 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复