Zrzuty ekranu w `docs/screenshots` są nieaktualne po zmianach panelu w 8.1.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- php
- Domain
- documentation
Research direction
Review screenshots 01–05 in docs/screenshots, especially docs/screenshots/02-template-editor.jpg, and compare them with the current panel described by lang/en/lang.php and models/template/columns.yaml. After the 8.1.0 UI changes are complete, follow the Marketplace screenshot procedure to capture replacements at 1116×838 JPG. Done when screenshots 01–05 match the 8.1.0 panel.
Written by the indexing model from the issue text.
Description
Problem
Zestaw zrzutów pochodzi z efc9a16 (#178). Po #179, #182, #254, #256 i #259 panel wygląda inaczej:
- „New Template” jest teraz „New template”, kolumna „Name” to „Title”;
- „Edit Template” jest teraz „Edit template”, „Save and Close” to „Save & Close”;
- brak podpowiedzi o pliku widoku (
_view_status, „This template follows the view file…”); - komentarz pola Sample data ma inną treść;
- tytuł podglądu „Default” zastąpiło „Invoice” (#179);
- w zrzucie layoutu brakuje
background-size(#182).
Dowód
docs/screenshots/02-template-editor.jpgpokazuje „Edit Template”, „Save and Close” i brak podpowiedzi o widoku.git show efc9a16:lang/en/lang.phpigit show efc9a16:models/template/columns.yamlvs obecnelang/en/lang.php,models/template/columns.yaml. Przejrzane wszystkie zrzuty 01–05.
Skutek
Strona pluginu na Marketplace pokazuje inny panel niż ten, który użytkownik dostanie po instalacji 8.1.0.
Proponowane rozwiązanie
Nowe zrzuty po zamknięciu zmian UI dla 8.1.0, według procedury zrzutów Marketplace (1116×838 JPG).
Kryteria akceptacji
- Zrzuty 01–05 odpowiadają panelowi z wydania 8.1.0.
Powiązane issues
#165/#178.
- Dominant language
- PHP
- Stars
- 30
- Forks
- 22
- Avg merge
- 11m
- Merged PRs (30d)
- 80
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
majorsilence/Reporting#493 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Automattic/safe-publish#764 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 2/5 1-3 hours Newbie friendliness 68/100