plugin culture

While ewiki is a rather monolithic script, it allows for extension by
various plugin hooks (= the internal $ewiki_plugins array). This keeps
the core small (just one script) and fast, but also easy to use (not too
cluttered user interface).

However for advanced needs, there is always the option to add a required
function very easily. Of course some plugins slow down your Wiki (for
example markup extensions often do), so it was unwise to enable all at
once. Also a few plugins can be incompatible to each other (very divorce
goals), and some require further configuration and setup in order to
be useful at all.

You may therefore also check out the standalone 'setup.php' script, which
also provides a simplified and _shortened_ overview of the easier to use
plugins. This utility also can generate the appropriate 'config.php' for

The structure of the plugins/ directory is purely presentational, ewiki
does not depend on accessibility of that directory; none of the paths is
hardcoded anywhere. This is because YOU are responsible for loading plugins,
the core script does never load anything on itself. The only exceptions to
this rule are: spages, mpi, and the pluginloader.
prev << "???"
next >> ".meta files"

You cannot modify the README.plugins file, but anyhow any ideas or suggestion should as usually get filed on BugReports, UserSuggestions or even better the README.plugins.Discussion.