First, having come at this from more of programmer/technical background thus far I’ve been very impressed with EE the app.

On the other hand, the documentation is heavy on what, lighter on how, and almost nil on why. Why can’t there be full blocks of code for examples and not just so many one liners. Not sure about anyone else but seeing things in full context helps. And when there are things unique to EE, a couple examples of why (i.e, This is helpful when…) might end up being the difference between a happy client and one who is ecstatic. I suspect there’s more wheel inventing and/or if-I-knew-then-what-I-know-now moments then there needs to be. So it might also be the differenc between under budget and over budget.

Finally, might there be a better way to org this forum? Categories? Tags? There seems to be a lot of content here but finding answers - if the question has been asked before - consume a bit more of my time then I wish it did.

<reat> To the rest of us in the peanut gallery… Using titles like “I have a problem” or “Some please help” and other generic title probably lowers the odds of you getting input. (I don’t read them that’s for sure. No time for crap shots.) You’re better of framing your issue with an informative title so if someone sees something they know something about they’re more likely to contribute/share. There’s a reason why the New York Times doesn’t have headlines like “Another Day with Problems in the World” </rant>

I know I’m new here but I’m excited and just want to dive right in and be productive. But then again, don’t we all?