Adding NixNote v2.0.2 UserDocumentation.pdf content to the wiki

[robert7]

Adding NixNote v2.0.2 UserDocumentation.pdf content to the wiki

[robert7]

OK thx!

I'll will add some intro and check why the page isn't displayed. don't edit it for now.
Regarding attribution i'll add some intro/explanation at beginning of the text. Otherwise its OK to use it (as its GPL and we stay here with GPL).

[robert7]

the page is here but it doesn't seem to be showing up in pane on the right ..

It was due to underline prefix. I'll fixed that.
I also added the intro.

Although I was skeptical about simply dumping all the old content in the new wiki, now I think its helpful. I'll think about what to do with it later. But I'Il probably just let it only add few notes/links/remarks to indicate obsolete information.

Thanks!!

[robert7]

note: ...as I renamed the page, you aren't anymore listed as author :) you may do few more edits, so your name is displayed..

but as there is git underneath the wiki, your contribution is forever there anyway..

[nopivnick]

I was skeptical about simply dumping all the old content in the new wiki

there's so much good information and it's really well organized but it's a lot for one wiki page, to be sure.

I'll think about what to do with it later.

you might want to cannibalize it over time, pulling out one section at a time, checking it for any changes / updates that need to be made, and moving it to it's own wiki page. that would cull it down and make things easier to find as far as using the wiki.

[nopivnick]

I'm happy to help with the above, I just figured it would be best to start with one block of content and have you weigh-in.

[robert7]

OK & i'll try to move the "legacy docs" to a subdirectory. There you can divide in parts, so they can be better indexed and referenced. I think updating/removing unrelevant/obsolete text isn't neccessary - i'll just add remarks marked with "v2.1+" to the parts where the legacy docs isn't valid anymore. And such remards can be added later, when the app changes further.

[robert7]

..I looked up and it seems that folders in github wiki aren't reasonably supported (can't be used for namespacing)..

So I let the file where it is. You may move ahead with dividing it to subpages. But as all pages in wiki need to have unique names, then pls use some prefix. Like I did with "FAQ's". I suggest "Legacy: " prefix. Like "Legacy: Evernote and NixNote Overview" .. "Legacy: NixNote History" ...

[robert7]

I did extract the first 2 chapters. I'm not sure if the "Legacy" prefix is the best, but let start with that. Later this can be changed eventually..