Yes but how often do we hear…
I have come from Bubble, it has amazing docs but is just way to expensive.
So I came over to wappler as it appears better but the docs suck. Why can’t wappler have the same quality of docs?
Wappler is basically a three man team, if people want better docs then does development stop or do they hire in more staff and put the prices up?
In an ideal world we all want everything but that’s a difficult call.
I got excited when they added two people to the team (Remi and someone else whose name I can’t recall) and their remit was the documentation. But I believe they’re no longer part of the team so it’s back to the three core people.
There must be enough in the bank to employ just one more person to specifically look at the documentation. And if all the posts about this are true, the number of additional paying users will more than cover that cost anyway.
I’m not asking for lengthy and thorough documentation on absolutely everything (although that would be a dream), I’m just looking for tooltips on every field so it’s really clear what is expected to be put in there.
They took on extra staff members to cope with this type of demand for more comprehensive docs.
I’m with @sitestreet on this one, even having ‘hints’ in the UI would be a massive help. For an example, the FormatDate formatter has one which I use all the time, I’m constantly forgetting which formatting to use in a few of my date fields. Just being able to hover over it to find an aide-memoire is a big boost - adding this to all components of the UI would be a huge time saver.
This could be a good compromise for the team, providing a very useful productivity boost whilst also negating the need for uber-comprehensive documentation.
Yes, I did some work with romy, dre67 never seemed to get involved.
Romy was a good designer but not at all technical and for me, she was not really a good fit for the team. Not sure why she left.
Romy, yes, that was her name. I was close!
I believe the software already has the facility in place for tooltips as they appear in lots of places. It just needs a bit of time spent adding them to the rest of the places. I know it will involve time to do it but it will be massively worth it. If it was just addressed bit by bit each week - maybe one of the team spends an hour a week adding some tips - then it will soon plug all the gaps and make it sooooo much better for us users.
Or add a mechanism for Ambassadors to add help texts?
Yep, I’d be happy to fill in some gaps and I’m sure others would be, too.
Great idea!
Thanks, this will help.
This is a very wrong perspective.
The question should be: “How many more clients would the project have had if the documentation was in place and supported the user every step of the way”.
How about the good old Wiki? If you make sense of the structure, you could 1:1 use them to produce ‘internal documentation’ / hints etc in Wappler.
Basically,that’s what we have now
I think we should create a feature request on this.
Seems a good one.
Besides that:
I always thinked on something like this could be helpful on Wappler:
With instructions and examples but sounds like too much work. I’m able to help if that’s the case 
I’d easily pay $100-$200 a month if it meant Wappler improved 2x faster.
In that case I will call it a day and revert to VS Code.
I’m very busy these days and the time I have is limited but I’m trying to understand where things going and unfortunately I can not follow up…
So, please let me point a few things:
Finally, I would like to say that the money paid for this product is OK…
I cannot afford paying more just for having every command and action written down in a documentation.
I had that with Cinema-4d but no matter how much I used it, I always had to watch a few related tutorials in order to achieve what I wanted.
If you take the only sensible candidate from the area as your wife, that doesn’t mean it has to be love straight away
What you seem to be missing here is the big difference that there are many people who come to Wappler from outside of development and who aren’t necessarily familiar with many of the technologies. Sometimes these things that seem obvious to you - we don’t even suspect their purpose, let alone the details of their application.
Maybe do something like small WiKi articles tied to elements inside Wappler - and give the community the opportunity to fill it out gradually.
Of course, some kind of moderation hierarchy will be required, but it seems to me that we can highlight the most qualified colleagues within the community and give them some stronger rights. In this case, the team will not have to spend additional resources, and the community will be interested in a simple and high-quality approach to writing these tips.
And then the learning progress will be several times faster, which will probably attract additional paying users.
I look at the comments above and see that other people have similar thoughts, you just need to combine the wiki principle with hints inside the interface - in fact, many things have already been discussed on the forum - but it’s difficult to get to them now
