Skip to content

Commit e223296

Browse files
Update modernizing-existing-add-ons.md
1 parent 36ef10f commit e223296

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/development/modernizing-existing-add-ons.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,8 @@ NOTE: These changes do NOT break existing add-ons. The old development methodol
1717

1818
The idea of a plugin, module, extension, fieldtype, etc. no longer exists. Instead, an add-on can have a template tag, a fieldtype, or an extension.
1919

20-
In order to harness the new add-on development methodology, you will have to do a few SMALL updates to your existing add-ons.
20+
To utilize the updated method for creating add-ons, you will need to make some small changes to your current add-ons. However, this does not mean that you need to completely convert your add-ons to the new method. After making these updates, you can continue using your existing add-ons and begin creating new ones using the updated method.
2121

22-
TIP: You don't have to migrate your add-on to the new development methodology. After making the following changes, you can leave your add-ons as is, and start new/additional development in the new method.
2322

2423

2524
[TOC]

0 commit comments

Comments
 (0)