Headless CMS

Definitions & benefits

Tools & Concepts

Open source

Features

Authentication

Custom plugins & Marketplace

Webhooks

Multilingual CMS

APIs

Dynamic Zones

User roles & permissions

Content Modeling

Security & Privacy

Use Cases

Ecommerce

Blog

Forum

About Strapi

Life at Strapi

Releases & Roadmap

Events

Community

News

The Tutorials section covers an introduction to Strapi, some advanced technical content, product updates and releases. From basic workaround to in-depth development guides. 

Tutorials

How tos

Get all the latest updates, news and events.

Subscribe to the newsletter 📣

We just released the v1.5.0, the first long term support version. The main change is the admin panel is now open-sourced and built-in your generated Strapi applications.

We first decided to spread the admin as a service to maximize the backward compatibilities and minimize the risks of a broken admin. But we are aware everyone prefers it as an open-source project that’s why we decided to change our mind to meet your needs.

Framework:

- Added git pre-commit automation tool aiming to launch tests before committing.
- Use tilde ranges for npm dependencies to avoid breaking changes.
- Added a ‘--dry’ option when generating an application not to have built-in ORM and features.
- Improved the restart process and automatically install adapters and template engines on config changes.
- The admin panel is now open-source and built-in your applications. This includes a suppression of the ‘dashboard’ hook.

User Management:

- Generate different JWT secrets for each environment.
- Prevent double password encryption.

Documentation:

- Add documentation about session configuration.
- Add documentation about the open-source admin panel.
- Add documentation about the ‘--dry’ option.

Studio:

- Improved database verification to make sure you don’t write wrong information.
- Improved global UX to make comprehension easier.
- Improved socket management to make connections between applications and the Studio faster and cleaner.
- Added application configuration and environment settings to let you manage your application preferences.

The v1.5.0 is the last minor release before the v2.0.0, which will be released in the next few months with some major changes.

We are really happy to see Strapi’s community growing up every day.

Your feedback is our motivation. Thank you all for your awesome support.

The Product section covers our releases, feature reviews and more. 

Product

Release v1.5.0

Loic is a Data Engineer, founder @ Nunchi and teaching at the Web School Factory. 

This release includes some interesting changes on the Strapi ecosystem such as the migration from 'passport' to 'grant' with 'purest' for user's authentication.

Framework:

- Improved the module loader to load config from API and specific environment.
- Improved the restart and rebuild processes thanks to clusters.

User Management:

- Migrated from 'passport' to 'grant' with 'purest'.

Documentation:

- Fixed user routes.
- Updated configuration paths for the new module loader.

Website:

- Added a RSS feed.

Studio:

- Added a preview for relations between models.
- Removed the summary page at the end of the API building process.

Dashboard:

- Improved permissions interface.
- Improved the creation process with auto-filled inputs.
- Use a dashboard token as a CORS header.

We owe huge gratitude and props to our contributors for their feedback and the work they did to make this release possible

Release v1.4.0

This release includes a few improvements of the Strapi framework but the most important change is the new Dashboard as a Service for clients.

Framework:

- Added an 'explorer' hook to dialog with the Dashboard as a Service.
- Used the 'passport' node module as a middleware.
- Removed useless request when logout action via the CLI.

User Management:

- Removed 'passport' useless sessions.
- Fixed error messages.
- Added a 'deleteRole' policy for more security.

Documentation:

- Added a lot of examples.

Website:

- Added a 'F.A.Q.' page.
- Added a 'How it works' page.

As you may know, we decided to separate the Studio and the Dashboard because the Studio is dedicated to developers with development tools and the Dashboard to clients with data management tools. Clients don't need to see what's going on, they only need to access their data, nothing more. Developers take care of the REST.

Thank you very much all for your live feedback on [Slack](http://slack.strapi.io) and your PRs on [GitHub](https://github.com/wistityhq/strapi).


Release v1.3.0