Skip to content

Update or Document Deployment Pipeline #54

@hydrosquall

Description

@hydrosquall

Presently, it's a little bit unclear how data gets from this repository to wherever campusdata.org looks to serve static files. As a result, we have a situation where https://campusdata.org/ is half health blog, half content from this project.

Screenshots: (health blog)

campus_data_-

(content from this project's markdown files)

guidebook_-_campus_data

Medium term suggestions:

  • Document current pipeline
  • Replace current pipeline with a new one (perhaps with Netlify)

Short term suggestions

  • Investigate how health blog content is getting deployed to the current location, and replace with the static build from this site

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions