Skip to content

Should we remove generate content from git repo? #1221

@tunetheweb

Description

@tunetheweb

@HTTPArchive/developers , question for you all:

We auto generate some content, including:

This creates some confusion as searching the code base (e.g. to fix a typo) leads to multiple hits - but only the .md files should be edited. It also means some people edit both .md and .html files when they don't need to.

We could remove these files from the Git repo (and add the relevant .gitignore entries to ensure they are not re-uploaded).

The generated HTML files will still be generated, tested and linted as part of our GitHub action so don't think we lose anything with that.

We should also add the npm run generate to the npm run deploy script as they need to be generated and uploaded to App Engine to actually run the site.

The one downside is developers will now need to run npm run generate to generate these .html files, to be able to run and be able to develop the website. So a developer just making some CSS changes but nothing else, now has an extra step to complete. Do we see that being a problem?

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    developmentBuilding the Almanac tech stackquestionFurther information is requested

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions