Hi,
Could you please provide new wappler documentation link here?
Hi! We are still working hard on the new docs 
Here is a link to the current one: https://docs.wappler.io/
Can you share anything more? Your first post since september! Does that mean there’s an amazing up-to-date documentation coming up?
2 Likes
Hahaha i can share a little bit more. We are looking at all the old documentations and check them all if they are still relevant or not. We are also writing some new ones, ones that have been asked for for a long time 
But because our current documentations are so old and specific it takes a lot of time to check them all and re-write, take new screenshots or decide if they should be deleted in the new docs.
Our main goal is an up-to-date documentation, easier to follow and only relevant information. The really specific questions can be asked and answered in the community.
So that’s our plan, but it is a long journey. We hope to give a bigger update soon!
3 Likes
Thanks for the update!
My 2 cents for improving the documentation while being future proof (due to UI changes / how Wappler works)
- Improve ‘help texts’ in the Wappler UI
There’s a LOT of low hanging fruit that can be cleared up with adding some help text.
For example, I have worked with Data details before and was going to add one again. Then I realised there’s another action called ‘Data view’.
This made me curious if I need that. (I’m still not sure what the difference is, but after 20 mins reading on the forums I decided to go with Data Detail anyway).
These 20 minutes could have been 30 seconds by for example:
Letting me hover on the component, and a popup shows a picture example of what the action does / what it’s used for.
Same thing goes for all the properties (both server actions and client side):
Rarely there’s an i that you can hover on for more info. If those are everywhere, I think it would make life much easier. Especially for beginners, but also for people like me who have been using Wappler for a while.
- Give us a place to search each component with examples. We need a place to reference.
There are plenty of guides, but they have a certain goal. Getting from A to B.
But what if I want to get the most out of a certain component? If I need to understand all the settings it gives? Because of a lack of help texts and a reference, it’s so much guessing and searching the forums to figure out how the stuff works that is already there.
I’ve literally been making my own docs to compensate 
5 Likes
I totally get the frustration and i do agree it is sometimes pretty hard to understand, especially if the docs is not offering enough information, or not the right information.
Yes, this would make things easier. I am going to tag @patrick in to this because i am no developer so i have no idea how easy this is to implement in to Wappler haha. Maybe he can take a look at it and has the right answers for you.
This is one of the things we are working on in the new documentations. Explaining the functions/components more one by one instead of using them in a random tutorial for a specific thing.
Thank you for thinking with us and letting us know what you are missing right now!
3 Likes
In support of karh’s points, let me refer you to one of my previous posts:
1 Like
We will definitely take a look at this. Thanks for sharing again!