Seperate Website and Crawler Repos?

[marianfoo]

that would solve a few problems:

• not a monorepo anymore so would not need all the infrastructure setup for that
• clean separation of crawler and ui
• separation of crawling pipeline, more unlikely to hit api rate limits Seperate Crawl and Build #25
• repo name is kind of wrong anyway, it´s not just the website :)
• have a history of data.json
• docs branch always force push
• can collect data, like necessary in Statistics for Easy UI5 Generators bestofui5-data#4
• can seperate crawling historic data and current data

against:

• @petermuessig work was a little bit for nothing 😁

todo:

• create new repo https://github.com/ui5-community/bestofui5-data
• copy crawler package to new repo
• setup new gh workflow for new repo https://github.com/ui5-community/bestofui5-data/blob/main/.github/workflows/build.yml
• fix ui build with new json files from new repo feat: move crawler to own repo #167
• remove crawler from website repo feat: move crawler to own repo #167
• deconstruct monrepo setup in website repo

[marianfoo]

@petermuessig
created new repo https://github.com/ui5-community/bestofui5-data
same concept for now, crawls data to a other branch every day
#167 would point the ui to the json files in this new repo

[marianfoo]

ui5-community/bestofui5-data#2