Tracking: move bioconductor.org from nanoc to Astro

Abierto
#440 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, ruby
Área
frontend, web-dev

Línea de trabajo

This is a tracking issue for a multi-PR migration, not a single task. Read the plan on the astro branch and the linked sub-issues #431 to #439, and start from #431 (scaffold) in order, since later PRs depend on the CI checks from #432. Done means this issue closes with the cutover PR from astro to devel; the package collector bioc.py moves to the infrastructure repo.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

astro-migration

Move bioconductor.org from nanoc (Ruby) to Astro, with content, renderer and checks in this one repo. This tracks the work.

Where the work happens. The astro branch on seandavi/bioconductor.org. Each piece is a short-lived branch merged into astro by PR, with CI on every PR. devel keeps running nanoc, untouched, until the cutover, which is one PR from astro to devel at a short content freeze.

Closing issues. A merge into astro on the fork can't close an issue here. When a piece lands, its issue is closed by hand with a link to the PR and labeled on-astro. This issue closes with the cutover PR.

What moves where.

  • The renderer from seandavi/bioc-website moves into this repo.
  • The package-data collector (bioc.py packages/tree) moves to the platform repo, seandavi/bioc-infrastructure (packages/site-data).
  • Course-material files (PDFs, slides, videos) were never in git. They stay archival content in R2, served by the edge.

Order. 431 → 432 first, so every later PR is checked. Then 433 → 434 → 435. 437 and 438 can run alongside those. 436 comes last, then 439 and the freeze.

  • #431 Scaffold
  • #432 CI checks
  • #433 Typed data with schemas
  • #434 Converter
  • #435 Port the ERB pages
  • #436 Remove nanoc
  • #437 CSS overrides into the stylesheets
  • #438 Parity check
  • #439 Editor docs and freeze runbook
Lenguaje dominante
HTML
Estrellas
40
Forks
55
Merge medio
12 h 31 min
PR fusionados (30 d)
4

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Bioconductor/bioconductor.org

Todos los issues de Bioconductor/bioconductor.org

Issues similares

Más issues de Web Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.