jaydonigian / 2016-road-trip Goto Github PK

Test to ensure that we can delete .md files and re-create them via JSON with no differences.

There's no need for it any more. The apply to template function can be removed

Add a new section to the entry if a bike map is detected. This section will have the map of the bike ride, some info about the ride and maybe a strava link if we can find one.

At the moment, a reader must read the journal entry to see where we went on this trip.

Add a section to Today's Trip with a list of the day's points of interest.

Currently we're writing the title to index, but sometimes the title is already there.

They should be in their own folder to keep things readable.

Consider the pro/cons.

Use the same format as the template everywhere. Early pages show the price after the item.

Store Entire Journal in JSON File

Everything should be stored in the json file. If you delete an entry, it should be perfectly recreated when the script is run.

Sub-Tasks

• #42
• #48
• #49

Adjust the workflow so that a contributor can provide a JSON blob and a page will be created

Add the previous entries that weren't created via JSON

Pages created with the script link to themselves rather than the next and previous day.

It feels awkward keeping a running total within the entry because that's not the responsibility of the entry.

Journal should hold the totals and then you can ditch the runningTotal terminology.

The date for each entry is mm-dd. This is left over from an early design decision. Changing it to yyyy-mm-dd will allow us to easily parse a time.Time object from the JSON file. We can then remove setEntryYear and all its associated logic.

The new format is not rendering properly.

Currently only the photo album links are made through bitly. Create Bitly links for each page and use those in the index and prev/next links.

Keep a running tally of how much money has been spent (not including gas).

Add this tally to existing posts and update the template.