Yes, may be that … preview a budget to find out retrospectively
- what Neos finally is (or has already become …)
could make some sense.
Knowing it, would surely facilitate documentation, communication, marketing and developer aspects …
‘Documentation’ is a complementary and complex task, as well described here
-
ask probably ‘Roland Schütz’ how much effort it took to him to write a ‘Customer documentation’ … (not only time)
-
ask ‘Robert Lemke’ how to elaborate an exhaustive Doc like the ‘FlowFramework DefinitiveGuide’
Huge efforts have been done and sometimes it’s just the problem, that people (developers) can’t find the ‘right thread’ to the ‘masterpieces’ of this rather extensive Software ecosystem …
Thanks to inspiration by ‘Stefan Bruggmann’ on the last ‘Neos meetup’ in Zürich, the following 2 examples show probably the problem of ‘complexity and awareness’ of the ‘Neos Tooling’
-
‘Neos Templating’ (still a draft)
https://drive.google.com/file/d/11BI7IDYqe10zgzwcrhVU6NdQvXHsrF8j/view -
‘Neos Modelling’ (inspired by Stefan Bruggmann)
https://drive.google.com/file/d/1JhmNMT_j_-xWZ8Z2LeitGpREYCw7Y3-k/view
Topic of these 2 “Cheat-Sheets” above (… should have produced more, but I lacked of spirit this year … unfortunately)
- How to open the doors for developers ‘not involved’ in the project …
Thanks for reading.