The following points are just ideas and are supposed to stimulate a discussion about the future development of Pico. For the more distant changes/improvements planned for Pico 2.0, see #317.

• Allow Markdown configuration (Parsedown doesn't support much configuration, probably it will be limited to the optional usage of Parsedown instead of ParsedownExtra, Parsedown::setBreaksEnabled(), Parsedown::setMarkupEscaped() and Parsedown::setUrlsLinked())
• Add only pages of the first level to the page navigation by default (e.g. page.md and sub/index.md, but not sub/page.md)
  possible BC break, maybe we should defer this to Pico 2.0?
• New default theme using Bootstrap 3 or (provided it has been released already) Bootstrap 4
  possible BC break, maybe we should defer this to Pico 2.0?
• Split Pico::run() into multiple methods, but still call them through Pico::run()
• Add includePico() function to prevent access to $this/Pico object in config/plugin files (use composer's includeFile() function instead?)
• Make theme_url configurable; the default value should support that Pico::$themesDir is a arbitrary deep sub path of dirname($_SERVER['SCRIPT_FILENAME']) (i.e. index.php resp. httpdocs folder); otherwise fallback to themes (and not basename(Pico::$themesDir))
• Support multiple plugin dirs
• Add onSinglePageLoading event (new preliminary event to onSinglePageLoaded)
• When changing the $page parameter of the onSinglePageLoaded event to null, don't add this page to $pages (keeping $page['sub/page'] = null makes no sense, thus no BC break)
• Add Pico::VERSION constant

New official plugins

• Blog features
  • Pagination
  • Tags
  • RSS Feeds
• Editor/Page Admin
• Multilanguage (both contents and themes)