Must have
Why Plone
What is Plone?
Features
Plone 6
Plone ecosystem

Nice to have

They use Plone (needs use cases)
Extend Plone

Example: https://beta.plone.org/get-started has teaser blocks with links but they don't look like links and there is no hover effect.

Suggestion: add some link style and hover style.

Some of the following plone.app.mosaic pages need to be recreated with volto blocks:

• - https://plone.org/community/archived/gsod1 -> not needed
• - https://plone.org/community/gsoc/google-summer-of-code -> https://beta.plone.org/community/google-summer-of-code
• - https://plone.org/events/wpd/about-world-plone-day -> migrated content
• - https://plone.org/what-is-plone/guillotina
• - https://plone.org/what-is-plone/plone-io
• - https://plone.org/what-is-plone/plone/plone-6/plone-6-pitch - NO need
• - https://plone.org/what-is-plone/plone/plone-features - already there
• - https://plone.org/what-is-plone/plone/plonecms -> what is plone
• - https://plone.org/what-is-plone/plone/plonecms-wo-6 - NO need
• - https://plone.org/what-is-plone/plone/try-plone - already there
• - https://plone.org/what-is-plone/volto
• - https://plone.org/what-is-plone/what-is-plone - already there
• - https://plone.org/what-is-plone/zope

Since we have cookie banner, we need to have https://beta.plone.org/privacy-policy

The original plone.org had this in the vulnerability view:

What is missing on the new plone.org:

• The contact information. See original template.
• The overall score. See original template , which gets the score (5.0) from a property on the content type and the scariness (medium) from the view, although that last part could easily be done in javascript as well.
• The nice colours to indicate how bad each item is. Note that "None" is sometimes good and sometimes bad. The template gets the css classes from the view, which gets them from vocabularies in the content type.

I would say the way it looks currently is okay for the moment, but should be fixed before we have a new hotfix.

• We need a restapi endpoint. What would be a good way to do this? Create a serialiser for the vulnerability type which includes all fields plus the above information? Of create an endpoint that specifically gets only the above missing info?
• A view in the Volto frontend to show this.

Release page content is not visible for public users:
https://beta.plone.org/download/releases/6.0.0rc2

Only title is visible if you are not logged in.

https://beta.plone.org/plone-open-garden/

Make it look something like https://plone.org/plone-open-garden/
Use any available blocks that seem useful. Does not need to be 1:1 compared to the orginal.

Note: This is not critical for the 1st release of the new site.

Service Providers
Training

https://beta.plone.org/services

Nice new frontpage to
https://beta.plone.org/foundation

• What is it and why
• Join
• Donate

Current contrast between white links and bacground grey is too low. Change footer background color to #595959 or darker to fix the issue.

Example of the old: https://plone.org/roadmap/

It has past roadmaps and the latest is from 2020, but with Plone 6 realease we should have up to date roadmap.

The "Icons and Text" block columns are left justified. On mobile especially, center is a better visual. Here is some css to center image, title, and text within the columns.

.block-icons-text .columns-wrapper .column-block {text-align:center;}
.block-icons-text .columns-wrapper .column-block.divider_before_title .column-head {justify-content: center;}

There is a visible text </https:> at the bottom of https://migration.plone.org/download/releases/6.0.0rc1.
Looking at beta 1 it gets worse: </https:></https:></https:></https:></https:></https:></https:>
This may be caused by the changelog field, which stores reStructuredText.

[Update: editing makes it worse, I will make a separate issue of this: #59.]

Problem: If a page has youtube embed on top, it shows through dropdown navigation on top

Example: https://beta.plone.org/news-and-events/plone-youtube-channel

Solution: make main navigation z-inder higher.

After migration, go through migrated content and check for problems. Write issues down here.

Since we create new pages for most main sections, old main pages can be hidden.

If you notice CSS-related problems, create new issues of those.

Search field button is empty, resulting to an accessibility error:

Check if that is valid by following the instructions and fix if necessary

What It Means
A button is empty or has no value text.

Why It Matters
When navigating to a button, descriptive text must be presented to screen reader users to indicate the function of the button.

How to Fix It
Place text content within the element or give the element a value attribute.
The Algorithm... in English
A element is present that contains no text content (or alternative text), or an , , or has an empty or missing value attribute.

Standards and Guidelines
1.1.1 Non-text Content (Level A)
2.4.4 Link Purpose (In Context) (Level A)

Currently the contrast is too low. Change body font color to #595959 or darker to achieve AAA level accessibility

For example when you click on "News & Events" only the first of the of the 6 items in there is accessible. Scolling only works sometimes.

At https://plone.org/community/bugs, clicking on the magnifying glass icon shows the search pane, but it is beneath the "There's a bug in my Plone" box.

I'm using Firefox 109.0 on a Linux desktop, the window is 1074px wide; it appears to be a breakpoint-specific issue as full screen is fine.

@ericof you dropped the code to import data from the old site. I resurrected it using my local reflog from revision 5b6f1c0 and will re-add it here.

Dropdown menu is not visible from 992px through 1329px width thus making site navigation impossible media query hides the hamburger. the culprit is https://github.com/media only screen and (max-width: 1329px) and (min-width: 992px) display: none!important

Example:

Reorder Plone news by category and check Plone news by year
https://beta.plone.org/news-and-events/news/plone-news-by-category
https://beta.plone.org/news-and-events/news/plone-news-by-year

Order by effective date, reversed. Resave the page.

The providers page (screenshot below) is a good example of this. The page title Providers is a <h1>, but so is the hero block title. Ontop of this, the hero block line-height is too big, causing a huge gap in the tagline

Create a form for submitting Plone success stories / use cases.

Check for reference:
https://beta.plone.org/news-and-events/news/plone-news-by-category/success-story
https://beta.plone.org/why-plone/they-use-plone

Use Form block to build the form.

Create a page that summarizes default Volto blocks. It is both marketing and documentation, so the proper place might be docs, but it would be nice to have a page for this in plone.org too.

https://community.plone.org/t/browsing-through-available-volto-blocks/15314/3

The cookie banner in the https://beta.plone.org site could use some work.

• Bug: the X close button the right corner always mimimizes user choises to only functional cookies
• Improvement: It is not generally goo to emphasize Accept all -button. Better to emphasize "only necessary" or "save my preferences"
• Feature: need to add/change Google Analytics to Matomo - since we use that to analytics. However, if/when we use YouTube embeds (for Plone 6 screencasts or other), we need to allow Google advertisement cookies.
• Improvement: Make the cookie button less obtrusive on the mobile view? Put it to footer maybe? This is just nice to have.
• Bug: Fix cookie banner contrast issues (image below, tested with Wave toolbar):

Compare:

• Old: https://plone.org/security/hotfixes/
• New: https://migration.plone.org/security/hotfixes/

On the old site, this was likely a special view in plone.app.vulnerabilities. It combines information from the hotfix content items and three configuration registry settings: plone.securitysupport, plone.versions, plone.activemaintenance.

Currently the breadcrumb contrast is too low. Color #777777 is too light grey over white background.

Change to #595959 at least to achieve AAA level accessibility.

Theme: Missing (Play?) icon on the carousel slider. Can be seen on https://beta.plone.org/ frontpage carousel on the first view.

See image bottom:

Overall not bad, but there's plenty to improve, even just looking at the frontpage. Hats off to the contributors and many many thanks for pushing Plone forward!

The first slide button has the same color as the background image.

For some reason, the form block used in Plone.org does not successfully send emails. The form answers are saved successfully, but the emails go nowhere.

You also might get:
"Errore:
Unable to send confirm email. Please retry later or contact site administator."

Examples:
https://plone.org/foundation/contact-us
https://plone.org/foundation/plone-org-feeback-form

The changelog and release notes fields do not work nicely.
I tried editing a changelog to remove some migration cruft, but that made it worse: the whole field is then shown with html codes plainly visible.

The changelog field stores reStructuredText. Maybe that is part of the problem.

Also, I always prepare the changelog (created automatically) and the release notes elsewhere, and then paste it. I tried pasting text in the field, but this does nothing. In the javascript console I see: "TypeError: undefined is not an object (evaluating 'l.children.length')".

Workaround available: use ClassicUI.

what i do:

• I logged in with github
• got to https://plone.org/foundation/members/add?type=FoundationMember
• i fill the form and press save

i get an error:

side note: typo issue in the error message

https://beta.plone.org/download

Maurits's proposa:
"On https://plone.org/download under the Download Plone header, we currently list Plone 5.2 (stable), 5.1 (old-stable), 4.3 (legacy) and Plone 6.0 (future).
I propose that next week we change this to only Plone 6.0 (stable) and 5.2 (old-stable)."
Is a good one.

Also, Plone 5 themes and distributions are unnecessary.

Check out https://beta.plone.org/why-plone/footer-content with improvement suggestions

• Change lists alphabetical -> no need
• Add mastodon link to social media
• Add social media icons -> can be without
• Separate Try Plone link in the first column as CTA -> can be without

For example: https://beta.plone.org/security/hotfix/20220128

• Banner image(s)
• Tagline and clear description what Plone is
• Plone 6 ad
• News, events
• Community
• Feature highlights

Make it good enough for release before Dec 12th 2022.

Current contrast in blue links is too low. Change the color to #005B85 or darker to achieve #AAA level accessibility.
Example https://beta.plone.org/why-plone/features

Even after accepting (or declining) the use of cookies, the cookie consent banner appears again and again when navigating to new pages? https://beta.plone.org/

Sharing tab or user management panel cannot find persons - unable to share local permissions

E.g. https://plone.org/foundation/sponsorship/sponsors/sharing

To replicate: search for a user by using their full name, username or part of the name results to nothing.

Groups can be found.

Only way to share permissions is to give site wide roles, which is not good.

On the old site, you would give the version 6.0.0, and this would be used as id, and the title is then Plone 6.0.0. On the new site, this becomes 'plone-6-0.0' or when you try it in classic I get '6-0.0'. As workaround I renamed it in the good old ZMI...

Note to self: see if I can move a new release to the top automatically.

I try adding a plonerelease:
https://migration.plone.org/download/add?type=plonerelease
Add a version number, say 6.0.0rc2, and click the Save button. Result is an error:

Errore 500: can't set attribute 'title'

For plonerelease objects we do not allow setting a title, because we use the version number for that.

The POST goes to https://migration.plone.org/++api++/download
Traceback as I see it in the response is:

File "/app/lib/python3.10/site-packages/ZPublisher/WSGIPublisher.py", line 167, in transaction_pubevents
    yield
  File "/app/lib/python3.10/site-packages/ZPublisher/WSGIPublisher.py", line 376, in publish_module
    response = _publish(request, new_mod_info)
  File "/app/lib/python3.10/site-packages/ZPublisher/WSGIPublisher.py", line 271, in publish
    result = mapply(obj,
  File "/app/lib/python3.10/site-packages/ZPublisher/mapply.py", line 85, in mapply
    return debug(object, args, context)
  File "/app/lib/python3.10/site-packages/ZPublisher/WSGIPublisher.py", line 68, in call_object
    return obj(*args)
  File "/app/lib/python3.10/site-packages/plone/rest/service.py", line 22, in __call__
    return self.render()
  File "/app/lib/python3.10/site-packages/plone/restapi/services/__init__.py", line 19, in render
    content = self.reply()
  File "/app/lib/python3.10/site-packages/plone/restapi/services/content/add.py", line 55, in reply
    obj = create(self.context, type_, id_=id_, title=title)
  File "/app/lib/python3.10/site-packages/plone/restapi/services/content/utils.py", line 63, in create
    obj = factory(new_id, title=title)
  File "/app/lib/python3.10/site-packages/plone/dexterity/factory.py", line 39, in __call__
    obj = klass(*args, **kw)
  File "/app/lib/python3.10/site-packages/plone/dexterity/content.py", line 347, in __init__
    self.setTitle(title)
  File "/app/lib/python3.10/site-packages/plone/dexterity/content.py", line 629, in setTitle
    self.title = safe_unicode(title)

I guess one way that might solve this, is to add a setTitle method to our content type class.
Okay, that works locally. I will make a PR.

Some UL elements do not have bottom margin. Add 1em bottom margin to UL to improve visual clarity or just make the bottom margin same as in default Volto.

Example https://plone.org/foundation/data-erasure-request

Footer looks different in the beta site https://beta.plone.org/ than in the Mural design

Also, it now has accessibility issues.

This is the design:

The 4 columns and content on the beta site now are good.

Content links need work, but making the visual changes is in the scope of this issue.
Footer content is being decided here https://beta.plone.org/why-plone/footer-content

Create a pretty frontpage with visual listings (using available search blocks and faceted search)

https://beta.plone.org/news-and-events

Could someone batch upload https://github.com/plone/pastanaga-icons like we had on the old dev site? I've just been cherry picking what I need to /icons, but would be nice to have the complete set.

Split off from issue #55. I think this is a frontend task.

Meta question: does it make sense to add labels for this in the issue tracker? Labels like frontend/volto, backend/classic, contents, deployment.

The release page content type has a Files field, which used to be a datagrid field, see screenshot from editing current plone.org:

On beta.plone.org it appears as plain text:

Unified Installer tarball -- builds Plone on most Linux/macOS/Windows 10 systems (5.6 MB, all platforms): https://launchpad.net/plone/5.2/5.2.10/+download/Plone-5.2.10-UnifiedInstaller-1.0.tgz
Unified Installer zip -- same as tarball, but easier to extract on Windows (5.6 MB, Windows): https://launchpad.net/plone/5.2/5.2.10/+download/Plone-5.2.10-UnifiedInstaller-1.0.zip

This format is stable, because this comes from a custom hook from the importer.

It would be good if the Volto view could handle this, either showing it as buttons, as used to be the case, or as simple bullet points. Here is how it used to look, in between the release notes and the changelog:

My workaround: use classic UI to add this text to the release notes instead. I can't do this for all releases, but I did it for 5.2.10 now: https://beta.plone.org/download/releases/5.2.10. I think we will just ignore this for other past releases, and live with some ugly text for now.

For Plone 6 releases we won't use this field anyway: this was only for linking to Unified Installers on LaunchPad, and for Plone 6 we only do Docker.

Nice new front page with real images of real people

Links to migrated content:

• Join
• Teams
• Chat
• Forum
• Conferences
• Events
• Foundation
• Donate

Highlight Plone Conference 2022 and 2023
Highlight WPD 2023

https://beta.plone.org/community

Try
Install
Documentation
Training

https://beta.plone.org/get-started