-
-
Notifications
You must be signed in to change notification settings - Fork 614
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
Read any page metadata #63
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
any fields can be added into the page meta section for use in themes e.g. /* BodyClass: amazeballs */ could be used in a template as: <body{% if meta.bodyclass %} class="{{ meta.bodyclass }}"{% endif %}> Specifying a "Template" field will attempt to load a a template html file with that name from the current theme directory e.g. /* Template: spesh */ attempts to use "spesh.html" but falls back to "index.html" if the file does not exist.
get_files() will ignore dotfiles now
allow custom meta fields and templates per page
using composer for markdown
installed markdown and committed so that its still a simple, download > add content deal for install
Removed `config.php` from repo, and replaced w/ `config.php.dist`. This allows users to update their Pico install w/o changing their settings. Additionally now ignoring user added themes.
Removed `config.php` from repo, and replaced w/ `config.php.dist`. This allows users to update their Pico install w/o changing their settings. Additionally now ignoring user added themes.
This was referenced Aug 11, 2013
Closed
Closed
/* Title: Sub Page Custom: Me So Custom */ the `Custom` property can be used in the pages foreach loop as `{{ page.custom }}`.
- Expose file last modification timestamp in page properties
Support for excerpt in meta
I appreciate all of this work guys, but pull requests should be limited to one feature per request. This is great as a fork but impossible to consume in one pull. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Page meta data is not limited to predefined set of keys. No more need for adv-meta plugin (https://github.com/shawnsandy/adv-meta)