-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
English documentation #19
Comments
@wbuck I will write the English document in few weeks, hope more and more people use feather to develop web application |
Awesome, I'm really looking forward to using this framework for an upcoming project I have |
@wbuck I have wrote a part of the English documentation, not finished yet, please give me feedback, i need to know if it is clear enough. https://github.com/qicosmos/feather/blob/master/feather_en.md Compare with coding, writing documentation is boring, but it must be done :) |
I'm at work now, I'll go through the documentation tonight and let you know. Thanks |
I'm just going through the documentation you have thus far but i'm a little unclear with the following:
To be clear, are you saying you must have either the zlib or gzip library installed in order to build? |
There is a compile switch for gzip, so if you want to use gzip, you sholud open the switch in cmakelists.txt firstly, secondly you need install zlib. If you don't want to use gzip, close the switch, and you don't need install gzip. uuid is always needed. I have updated the document to clearify the gzip library. |
I've started to have a look at feather and tried to document my baby steps here: |
@axx I looked at the document, it's great, hope you could continue to write the documents, thank you very much. |
I cleaned up some of the English documentation. I followed a naming convention I saw in other projects. README.en.md contains the English version. Links at the top of each README allow the user to select different languages. I also created a docs folder. Unfortunately this appears to have broken links from the README files. Would you consider organizing the files and directories more? For example, your top level could have docs, demos, src, README, and CMakeLists.txt files. The purecpp example appears to be spread out among several directories. |
There is a docs directory now. |
@qicosmos are websites created using this framework "secure" as in they use HTTPS? if so how to use SSl? |
I watched your talk at CppCon 2018 and I really like the look of this framework. The only thing holding me back from using it is the lack of English documentation.
The text was updated successfully, but these errors were encountered: