Ben Balter

Results 111 comments of Ben Balter

> Jekyll doesn't have a dedicated object for includes, and assets in the Core. Good point. For includes, I think we can make our own, like we do data files....

What I'm suggesting: ``` _layouts/default.html : http://localhost:4000/_api/layouts/default.html _includes/include.html : http://localhost:4000/_api/includes/include.html _sass/test.scss : http://localhost:4000/_api/pages/_sass/test.scss assets/css/main.css : http://localhost:4000/_api/pages/assets/css/main.css assets/img/logo.png : http://localhost:4000/_api/static_files/assets/img/logo.png ```

@ashmaroli I asked a few questions over in https://github.com/jekyll/jekyll-admin/pull/344#issuecomment-293915592: > That helps to understand what you want the API to do, but what user-facing functionality are you trying to provide?...

> 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...

It sounds like then, an autocomplete feature would likely need two data sources: 1. Pre-defined choices in config (e.g., colors, sizes, etc.) 2. Pre-defined relationship in config (e.g, authors, products,...

> Yes, though, for the pre-defined relationship, both Siteleaf and Cloudcannon use field naming conventions rather than configuration. Can you explain a bit more?

@parkr would say that that violates Jekyll's [no magic philosophy](https://github.com/jekyll/jekyll#philosophy) because it's an instance of Jekyll trying to be too clever since the user didn't explicitly ask us to do...

> How is this coming along? Not yet started. On our long-term wish list. > Any help needed? Yes please! It'll likely be a matter of creating an HTTP interface...

@mertkahyaoglu I'd caution against putting creds in `_config.yml`, as that's almost always committed to the repo. At the very least, I'd use an environmental variable, but even more simply, I'd...

@xuv thanks for starting the discussion. How would you explain to a developer releasing their first open source project (with no background in copyright or open source licensing) why they...