Would like to contribute to the Docs
Hi all,
My name is Anthony McGlone. I am a QA Engineer and I am very interested in making a career switch to Technical Writing.
I've always wanted to learn how to use a vector graphics editor. Documenting a tool like InkScape would allow me to do that and give me a chance to learn some technical writing skills as well.
In terms of my tech writing experience, I have mostly documented how to use test automation suites in Confluence. I know how to use Git and have a basic understanding of GitHub's Markdown tool. I've also used tools like pdflatex to create PDFs.
I can make a commitment of about 5-10 hours per week minimum to this project. I could potentially commit to more hours as I get more experience. I'm happy to help out wherever I can.
Regards, Anthony
PS: Apologies if I should have done this Intro somewhere else.
Welcome Anthony,
I think you have all the needed skills for document writing.
Our documentation team isn't staffed yet, so I have no team or person I can point you to. So far people have been patching together different tasks depending on their needs. If you're interested in focusing on documentation, I'd be happy to answer all your questions and get you set up.
The best place to talk further is chat.inkscape.org where most of the communication happens for the project.
Best Regards, Martin Owens
On Tue, 2022-07-26 at 22:24 +0100, A Mc wrote:
Hi all,
My name is Anthony McGlone. I am a QA Engineer and I am very interested in making a career switch to Technical Writing. I've always wanted to learn how to use a vector graphics editor. Documenting a tool like InkScape would allow me to do that and give me a chance to learn some technical writing skills as well. In terms of my tech writing experience, I have mostly documented how to use test automation suites in Confluence. I know how to use Git and have a basic understanding of GitHub's Markdown tool. I've also used tools like pdflatex to create PDFs.
I can make a commitment of about 5-10 hours per week minimum to this project. I could potentially commit to more hours as I get more experience. I'm happy to help out wherever I can.
Regards, Anthony
PS: Apologies if I should have done this Intro somewhere else. _______________________________________________ Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org To unsubscribe send an email to inkscape-docs-leave@lists.inkscape.org
Hi Anthony,
welcome :)
You can find our documentation team in the corresponding chat channel on rocket.chat at https://chat.inkscape.org/channel/documentation, and our documentation repositories on GitLab in the inkscape-docs subproject: https://gitlab.com/inkscape/inkscape-docs
Lately, we've been working on polishing the Beginners' Guide, have been setting up a guide for documenting internal processes, and have updated the command line documentation.
Do I understand correctly that you're interested in user-facing documentation?
I think what Martin is referring to is developer-facing documentation, which has mostly been handled by the different development teams, e.g. extension devs documented how to write custom extensions, and packagers document how they do packaging etc.
Kind Regards Maren
Am 26.07.22 um 23:42 schrieb doctormo@gmail.com:
Welcome Anthony,
I think you have all the needed skills for document writing.
Our documentation team isn't staffed yet, so I have no team or person I can point you to. So far people have been patching together different tasks depending on their needs. If you're interested in focusing on documentation, I'd be happy to answer all your questions and get you set up.
The best place to talk further is chat.inkscape.org where most of the communication happens for the project.
Best Regards, Martin Owens
On Tue, 2022-07-26 at 22:24 +0100, A Mc wrote:
Hi all,
My name is Anthony McGlone. I am a QA Engineer and I am very interested in making a career switch to Technical Writing.
I've always wanted to learn how to use a vector graphics editor. Documenting a tool like InkScape would allow me to do that and give me a chance to learn some technical writing skills as well.
In terms of my tech writing experience, I have mostly documented how to use test automation suites in Confluence. I know how to use Git and have a basic understanding of GitHub's Markdown tool. I've also used tools like pdflatex to create PDFs.
I can make a commitment of about 5-10 hours per week minimum to this project. I could potentially commit to more hours as I get more experience. I'm happy to help out wherever I can.
Regards, Anthony
PS: Apologies if I should have done this Intro somewhere else. _______________________________________________ Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org To unsubscribe send an email to inkscape-docs-leave@lists.inkscape.org
Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org To unsubscribe send an email to inkscape-docs-leave@lists.inkscape.org
participants (3)
-
A Mc -
doctormo＠gmail.com -
Maren Hachmann