I'm not a coder. Can I still help?

[Skirge01]

Originally Posted by Opus4

Is there anything that would take the original Word doc and convert it, links and all?

Andy

While it may not be able to be uploaded all at once, we could most likely use the original document to avoid retyping some larger pieces by hand. For example, in the version on the wiki, the table of contents for chapter 4 only contains 7 items, while the PDF contains 27.

I could also toy around with uploading text sections of the Word version to see if there's any improvement over how Someassembly got the pages up there.

[Opus4]

OK, I'll try to get it uploaded to github sometime in the next few days.

Andy

[Skirge01]

I added a bunch of " " to get better indentation on the main manual page. It makes spacing in the Contents section at the top look a tiny bit weird, but I think this makes the lower portions much easier on the eyes when browsing. It requires a bit more effort on my part, but I think this is the way to go.

[Someassembly]

Originally Posted by Skirge01

While it may not be able to be uploaded all at once, we could most likely use the original document to avoid retyping some larger pieces by hand. For example, in the version on the wiki, the table of contents for chapter 4 only contains 7 items, while the PDF contains 27.

I could also toy around with uploading text sections of the Word version to see if there's any improvement over how Someassembly got the pages up there.

I must have missed something my; PDF chapter 4 does NOT have 27 items. You may need to confirm I used the correct document.

[Skirge01]

Originally Posted by Someassembly

I must have missed something my; PDF chapter 4 does NOT have 27 items. You may need to confirm I used the correct document.

Hmmm... I thought that chapters 1 & 2 matched what I showed in the PDF when I first started, but I've done so much editing already, I could be mistaken. As a result, I just continued down that trek of making subsequent chapters match how chapters 1 & 2 looked and that turns out to include every child section. Contrast that with what chapter 4 was showing (7 sections), which turns out to only include the title plus child sections one level deep.

Since I already have all the child sections for the first 3 chapters, I'm thinking I may as well continue down that path; unless you disagree. I'm open to differing opinions.

[tmiranda]

Originally Posted by Someassembly

The bulk of the migration of the manual is complete.
SageTV.wikia.com

The Wikia site has some quirks to get used to but; So Far So Good.

I invite help to clean up formatting errors and upload pictures into the manual.


Mike

Nice work Mike. Thank you.

[gary201]

Perhaps a different wiki location/implementation would provide more flexibility at some point.

[Someassembly]

Thank you.

Skirge01 has been doing a lot of work making it user friendly but it is taking shape.

[Skirge01]

Primary chapters are complete as far as being linked from the manual's main page, as well as the headers being formatted and labeled properly for accurate indexing by the Wikia engine, which you can see by the 'contents' sections all nesting the subsections correctly. I'll continue the work by starting the Appendices sometime this week.

I felt that the first big step to getting these sections fixed by people would be if they were able to easily GET TO each of the sections in the first place. I think the next big effort should be fixing formatting errors, such as extra carriage return symbols, bold or italicized words which shouldn't be, etc.

Hopefully the main page of the Wiki can get updated with some more timely info since it gives the impression that it's primarily for European users.

[Opus4]

The SageTV and Studio word doc files are now in github, and the latest Studio manual was updated to the latest PDF file too.

Andy