Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Import WordPress stories into the Story Share portal

未关闭
#2,145 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
ruby, wordpress
领域
backend, content

调研方向

首先比较 origin/maebeale/csv-story-importer 与 current main,重点查看 app/services/story_importer.rb、lib/tasks/import_stories.rake 以及 admin import-preview UI。阅读 lib/tasks/migrate_sectors.rake L152-181 中的 sector mapping,并根据 portal-parity 变更和 Asset pipeline 调整 importer。完成的标准是:stories 导入时不会暴露 facilitator_email,portal home/sector/search pages 已填充数据,并将 sector counts 与 WordPress figures 进行抽样核对。

由索引模型根据 Issue 内容生成。

描述

post-prod-data-import stories

Context

The Story Share portal (/story_shares) is now fully functional but has little real content — dev seeds provide a handful of demo stories. The live WordPress site (stories.awbw.org) holds ~339 published stories across the sector taxonomy (Domestic Violence 80, Self-Care & Personal Growth 94, Mental Health 68, Schools & Universities 52, Facilitator Spotlights 41, …).

A WordPress CSV story importer already exists but is not on main — it lives on branch origin/maebeale/csv-story-importer (app/services/story_importer.rb + lib/tasks/import_stories.rake + an admin import-preview UI, commits 2cdcefe44, ccb37e0ab).

What's needed

  • Merge/rebase the importer branch onto current main and reconcile with the portal-parity changes (sector taxonomy, story_share_position, asset pipeline, publicly_visible/publicly_featured flags).
  • Map WP user-categories → canonical 2026 Sector names (mapping already exists in lib/tasks/migrate_sectors.rake L152-181; e.g. "Social Justice" → "Racial/Social Justice", "Self-Care & Personal Growth" → "Self-Care/Personal Growth").
  • Map WP audience tags → StoryPopulation categories (1:1: Children/Teens/Adults/Families/Community/Self/Colleagues).
  • Import artwork/featured images into the Asset pipeline (PrimaryAsset/GalleryAsset).
  • Decide visibility defaults on import (published + publicly_visible?) and handle known data gaps the importer logs (original publish date, free-text state, permalink).
  • Do NOT import facilitator_email publicly (WP leaks it via its REST API).

Verification

After import, the portal home/sector rows/search should be populated with real stories; spot-check sector counts against the WP figures above.

主要语言
Ruby
星标
15
派生
28
平均合并
1 天 12 分钟
30 天内合并 PR
262

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rubyforgood/awbw 的其他 Issue

查看 rubyforgood/awbw 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。