Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Application block Map #27

Closed
ifsimicoded opened this issue Dec 5, 2017 · 2 comments
Closed

Application block Map #27

ifsimicoded opened this issue Dec 5, 2017 · 2 comments

Comments

@ifsimicoded
Copy link
Contributor

ifsimicoded commented Dec 5, 2017

Mobile mockup

screen shot 2018-01-16 at 4 55 48 pm

Desktop mockup

none, yet

@mateoclarke mateoclarke added this to the Dec Sprint Review milestone Dec 8, 2017
@ifsimicoded ifsimicoded self-assigned this Jan 16, 2018
@mateoclarke
Copy link
Contributor

mateoclarke commented Jan 16, 2018

Putting down and elaborating on some thoughts I shared with @ifsimicoded earlier today

It seems like there is some Joplin data modeling that needs to happen here that hasn't been scoped out yet. I didn't see any Joplin issues (open or closed) related to map data.

When a content editor selects a Map Application Block, they are currently choosing a Wagtail "Snippet" to include. Those Application Block Snippets seem to be modeled currently with the fixture data as having a URL and a description. In one case, the URL links to an image of a map. This might just be a placeholder, but I'm confused about how this gets implemented consistently. If adding a map to a page means inserting an image and some descriptive text, can't they just do that in the WYSYIG?

Or is this feature about letting an admin build a map with one or several lat/longs and then inserting a proper webmap onto the page, a la ctxfloods?

@ifsimicoded
Copy link
Contributor Author

Closed by #107

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants