we have a hard dependency by using Neos.Seo:StructuredData.* which would fail otherwise in fusion.

Tested with 9.0-dev

Maybe related to #18

We need some more individualizations features:

• Allow adjusting color's via homepage
• Allow adjusting logo via homepage

Relates: neos/Neos.NeosIo#433

https://neos-project.slack.com/archives/C3MCBK6S2/p1688542914136669?thread_ts=1688542588.698759&cid=C3MCBK6S2

This increases code readability and allowes to remove the Neos.Demo:Helper.StyleTag and Neos.Demo:Helper.ScriptTag helper.

This helper is available from neos 6

We need to clean up content elements that we dont need anymore, e.g. Flickr, Registration, ...
In addition we need to clean the setup, make it work on M1, remove compass etc.

Relates: neos/Neos.NeosIo#433

Hello Neos Friends 😊 👋🏼 !

Description

In the current Neos version, you get an exception when you want to add the content element. There was already a ticket for this: #77 but I thought it would be better to open a new ticket.

Informations

• Neos Version: "neos/neos": "~7.1.0",
• Neos.Demo Package Version: "neos/demo": "^7.1",
• Development Environment: DDEV

Jira issue originally created by user siwa_pparzer:

When I try to complete Step 4 in the setup, by importing the demo site i get following error:

Error: During the import of the "Sites.xml" from the package "TYPO3.NeosDemoTypo3Org" an exception occurred: Error: During import an exception occurred: "Exception while property mapping for target type "TYPO3\Media\Domain\Model\ImageVariant", at property path "originalAsset": Tried to refresh the dimensions and meta data of Image asset "" but the file of resource "ed77a0bb1f19cdb992c214197bb1f28dddf29031" does not exist or is not a valid image.".

It's likely the same Bastian Waidelich described here:
https://jira.neos.io/browse/NEOS-1440

What I've done so far:
installed composer
installed neos from composer
configured virtual host
created DB
changed permissions to drwxrwxr-x recursively
completed setup steps 1-3

Image Variant Entries:
persistence_object_identifier | originalasset | name | width | height |
| c1e528e2-b495-0622-e71c-f826614ef287 | ec147d63-a7a9-7029-2cea-95dc381114ab | | 2508 | 1254 |

Image Entries:
| persistence_object_identifier | width | height |
| ec147d63-a7a9-7029-2cea-95dc381114ab | 2508 | 1672 |

Jira-URL: https://jira.neos.io/browse/NEOS-1650

We need Content within the Neos.Demo package that explains how Neos works, how things are developed

We should add the editor registration plugin right on the Homepage in the Teaser-Area (the one with the flower).
If the registration is nicely designed, this is moreless the most important part that (at least on demo.neos.io) a user wants to do, thus ist should be as far up as possible.

The _hidden property is not longer changeable for auto created nodes.

The current demo package creates a "Not Found" - Page automatically. As this property is not longer changeable there is no way (but to manually edit the database content) to enable the prepared custom not found handling.

See also:
neos/neos-ui#2282
neos/neos-ui#3004

We should be able to directly login after registering the user successfully via the frontend form.

We have to provide the fields to the Neos\Neos\LoginController->authenticate action as

__authentication[Neos][Flow][Security][Authentication][Token][UsernamePassword][username]

and

__authentication[Neos][Flow][Security][Authentication][Token][UsernamePassword][password]

No csrftoken is needed.

Triggered by testing the pull request neos/neos-development-collection#4281 (comment) I would suggest to switch the usage of Neos.Neos:PrimaryContent to Neos.Neos:ContentCollection as I can see no advantage of using it in the demo.

Any objections? If not: Do we want to target the changes for v8.3 or introduce them in the v9 branch?

Current usages:

• Page.fusion
• Blog.fusion
• BlogPosting.fusion
• LandingPage.fusion

For NeosDemo we need Content Elements that show pretty well how the editing in Neos works.

Currently the main content area on the demo site is hidden behind the top bar so to add content to an empty page one has to use the content tree to select the collection.

This is due to the demo site making use of CSS adjustments for the backend to fix that, however the new UI doesn't have the same UI state classes added to the body tag as the old UI did.

Currently, we have two content elements for displaying a youtube video on the page.

1. Neos.Demo:Content.CarouselYouTube
2. Neos.Demo:Content.YouTube

Is there a specific reason for that? If not, we should decide which one of the elements should be removed.

Ideas from Neos Sprint Hamburg 2022

• Presentation folder with all components inside
  • More complex components like columns will have a subfolder to contain their parts
  • Remove atoms, section and block folders
• Document Mixin in Page mergen
• Remove restrictions and enforce adding constraints on all nodetypes @Sebobo
• Rename CKConfig
• Add readme to subfolders to explain their use
• MenuItems Recursion @jonnitto
• Remove context dependent setting and replace with simple setting access set by context
• Rename Splide to Slider
• Release notes should contain information about pruning and reimporting the new content
• Explain that Tailwind is an example and people could use anything
• Chapters still have to be renamed @jonnitto

v9 new CR specifics

• Create separate issue #156

We want to make the demo package more approachable for integrators, editors, decides, etc. and also reuse it for our online demo

• Replace meta menu system with homepage menu references property
• Replace "The book" with a news/blog example
• Remove languages except US, UK, DE
• Fix constraints

• Margin between elements
• Print style
• Rendering of asset list
• Rendering of content navigation elements
• Rendering of form elements

• Check refactored code for CR specifics

relates: #147

create a user foo

logout

try to create a new user foo

expect idk ^^

exception is shown

Jira issue originally created by user @Sebobo:

Jira-URL: https://jira.neos.io/browse/NEOS-1677

Neos throws a PHP Warning for every hit on the 404 page.

Neos\Flow\Mvc\Controller\Exception\InvalidControllerException
No controller could be resolved which would match your request. Package key: "", controller name: "Standard". (GET http://domain.tld/non-existing-url)

"/Data/Temporary/Production/Cache/Code/Flow_Object_Classes/Neos_Flow_Mvc_Dispatcher.php in Neos\\Flow\\Mvc\\Dispatcher_Original::resolveController"

throw new Controller\Exception\InvalidControllerException($exceptionMessage, 1303209195, null, $request);

Im not sure if this is a problem of the Neos.Demo or the Neos Core.

Ive never come around reporting it, but look :P

i guess the black bars are not on purpose ... `

(you need a wide screen to reproduce it, or just make the window wider ^^)

.main-header.image {
    background-size: cover;
}

Since #57 the Neos.Demo Sites.xml export contains 5 disabled (aka "hidden") document nodes:

I doubt this was done on purpose, but I might be missing something. @mficzel maybe you can recall?

When we fill the database username, password and select the database and then go to the step three
we got error as below picture

The registration process on demo.neos.io needs to set some more things:

• User Role: RestrictedEditor
• Own private workspace for each user
• Set user base-workspace to that one
• Add media collection and set restrictions

Relates: #433