for the full-blown project Flagfile follow same bottom up technique just like NOM parsing bottom up :)
feature flags perfectly decribed here: https://martinfowler.com/articles/feature-toggles.html
- create parser and evaluator for boolean expressions (DONE)
- create parser and evaluator for Flagfile (IN PROGRESS)
- finalize api for parsing and evaluating both
- publish them as cargo libs
- export WASM and FFI
- create demo ffi lib in lets say c# .net core
- create simple UI to create and update Flagfile on web 7.1 create syntax highlights for vim/neovim, vscode etc. (ex.: https://github.com/NoahTheDuke/vim-just)
- create sidecar container with storage of Flagfile in git/filesystem/cdn configurable expose same through either restful/grpc/redis custom command
- create full-blown UI multi-tenant and projects, envs and stuff to serve Flagfile through cdn
- create clientside libs through ffi in other popular languages