more docs

Flagfile.example

@@ -41,5 +41,8 @@ FF-testing {
 FF-feature1 {
     /* comment like this */
     true
+    a == "something": false
+    false
+    json({})
 }
 

TODO.md

@@ -7,4 +7,4 @@
 - [+] date comparisons
 - [ ] date > timestamp comparison
 - [ ] parse NOW function
-- [ ] parse comments in function body under rules
+- [+] parse comments in function body under rules

docs/roadmap.md

@@ -0,0 +1,17 @@
+# Roadmap
+
+for the fullblown project Flagfile follow same bottom up technique just like NOM parsing bottom up :D
+
+## sequence of events
+
+1. create parser and evaluator for boolean expressions
+2. create parser and evaluator for Flagfile
+3. finilize api for parsing and evaluating both
+4. publish them as cargo libs
+5. export WASM and FFI
+6. create demo ffi lib in lets say c# .net core
+7. create simple UI to create and update Flagfile on web
+8. create sidecar container with storage of Flagfile in git/filesystem/cdn configurable
+    expose same through either restful/grpc/redis custom command
+9. create fullblown UI multitenant and projects, envs and stuff to serve Flagfile through cdn
+10. create clientside libs through ffi in other popular languages