portfolio-performance / portfolio-help Goto Github PK

Unlisted security example descriptions would be useful.

Relevant forum questions:

1. https://forum.portfolio-performance.info/t/handling-of-unlisted-securities-scrip-dividends/3960
2. https://forum.portfolio-performance.info/t/tracking-the-aum-and-performance-of-individual-accounts-and-sub-accounts/19329

PP comes with sample files for user testing and it would be useful if the use could also test the documentation file.

Options:

1. Use an existing sample file
2. Modify and use and existing sample file
3. Add documentation file to program samples

Following the suggestion of @flywire (see https://documentation.divio.com/), the structure of the documentation could be updated. Currently, there are 4 chapters: getting-started, basic concepts, common procedures, and tips & tricks. This resembles vaguely the structure, proposed by divio.com (tutorials <-> getting-started, how-to <-> procedures+tips&trics, concepts <-> explanation, not yet available <-> reference).

@buchen My proposal is:

1. rename the chapter "Common procedures" to "How-to" and make a division into "basic" and "advanced" (the current tips&tricks).
2. add a new chapter "Reference". Structure? Follwing the UI?
3. review the existing text and move them to the appropriate chapter.
4. decide on the location of images: multiple images folders, close to the source text (used to be), one global images folder (current situation)

Today, the help pages only support one language. Plus, it is not trivial to surfe the site with Google Translate.
There is an need and ask - see for example portfolio-performance/homepage#4

Goal:

• Research multi-language support for mkdocs-based help pages
• Setup an initial skeleton with English (and the existing German help pages)
• Describe how/where to contribute pages.

Referenz: #77

Bitte vor pull request.... Rechtschreibprüfung durchlaufen lassen sowie
Grammatikprüfung absolvieren.

Es sind soooooooo viele Fehler und falsche Formulierungen drin.

@hug-sch
Please write the Contributing Rules so that a uniform standard is developed.

please before pull request.... run through spell check and
grammar check.

There are soooooooo many mistakes and wrong formulations in it.

Video setting: (First thoughts)

• At least Full HD resolution - 1080p (1920x1080)
  • I don't know... maybe 1024x768? I dont know...
• Subtitles <->Text possibly in German/English?
  • No sound
• Defined image section of the video content
  • If possible exclusively in the PP software
  • Use in example file → Kommer.xml which is in PP
  • No private PP file with data
  • No private desktop background (solid color)
  • Portfolio performance in "light" mode (no dark)
  • z. e.g. in Windows or Mac → Standard design → "Light" mode (no dark)
  • etc.

Picture/Screenshot setting: (First thoughts)

• Use in example file → Kommer.xml which is in PP
• If possible exclusively in the PP software
• At least Full HD resolution - 1080p (1920x1080)
• No private desktop background (solid color)
• No private PP file with data
• Portfolio performance in "light" mode (no dark)
• e.g. in Windows or Mac → Standard design → "Light" mode (no dark)
• etc.

Originally posted by @Nirus2000 in #77 (comment)

Hallo,

in der aktuellen Version hat sich ein kleiner Fehler eingeschlichen - es öffnet sich bei Programmstart immer ein leeres Fenster mit Menü.
Von dort kann ich dann das zuletzt verwendete File auswählen, welches in einem zweiten Fenster öffnet.
Beide Fenster muss man nach verrichteter Arbeit auch wieder schließen.

Leider öffnet PP beim darauffolgenden Start das zuletzt verwendete File nicht mehr automatisch. (War bei alten Versionen so.)

Version: 0.48.1 (Sep. 2020)
Platform: win32, x86_64
Java: 11.0.4+11-LTS, Azul Systems, Inc.

Liebe Grüße und vielen Dank für das großartige Werkzeug PP!
Dirk

Can the MkDocs Header Page link be enabled for direct navigation to page source: https://www.mkdocs.org/user-guide/configuration/#edit_uri ? (Click Edit on GitHub.)

While technically correct, https://help.portfolio-performance.info/en/reference/ describes panels while PP used the terms sidebar and information pane for the same objects. The documentation should use the same terms as the program.

Top panel would probably better be described as Main pane.

A developer is needed to create the default rule.
It is about formats, video resolutions, writing, image formats, structure, content overlays etc.

The "Contributing rules" from Portfolio Performance can serve as a template here.

Check your GitHub Pages status, you find that GitHub Pages build event did not start.

• Please do not use GITHUB_TOKEN, use ACTIONS_DEPLOY_KEY or PERSONAL_TOKEN
  • cf. peaceiris/actions-gh-pages#9
• Please use the latest version of peaceiris/actions-gh-pages
  • Releases · peaceiris/actions-gh-pages

Hallo @Sn1kk3r5
super Arbeit bisher.... Rechtschreibung... Grammatik.... sehr geil! Saubere Arbeit !! 👍🏻

Eine möchte nochmal den Hinweis geben, dass die Bilder (Screenshots) einheitlich sein sollten.
In Portfolio Performance bitte das "Helle Layout" verwenden, da der "Dark Mode" in den unterschiedlichen Betriebssystemen sich sehr unterscheidet. Die meisten Übereinstimmungen sind eben im "Hellen Modus", was die Standardeinstellung ist.
Auch bitte darauf achten, dass Ihr deutsche und englische Screenshots nicht vertauscht.

Gruß
Alex #

Originally posted by @Nirus2000 in #92 (comment)