Re: Documentation Updating

2022-02-23 Thread Ervin Hegedüs
Hi guys, On Wed, Feb 23, 2022 at 10:16:24PM +0100, Thomas Beierlein wrote: > Seems the ball is rolling :-). Fine. :) > Having the main documentation distributed with TLf in the main repo > seems sensible. agree, > Regards Ervins idea of an additional repo I would recommend the > existing

Re: Documentation Updating

2022-02-23 Thread Ervin Hegedüs
Hi all, On Wed, Feb 23, 2022 at 03:12:58PM -0500, Alan Dove wrote: > > Ervin, I can't read a word of Hungarian, but I'll trust that you've > done fine work there. I don't favor splitting the documentation into a > separate project. sorry, parhaps I was misunderstood - I don't want to split the

Re: Documentation Updating

2022-02-23 Thread Thomas Beierlein
Seems the ball is rolling :-). Fine. Having the main documentation distributed with TLf in the main repo seems sensible. Regards Ervins idea of an additional repo I would recommend the existing tlf.github.io for any web page related documents. These documents are easily rendered as GH pages by

Re: Documentation Updating

2022-02-23 Thread Alan Dove
Hey, folks: Ervin, I can't read a word of Hungarian, but I'll trust that you've done fine work there. I don't favor splitting the documentation into a separate project. Let's keep it in the main Github repository and try to stick with (or move things into) Markdown for the reasons already

Re: Documentation Updating

2022-02-23 Thread Ervin Hegedüs
hi there, On Wed, Feb 23, 2022 at 08:33:33PM +0100, Ervin Hegedüs wrote: Just one more thing, > The zipped file is available here: > > https://www.dropbox.com/s/i9bq4ixinh7cm23/tlfdoc.zip if somebody was curious and checked the doc, and didn't realized the effects, just move the mouse over

Re: Documentation Updating

2022-02-23 Thread Ervin Hegedüs
Hi all, On Wed, Feb 23, 2022 at 04:53:42PM +0100, Thomas Beierlein wrote: > Maybe I should give some starters from my point of view: > [...] I can add few more things. Few years ago I started to work on a documentation about Tlf for dummies. I mean for real "dummies", who never saw any Linux,

Re: Documentation Updating

2022-02-23 Thread Nate Bargmann
* On 2022 23 Feb 08:21 -0600, Alan Dove wrote: > Hey, folks: > > As a recent convert to Linux-based ham radio and TLF, I'd like to help > a bit with the project if I can. My coding is rudimentary at best, but > I've worked as a technical writer for over 20 years and feel I could > probably put

Re: Documentation Updating

2022-02-23 Thread Nate Bargmann
* On 2022 23 Feb 10:46 -0600, Nick Craig-Wood wrote: > As a new user (new to both contesting and tlf) I was thinking about helping > with the docs too. Welcome! > I think it would be good for the project to have nice looking online docs. > In another project I'm involved in (rclone) we use

Re: Documentation Updating

2022-02-23 Thread Alan Dove
Tom and Nick: This is off to a great start. I have a bit of spare time today and am starting to work through the files. I'm already working in Markdown so the files will display well on Github, and so far I've edited doc/INSTALL and am just about done drafting a quick start guide in doc/README

Re: Documentation Updating

2022-02-23 Thread Nick Craig-Wood
As a new user (new to both contesting and tlf) I was thinking about helping with the docs too. I thought I'd add my fresh-eyes perspective on the docs here. I could have done with some better getting started instructions. The best ones I've found are here:

Re: Documentation Updating

2022-02-23 Thread Thomas Beierlein
Hi Alan, Am Wed, 23 Feb 2022 09:20:52 -0500 schrieb Alan Dove : > Hey, folks: > > As a recent convert to Linux-based ham radio and TLF, I'd like to help > a bit with the project if I can. My coding is rudimentary at best, but > I've worked as a technical writer for over 20 years and feel I could

Documentation Updating

2022-02-23 Thread Alan Dove
Hey, folks: As a recent convert to Linux-based ham radio and TLF, I'd like to help a bit with the project if I can. My coding is rudimentary at best, but I've worked as a technical writer for over 20 years and feel I could probably put those skills to use on the documentation. I've forked the