-
-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pico 1.1 and beyond #270
Comments
I plan to take a crack at expanding the Just wanted to reassure you that I'd still like to help and haven't "moved on" or anything. 😉 |
I've moved the Website/Documentation ToDos to #323 |
Moved to PR #334 |
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.
Parsedown
doesn't support much configuration, probably it will be limited to the optional usage ofParsedown
instead ofParsedownExtra
,Parsedown::setBreaksEnabled()
,Parsedown::setMarkupEscaped()
andParsedown::setUrlsLinked()
)page.md
andsub/index.md
, but notsub/page.md
)possible BC break, maybe we should defer this to Pico 2.0?
possible BC break, maybe we should defer this to Pico 2.0?
Pico::run()
into multiple methods, but still call them throughPico::run()
includePico()
function to prevent access to$this
/Pico
object in config/plugin files (use composer'sincludeFile()
function instead?)theme_url
configurable; the default value should support thatPico::$themesDir
is a arbitrary deep sub path ofdirname($_SERVER['SCRIPT_FILENAME'])
(i.e.index.php
resp.httpdocs
folder); otherwise fallback tothemes
(and notbasename(Pico::$themesDir)
)onSinglePageLoading
event (new preliminary event toonSinglePageLoaded
)$page
parameter of theonSinglePageLoaded
event tonull
, don't add this page to$pages
(keeping$page['sub/page'] = null
makes no sense, thus no BC break)Pico::VERSION
constantNew official plugins
The text was updated successfully, but these errors were encountered: