Skip to content
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

Allow for default fields #165

Closed
budparr opened this issue Aug 22, 2016 · 3 comments
Closed

Allow for default fields #165

budparr opened this issue Aug 22, 2016 · 3 comments

Comments

@budparr
Copy link

budparr commented Aug 22, 2016

Following from #140, I'm breaking this issue out.

Allow for default fields. A site owner should be allowed to set up fields in the config file, or elsewhere, which creates consistency and ease of use for content creators:

Here are examples for how others handle this: Prose.io:, Cloudcannon, Siteleaf.

One approach, as mentioned by @benbalter, is that I could have the following in my config:

jekyll_admin:
  default_fields:
    - title
    - description

And then when creating a new post, those fields would be initialized, but empty, by default. This is closest to the prose.io configuration.

@benbalter
Copy link
Contributor

Just to note, if we head down this route, I'd suggest we don't call them "default fields", which could easily be confused with "front matter defaults".

@mertkahyaoglu
Copy link
Member

@benbalter Is it possible to group the default front matters under a name like initial_fields for the api so it would be easy to initialize them in the front end. Currently default ones at the root level like this;

default

@jekyllbot
Copy link

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants