codeforboston / codeforboston/finda

Minimal config file

Open
#33 0 comments 0 reactions 0 assignees View on GitHub
discussion enhancement question
Dominant language
JavaScript
Stars
57
Forks
98
PR merge metrics
No merged PRs in 30d

Description

I'd like to make make the site as data driven as possible, while still allowing people to fine tune things with the config file if they want.

Things in the config file that might be possible to replace with sensible defaults:
map.center - calculate the center of the data
map.zoom - pick a good default zoom level
map.bounds - no default boundaries
max.zoom - hardcode this in based on the resolution of the

properties - if there are no properties then display every item in the properties section of the json intelligently.
- use the key for each item (converted to Title Case) as the title
- recognize email/web addresses and display as mailto/href links.
- display lists as lists

search - include the search by default and allow the config file to turn it off?

facets - probably just make these off by default. If there was an easy way to pick facet-able properties that would be cool, but I can't imagine one.

There are also some config features I'd like to add (while keeping the current defaults.) Where the border between what should be a config file change and what should require a code change should be are not clear. If anyone has thoughts on how to finesse this split please discuss.
- allow people to change the default tileset with their own

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.