You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
May I suggest you to write extensive documentation?
I'm a little familiar with (python) Flask web microframework. It alone has extensive User Guide, with lots of example code, and advice. Beginning with "Quickstart" (kind of advertising overview), then Tutorial, then covering standard tools, then advanced issues, and eventually, API. Look at it, it's a great example of documentation. Each module Flask is usually used with (like login, forms, templates, database, etc) also has similar extensive documentation.
Same with nginx: lots of documentation, examples, FAQs, (official) blog posts.
For ulib, I only see a very short wiki (by jonathan kelly). For such a huge project (much larger than Flask), only a short "getting started"?!
Examples are great, but, in my perhaps not very humble opinion, there should be an intermediate-level documentation: use cases with key code excerpts.
Suppose you die. Will this great kid of yours continue to live its life on its own?
What do you think?
The text was updated successfully, but these errors were encountered:
You are right. I apologize for this but I am sick and I feel very
tired at the moment. I don't think that this state can change in the
future, sorry.
2021-07-06 8:45 GMT+02:00, blue-apparition ***@***.***>:
Hello!
May I suggest you to write extensive documentation?
I'm a little familiar with (python)
[Flask](https://flask.palletsprojects.com/en/2.0.x/) web microframework. It
alone has extensive User Guide, with lots of example code, and advice.
Beginning with "Quickstart" (kind of advertising overview), then Tutorial,
then covering standard tools, then advanced issues, and eventually, API.
Look at it, it's a great example of documentation. Each module Flask is
usually used with (like
[login](https://flask-login.readthedocs.io/en/latest/),
[forms](https://flask-wtf.readthedocs.io/en/0.15.x/),
[templates](https://jinja.palletsprojects.com/en/3.0.x/templates/),
[database](https://flask-sqlalchemy.palletsprojects.com/en/2.x/), etc) also
has similar extensive documentation.
Same with nginx: lots of documentation, examples, FAQs, (official) blog
posts.
For ulib, I only see a very short wiki (by jonathan kelly). For such a huge
project (much larger than Flask), only a short "getting started"?!
Examples are great, but, in my perhaps not very humble opinion, there should
be an intermediate-level documentation: use cases with key code excerpts.
Suppose you die. Will this great kid of yours continue to live its life on
its own?
What do you think?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#89
Hello!
May I suggest you to write extensive documentation?
I'm a little familiar with (python) Flask web microframework. It alone has extensive User Guide, with lots of example code, and advice. Beginning with "Quickstart" (kind of advertising overview), then Tutorial, then covering standard tools, then advanced issues, and eventually, API. Look at it, it's a great example of documentation. Each module Flask is usually used with (like login, forms, templates, database, etc) also has similar extensive documentation.
Same with nginx: lots of documentation, examples, FAQs, (official) blog posts.
For ulib, I only see a very short wiki (by jonathan kelly). For such a huge project (much larger than Flask), only a short "getting started"?!
Examples are great, but, in my perhaps not very humble opinion, there should be an intermediate-level documentation: use cases with key code excerpts.
Suppose you die. Will this great kid of yours continue to live its life on its own?
What do you think?
The text was updated successfully, but these errors were encountered: