diff --git a/frontend/src/routes/+page.svelte b/frontend/src/routes/+page.svelte index 4d6a66b..93ecdf1 100644 --- a/frontend/src/routes/+page.svelte +++ b/frontend/src/routes/+page.svelte @@ -1,4 +1,7 @@ -

No frontend yet!

+

Welcome to the City Portal

-

If you know your way around GraphQL, you can try directly interfacing -with the backend.

+ diff --git a/frontend/src/routes/about/+page.svelte b/frontend/src/routes/about/+page.svelte new file mode 100644 index 0000000..e099c59 --- /dev/null +++ b/frontend/src/routes/about/+page.svelte @@ -0,0 +1,9 @@ +

City portal is a local data aggregator: local data is a term I coined to mean data that only matters to a specific geographical community. +This can range from weather, to events at the local town hall, to transportation. City Portal provides an open and extendable way to use this data, +exposing a GraphQL API that anyone is free to read from, but write access can be restricted.

+ +

The City Portal is adaptable to different scenarios: by customizing the different datasets that the server stores and that data can be stored into, +the managers of the Portal can decide what kinds of local data is stored, but still have this data categorized neatly by function.

+ +

Finally, because of its free to read API, the City Portal promotes extension: anyone is free to build ML models, graphs, or visualizations on top +of the Portal.