• map data model from BE to vuex store
• add static data for development (if backend is not available yet)

direktee URL zur demo, mit zentrierter Karte und offnen demo details popup

sicherheitsfrage vor dem Löschen
Abhängig von #13

Felder: email, Telefon, Name, Ortsgruppe (select), Passwort

• show marker on map
• load marker data from store

Demos in Liste Zeigen

Erweiterung das nur die Demos des Users/Ortsgruppe angezeigt werden (Abhängig von #11 )

CORS für dev

init leaflet
init map provider
show map on home view

abhängig von #11

abhängig von #13

Felder: Username/email, password
Abhängig von Registrierung #10

To handle package agnostic issues it would be good, to have a global repository, which should not have any code at all. It should handle general discussions and issues between single packages. I would also give a platform to discuss new packages/repositories, cause they are needed somehow.
At the end we would also have a kind of an open wiki, a project board to visualize issues, and a nice way to communicate open stuff asynchronously.

Demo mit allen Daten anlegen
Daten für Kontakt (Telegram, whatsapp, Twitter, Facebook, Email) unter ortsgruppe speichern
Abhängig von #11

Please add a kind of a story, what this adds is responsible for to README.md

It seems to be obvious for someone being in each chat meeting. But for newbies and someone with a lazy head, this is not. So it would be cool to add the main purpose and the mail models it is dealing with into a separate section of the README.md.
This is the same for the backend. On both sides, I am not able to give a hand as I do not see main responsibilities.

abhängig von #12