Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Jekyll Admin pre-release #136
If you like to test Jekyll Admin before it's released next week, we'd love your help!
It's easy to get Jekyll Admin installed on an existing site. Here's how:
If you do try the pre-release version of Jekyll Admin, we'd love your feedback. Leave it below, or open a new issues. Happy Jekylling!
: It may be a bit rough around the edges, but it shouldn't break your site (hopefully
First thing i noticed is the warning "You have no title" at the top of the page.
I guessed but didn't know before looking in the code that i should add a title in my global config. Maybe we could add a hint on what the user should do to set a title as this config option is not documented in the docs. Or we could convert it to an input field for a title on click if no title is present?
+1 just installed it, works great.
Just the other day I was thinking of switching to ghost for a CMS, but I didn't want to sacrifice Jekyll's flexibility. Glad I held on!
Hi! I tried on my website and when I want to edit a post, the error "Could not find the document" is displayed. I have a lot of configuration for my posts in scopes. Maybe that's the problem.
Works - thanks!
Findings (apart from "looks pretty & promising!"):
referenced this issue
Aug 20, 2016
@alidcastano All three of those are great ideas. Would you mind opening a new issue for each so that that so we can discuss them further and track their progress?
@frankis do you have a config file? What's it's path relative to the site source?
While there's nothing wrong with doing that for your own site, that's not a design pattern that I've seen widely adopted for Jekyll sites and would recommend putting the title in the config file where other plugins like Jekyll SEO Tag, Jekyll Sitemap, Jekyll Feed, etc. would expect it to be.
Front matter defaults should be applied, in that, when the page is rendered via Jekyll, they will be taken into account, but they do not appear as editable fields on the post/page edit screen. What behavior would you expect to see?
This is the intended, if not unexpected behavior as technically that's a page. Perhaps we should only show pages that render to HTML?
Technically, a post is a document, at least in Jekyll's eyes, but that'd be a good bit of polish to match user expectations.
Could you explain this a bit more? The filename is the filename as it is saved on disk, the permalink is the resulting destination. Would you like the edit screen to show the computed permalink?
Can you explain this a bit more? Steps to reproduce would be helpful here.
First time submitting feature requests, so let me know if there's anything else I should do.
Also, I'd be happy to help with any of those changes. Front end part shouldn't be too hard. I just don't know any Ruby, and have been focusing on learning node.js, so not sure to what degree I can contribute.
Finally got this installed and working although this is not for the faint-hearted, certainly if (like me) they know little about ruby and all the various places where gem files may be installed with various permissions. But after several hours googling and trying options and installing & uninstalling rbenv (which seemed to work as it left ruby 2.3.0 behind in a folder that bundle install agreed to use once rbenv was gone), I got the admin page to appear.
For people who did not have a GemFile before, I found this worked:
Anyway, the web app looks like it will be good but not yet.
The links on the side frequently fail - a refresh of the page usually fixes this.
Pages lists several files that are in sub-folders but does not show that they are in sub-folders and cannot display them.
Posts shows a blank page - I have 78 posts files in the _posts folder. I tried refreshing and got "You don't have any documents." For test purposes, I created a new document. I was surprised that the file name was not created for me when I entered the title. When I saved, it saved correctly to my _posts folder but still does not appear when I try to show Posts.
Static files offers no view option, just download or upload and upload just puts files at root level even though it displays files from many sub-folders.
Configuration: it could be great to have access to css files, layouts and includes as well as _config.yml
Testing in Chrome instead of Safari, I find that the navigation links now work and that the posts are listed.
Really looking forward to using this when it is ready - great job :-)