Please read - I would really like feedback on this proposal re documentation

Wappler General
21

That very idea has always been part of my vision although any certification would need the Wappler team's approval re content of course.

22

@Hyperbytes, I would be happy to assist as well with proofreading, testing, and contributing.

1 Like
23

The idea is excellent and extremely necessary.
Let me make a few comments and clarifications (Given the fact that this is a non-profit project for enthusiasts):

Why do you need to write your own CMS?

For example, we use:

for our small team.

Advantages:

  1. It can be deployed in a Docker container in minutes.
  2. It allows to create content that adheres to the principle of a single source of truth.
  3. It allows you to create a read-only documentation website for public access.

Cons:

  1. There are no granular user access (yet).
  2. The design is predetermined.
  3. The documentation in English is weak, but to write documentation this is not a very big problem, for complex SQL queries you have to use the forum.
    For example:
    SiYuan Template Function Guide for Newcomers: Template Synt - LiuYun

Conclusion:
For a completely open project, with the total access of all trusted editors to edit the documentation and the cost of deployng and contents is very well suited.

24

Two reasons.

  1. i believe software should follow workflows, not the other way around.
    I have followed that path before and always regretted it when in found myself having to adjust to a non optimal workflow.

  2. Possibly the most important, I think a support system for Wappler should be developed using that platform. To use an alternative would not showcase it and even infer it is not suitable.
    Nothing you quote cant be done in Wappler

4 Likes
25

I would strongly recommend revisiting your primary objective: is it to build a learning platform CMS, or to deliver high-quality educational content?

Developing your own CMS from scratch can be time-consuming. Instead, consider leveraging one of the many open-source learning platforms available, which would allow you to focus immediately on creating and sharing valuable content.

1 Like
26

I take a different approach in my business. Know what is my app's core value proposition, and build that. If it isn't core, serious consideration should be given to using existing solutions.

For example, I use a customer support beacon from Intercom because customer support while important, is definitely not my core value proposition. Intercom has invested heavily in their solution, so it is worth paying them. Could I build it with Wappler, sure but it would take resources away from building what my customers are actually paying for.

Another example, this forum. Could it be built with Wappler, yes. Is that a good investment of time, I don't think so.

The core value prop of Wappler can be debated, but I can't think of a scenario where people are buying Wappler specifically because it can build a support system. They buy it because if its ability to help them deliver solutions, which usually means, features and performance.

27

@Notum @mebeingken lets make this simple.

IT'S NOT HAPPENING!

28

@Notum I guess he didn’t like our feedback. :rofl:

1 Like
29

Correct, you are looking at thiis as a business proposition, i am looking at it as a non profit community project so your comments are not relevant.

30

It’s all fine, I disagree that tax status has anything to do with how to make choices on tech stack, but you want this your way, and I’m sure it will help many people when ready.

31

The choice of tech stack was the easiest decision and not related to tax status, Wappler for a Wappler docs system.

But it's true, making money is not an issue for me, i dont need it.
Philanthropist, just like Bill Gates. :grinning:

1 Like
32
  1. Take your CAPS off. You've asked for a feedback - here is mine.
  2. I never mention "money, business or anything related to profit". I just gave my opinion that use of an a rock-steady open-source documentation/WIKI CMS will save you a ton of time, effort and nerves.
33

No, Ken did.
I made the clear comment above to avoid this long and pointless conversation.
This is a wappler project i am doing and that is set in stone.
I have no desire to do otherwise.
It's Wappler or i dont do it.
Can we agree to disagree and move on.

1 Like
34

This is a great idea :slightly_smiling_face:

Don’t know if it’s possible (would need the teams help) but a tooltip or similar from Wappler app that links to the relevant documentation page. Then if something isn’t documented yet it could say this in the tooltip encouraging people to document this.

1 Like
35

That was discussed previously and the team did talk about dynamic tool tips from a central editable core but for some reason it never materialised.

36

Brilliant idea! Let me know if there's anything I can help with..

37

I am anxiously awaiting which direction this goes. You are a rock star!

I would love to help out by reviewing non node tutorials.

Best of luck Brian!

38

Hope to have a limited preview within a few weeks, coming together nicely.

1 Like
39

Awesome! Count on me for reviews!

1 Like
40

Hi Brian,

This is a fantastic initiative! I'd be glad to contribute by testing the steps outlined in the documentation using Wappler and sharing feedback.