Felt has sjablonen, stored in config

sjablonen.(name) has fields:
* naam_nl = default name
* naam_en = ...
* info = used in the sjabloon overview
* types (array_keys ???)
* parameters = dict of parameters & type
* parametes_beschrijving = description of parameters
* parameters_sample = default values of all parameters

On /activiteiten/bewerk we have a list of if statements
It groups the answers by type
* choises, feedback, teams, dinner, shirtsizes, nnv, 
* public transport, reserve list, signups list

* activites store their "types" as bitmask (1 = medisch, 2 = thuisfront ...)
* stored in models\Parameter  
* list of parameter datatypes, 

Why is everything so builtin ?! Crazy. 

List of question types:
* medical --> alergies, meds, extra info
* thuisfront --> name contact, email contact, phone #1, phone #2
* shirtsize --> pick enum from XXS, XS, S, M, L, XL, XXL
* identification --> document type, document number, expiry date, ...
* nnv --> state (notmember, later, member) & nnv number
* food --> joins for the meal (true/false), diet (text), vegetarian (t/f)
* public transport --> enum (no, week-only, weekend-only)
* travel / zorgverzekering --> verzekeraar, polisnummer, noodnummer, type (zorg of reis)
* questions --> parameter_id, slot, answer
* choices --> parameter_id, slot, choice
* feedback --> feedabck (str)
* team --> teamname (str)



omg it is TERRIBLE. In Silk every sjabloon has its OWN template ?!
so much work yikes

Example for the "Studiereis" sjabloon:
* Some text (incl deadline) --> we can refer to variables and use HTML!
* Header (your signup is coupled to your current account!)
* Health insurance (+ text)
* Medical information (+ text)
* Home stayers (+text & checkmark about International Office)
* Identification (+text)
* NNV (+text)
* T-shirt 
* OV
* Feedback

Pattern:
* (title) (prefix text) item (suffix text)
Then possibly also:
* title-items & text-items

-------------

Ideas:
* Modular system!
* Create template activities (by creating activity, store as template & then delete?)

* Combine complicated questions into custom question (see all above)