[WIP] FAQ
#189
Replies: 2 comments 1 reply
-
Although we haven't discussed the format yet, I'm advancing some content. TODO:
First proposed content:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
IMO, it's worth using markdown as a format. Markdown is easily readable as raw text - but it has the added benefit that you can make links to specific FAQ entry. For example if you use ### Question?
Answer Then each question can be uniquely linked. E.g like this: https://github.com/resurrecting-open-source-projects/scrot#generic-installation-instruction |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
Some time ago @eribertomota had an excellent idea: to add a
FAQ (Frequently Asked Questions)
file to the project. The following will be discussed here: file format and its content (questions and answers).Users and collaborators are invited to participate here with, just questions and waiting for an answer, or by creating the question/answer pair. The questions must be imperative and concrete.
After the contributors we will choose which ones will go into the project FAQ archive.
There will be a label called
mark as FAQ
for other discussions outside of this topic that should be noted.The FAQ file will possibly be available to the user from version 1.8, while in the
master
branch it will be included as soon as possible when we have the format resolved and at least 3 questions/answers.First format proposal.
Use plain text file format, UTF-8, indentation with 4 spaces (no tab), text line limit of 74 characters, without file extension, with name all in capital letters called FAQ.
Content:
Another idea is to use the content of the FAQ file to create a scrot Wiki entry, with a more "eye candy" format.
Bye, see you later!
Beta Was this translation helpful? Give feedback.
All reactions