Geolocation Information and Post Mapping


#1

Hi all,

I’ve used ghost for a bunch of different blogs over the past few years and really love it. That said, one thing that I’ve always thought would be a great feature would be stronger product support for geolocation information.

A few use cases for this feature:

  1. A travel blogger wanting to show post locations on a map.
  2. A house-hunting blog wanting to link house / renovation locations to where those houses are.
  3. A hiking blog plotting favorite routes and trails.

I can see a pretty simple way to make this work:

  1. [CORE GHOST] Allow users to tag posts with geolocation information, ideally supported by some sort of location API.
  2. [THEME IMPLEMENTERS] Process geolocation information into a map view or as additional metadata on posts.

Is there appetite for this feature set? If so, I’d be happy to pull together a PR against Ghost.


Add and remove fields in page settings
#2

I was looking for the same. :smiley:


#3

If you want the same feature, then you should vote on it, not comment :wink:


#4

I would like to add field with general metadata. Any template will define which metadata uses and users should have in admin panel place to paste json with configuration.

This is extremely elastic and quite simple. Now database schema for post is following:

+---------------------+---------------+------+-----+---------+-------+
| Field               | Type          | Null | Key | Default | Extra |
+---------------------+---------------+------+-----+---------+-------+
| id                  | varchar(24)   | NO   | PRI | NULL    |       |
| uuid                | varchar(36)   | NO   |     | NULL    |       |
| title               | varchar(2000) | NO   |     | NULL    |       |
| slug                | varchar(191)  | NO   | UNI | NULL    |       |
| mobiledoc           | longtext      | YES  |     | NULL    |       |
| html                | longtext      | YES  |     | NULL    |       |
| comment_id          | varchar(50)   | YES  |     | NULL    |       |
| plaintext           | longtext      | YES  |     | NULL    |       |
| feature_image       | varchar(2000) | YES  |     | NULL    |       |
| featured            | tinyint(1)    | NO   |     | 0       |       |
| page                | tinyint(1)    | NO   |     | 0       |       |
| status              | varchar(50)   | NO   |     | draft   |       |
| locale              | varchar(6)    | YES  |     | NULL    |       |
| visibility          | varchar(50)   | NO   |     | public  |       |
| meta_title          | varchar(2000) | YES  |     | NULL    |       |
| meta_description    | varchar(2000) | YES  |     | NULL    |       |
| author_id           | varchar(24)   | NO   |     | NULL    |       |
| created_at          | datetime      | NO   |     | NULL    |       |
| created_by          | varchar(24)   | NO   |     | NULL    |       |
| updated_at          | datetime      | YES  |     | NULL    |       |
| updated_by          | varchar(24)   | YES  |     | NULL    |       |
| published_at        | datetime      | YES  |     | NULL    |       |
| published_by        | varchar(24)   | YES  |     | NULL    |       |
| custom_excerpt      | varchar(2000) | YES  |     | NULL    |       |
| codeinjection_head  | text          | YES  |     | NULL    |       |
| codeinjection_foot  | text          | YES  |     | NULL    |       |
| og_image            | varchar(2000) | YES  |     | NULL    |       |
| og_title            | varchar(300)  | YES  |     | NULL    |       |
| og_description      | varchar(500)  | YES  |     | NULL    |       |
| twitter_image       | varchar(2000) | YES  |     | NULL    |       |
| twitter_title       | varchar(300)  | YES  |     | NULL    |       |
| twitter_description | varchar(500)  | YES  |     | NULL    |       |
| custom_template     | varchar(100)  | YES  |     | NULL    |       |
+---------------------+---------------+------+-----+---------+-------+

and there is no place for custom data with complex structure. Only tags are supported, but tags cant be used in this case.

And I have question about locale parameter. How to set it in admin panel for given post?