According to the "Primer" article:

• Logged in users will see links to Symphony's admin to edit articles, manage comments and add notes.
• Logged in users will see 3 protected menu items, article drafts, the debug page and a link to the Symphony admin.

This is not actually true (and has not been true for a while).

If Symphony is installed in a subdirectory, the link from the "A primer to Symphony 2's default theme" article breaks because it uses an absolute path.

The workspace needs updating to be able to run on 3.0.0.

1. The database engine, collate and charset needs to be changed
2. xslt parameters must be replaced with proper, always defined variables (See symphonycms/symphonycms#2804)
3. Clean up readme

The default workspace is incompatible with Symphony 2.7.x, because install.sql does not honor the new columns (in tbl_sections and tbl_entries). You will see errors like this:

Symphony Fatal Database Error: Unknown column 'e.modification_author_id' in 'field list'

A README file needs to be added to this repository.

At the very least this should include that when updating from the 2.2 workspace (aka. master atm) to the 2.3 workspace (aka integration), that you will need to remove the Login event from your pages and instead attach the the Logged In Author datasource.

In a lengthy discussion about Symphony breaking on corrupted data we asked ourselves : "How can it ever happen that Input fields do not use a UNIQUE KEY on the entry_id column?"

Here is one way: Start your website with this workspace — all input fields are missing the UNIQUE constraint.

I haven't checked any other field types.