Reading paths for DXP developers #

This page is for developers who want to read the DXP pages in a useful order. Pick the path that fits you; the times are rough reading times, without hands-on work.

Contents #

1. The evaluator (45 minutes)
2. The first week (one day of reading)
3. The theme builder (two hours)
4. The API integrator (two hours)
5. The migrating team (half a day)
6. The operator (two hours)

The evaluator (45 minutes) #

For architects and leads who decide whether to use the DXP.

1. What Exponential Platform DXP is
2. What the DXP ships and what it does not
3. Choosing DXP, Legacy, Nexus or Exponential 6
4. Claims to avoid
5. Licensing

The first week (one day of reading) #

For developers who join a DXP project.

1. Versions, Installing, Environment variables
2. The project directory layout, Siteaccesses
3. Content, content types and locations, Field types
4. Twig and the design engine, Twig functions
5. Console commands, Day-to-day commands
6. Troubleshooting

The theme builder (two hours) #

1. Twig and the design engine
2. The standard design and your theme
3. Twig functions you use daily, Twig components
4. Image variations, Building assets
5. From the designer audience: Accessibility basics for themes, CSP-safe design

The API integrator (two hours) #

1. The REST API, JWT authentication
2. GraphQL and GraphiQL
3. Headless with the DXP
4. HTTP cache

The migrating team (half a day) #

1. Coming from Ibexa OSS or eZ Platform or Coming from Exponential 6
2. The se7enxweb forks and replace
3. 16. Migrating from eZ Platform and Ibexa
4. The 4.6.x skeleton, if your source is 4.x

The operator (two hours) #

1. Web server setup, File permissions
2. Databases, Application cache
3. Cron, Messenger, Reindexing
4. Deploying, Updating, Project checklist

Related pages #

• DXP Developers: start here
• Reading paths for developers (Exponential 6)
• Glossary for DXP developers
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.