General maintenance tasks

[roll]

• [ ] Update/clean starlight
• [ ] Split the v1/v2 repositories
• [ ] Migrate both to Github Pages
• [ ] Test https://datapackage.org/guides/csvw-data-package/ (some reports on broken CSS on mobile)
• [ ] Update outdated dependencies
• [ ] Don't use MDX for documentation
• [ ] Use Markdown compatible notes for documentation - https://github.com/HiDeoo/starlight-github-alerts
• [ ] Update to modern tooling - pnpm/biome/etc
• [ ] Rebase data package profiles on JSON (no need in the generate step)
• [ ] Add Extension DP / Camtrap DP / etc exampes to extension spec
• [ ] Add Cardealer DP to extensions
• [ ] Profile should be full URL in the specs docs
• [ ] Remove fiscaldp from the data package subdomain
• [ ] Propose format instead of standard for data package? (works better for end-users?)
• [ ] Rebase datapackage on semantic-release (use issue types)
• [ ] Add badges to the readme
• [ ] Remove fiscaldp from the data package subdomain
• [ ] Add html {scroll-behavior: smooth;}

[roll]

Hi @pdelboca,

As OKFN is getting back to active project maintenance here is some context from my side (as I was maintaining this repository last 2 years to the extent I could manage in my free time).

Here is an infra:

• Board: https://github.com/orgs/frictionlessdata/projects/18 (issue categorized/prioritized)
• Discussions: https://github.com/frictionlessdata/datapackage/discussions (to triage and answer when possible)

Most pressing points ATM:

• The initial idea of releasing v2.1, v2.2 etc like one a year was probably wrong as using it we can't release quick fixes to the profiles. So things like https://github.com/frictionlessdata/datapackage/issues/965 was fixed many moons ago but still are not released (see the "Done" issues on the board). We discussed it with Peter and I think following more straight-forward semver with immediate quick-fixing might make more sense for the project (it will require using version like v2.0.1 instead of just v2.0)
• Separation of v1 and v2 portals and releasing to Github Pages. We already discussed it once I think. This one needs to be handled - https://github.com/frictionlessdata/datapackage/issues/1082 - and it was blocked by the CloudFlare build. So separating version to v1 repo and v2 repo and deploying both to Github Pages would make a lot of sense (so the project is more transparent to the contributors as well).
• Releasing Metadata for Table Schema - https://github.com/frictionlessdata/datapackage/issues/899 - this one meant to be v2.1 is well over due as well

cc @peterdesmet