Scope: Data Entities for government (country, state, city, district) and observables (CVE, software components, ...) must be defined.

Note:
Adding of additional observable entities must be guarantied.

Scope: Implementation of a database schema for data entities.

Scope: A given entity should be categorized into a government institution type (ministry, state, city, district).

Scope: Documenting the project scope, context, and limitations.

Scope: Integration of the Versionmanger API to get information about used components of the system.

To improve readability (not only but especially for people struggling with reading), let's say goodbye to excessive capitalized letters in headlines.

This should not affect "Follow the Money" because it's the project's proper name. But in all other instances we can improve (and help the proper name even stand out):

How Is Taxpayer's Money Being Spent On Public Sector Websites?
How is taxpayer's money being spent on public sector websites?

Reading recommendation: https://medium.com/@jsaito/making-a-case-for-letter-case-19d09f653c98

Scope: Documenting the architecture overview, incl. context view, component view, and high level flow chart.

Scope: Data from different systems must be integrated into the CMS system Directus.

Scope: Querying the knowledge database wikidata to get government entities, their webpage, additional meta information (e.g., geolocation, CA, ...).

Scope: Development of a webpage to search records by government entity properties.

Note:

• Focus should be on a high usability and accessibility.

Scope: Creation of a landing page to get an overview of the project and its content.