gulix / fiasco-mustache Goto Github PK

Some playset (Road Trip, for instance) have more than the four classic "Sections". There should be a way to generate these extra sections.

When the Playset have been completed, it can be difficult to imagine an insta-setup.
A button could be added to allow the user to get a random Insta-setup filled.

If the textarea is empty, a void object is used for creating the paragraphs, then causing an error.

In addition to the generic paragraphs of the Introduction (Credits, Description, Movie Night, ...), custom paragraphs, with custom titles, should be available.

Some playset have a custom Tilt Table.
It could be an optional section.

In order to get a better User-Experience, some enhancements are needed.
The PDF button generation need to be moved (with Load / Save ?)
The Save button should stick with the loaded name, even if the Playset changes name.

When a section has a void name, the tabs are not displaying correctly.

Automatic Boilerplate addition, with mention to Fiasco / Bully Pulpit Games.
It could be added on the "Credits" page automatically, or following the Credits (a button to add "Standard Boilerplate"

Maybe use some kind of markdown syntax (* & **) to get bold and italic text in the pdf

We should have a field to include a standard Boilerplate and include it (modified or not) in the generated (pdf or mustache) playset

Will make for a better code, easier to read / work with

Currently, the Cover is not saved with the other data

The Red Color of the Title could be set by the Playset itself (with default value)

Fiasco-Mustache should be able to store the data of a user in the browser cache.
No load/save needed if he uses the same browser / computer.
Optional only, with a "file browser" to select which file to edit (and auto-save)

Maybe in link with #2
The current text is given to the json data for generation "as is". But somme generation methods should have "paragraphs" instead of text with breaklines.

Maybe getting the description in full text mode, with markdown Titles and text ?

    # Description

    This is the description.

    With a second paragraph.

    # Movie Nights

    List of movies

    # Advices

    And so on ...

Reviewing the JS code, the files, moving and renaming ...

Insta-setup is not a mandatory part of a template.
Instead of having a "not-thought" insta-setup, there should be an option to mask the Insta-setup and not use it in a template

Provides a new way to create a playset with only the cards.
Less pages on the website, and also a shorter description.

Some playset have a custom Aftermath table.

If the description include a great chunk of text (additional rules, for example), the text is on multiple pages, abritrarily divided.
A specific page break could be a good addition.

When editing a new playset, and taking another playset for example, all the fields are completed. A good function would be a "Clear entries" at different levels (sections & categories).

Currently, the Insta-Setup add text in english (For X players ...)
In order to produce Playsets in other languages, the ability to select a language is required.

Some examples of Mustache templates (Markdown, BBCode, HTML, ...) should be accessible from the UI.

When printing a Category to PDF, if there is multiple entries that need two lines to be printed, then the subheader goes on another blank page.

This subheader could be printed with absolute positioning if possible to avoid that. Or a better control be put.

The current Layout works fine in Desktop, not so much in Mobile.
A revision is needed, maybe getting rid of Bootstrap ?

Allowing the current item of a previous playset to be used in a v2 playset generation (cards).

It will be an "hybrid" playset, with both version

Fiasco V2 no longer use the current playset (4x6x6) presentation.
Instead, it uses a deck of items. Mostly 18 Relationships, 13 Needs, 9 Items, 9 Locations.

First step is to generate a PDF with cards, and then use the data of the playset to populate those cards.

The Insta-Setup is not saved / loaded through the json data.
The selected options (dice choices, not text) should be stored in the JSON.

In addition to generate a template via Mustache, the inclusion of a generic PDF export would be a great addition.

Following Issue #24 , multi-language has been added to InstaSetup.
General UI could be improved with it too.

If the data saved as JSON have accent characters (é à ...), the encoding fails, and when the file is loaded, these characters are not properly displayed.

Add a "Made via Fiasco-Mustache" kind of watermark to the produced PDF ?