@hieu-jan I'll open a PR to this branch, with some WIP changes. Easier for me to explain by writing.

@hieu-jan @hahuyhoang411 For Documentation, one common piece of feedback for both of you is to make your writing concise and succinct. Short sentences, 1-2 line paragraphs, more images, code blocks. Avoid walls of text.

Fortunately for us, we're working on the very technology that helps us with this: LLMs!

I have found Codellama 34b to be fairly good, but you should experiment with ChatGPT as well.

I use the following prompt:

Please transform the following text into a technical documentation format. The new document should be professional, clear, and concise, providing detailed and organized information. It should maintain a formal tone, avoid colloquial language, and be structured with clear headings and bullet points where necessary. The content should be neutral in sentiment, focusing on delivering factual information in a straightforward manner. If applicable, include code blocks, file paths, or URLs to enhance the technical specificity. 

Here is the text to be transformed: [Insert your text here]

@hieu-jan I have done an example of this on the "Installing Jan on Windows" PR here.

While I'm against step-by-step instructions, I would recommend having an image to break up the monotony (e.g. an image of the Windows installer at the top of the screen)

#666

@dan-jan Thanks for your valuable feedback. I will update these docs asap!

@hieu-jan , please rebase main by clicking to Update Branch or via console then the feature Preview URL for PR will be applied to this PR