We can then open them from there, in our markdown editor, and edit them all we want. We first create a directory on our server, to hold the Markdown files.See my original post at the top, for my thoughts on why this would be cool. Great news! I’ve managed to put together a solution to my wish, of having ExpressionEngine pull content from Markdown files on the server, directly into entries, and have the site update when changes are made to those files! PS: The quote above doesn’t seem to render correctly, event though the markdown formatting should be correct, at least from here in Safari under macOS 11.2? Which … is easy to say, when it’s not you who has to code it, I know □ > Note: It’s not a full blogging platform, does not currently come with any premade themes, it’s just a script and specific folder structure to load and display markdown files.Īnyways, there are lots of other projects like this, and integrating something similar into EE - which already has the “ load from files to update database” functionality for Templates - might be pretty easy. > Extremely simple “static” PHP blog that renders markdown posts. For example this Github called simply Markdown Blog looks a whole lot like what I’m after, sans the EE integration. I did a bit of research, and a quick google search for “ blog posts from markdown files on server” gave lots of links to projects that might serve as inspiration or starting points. Other than that, the idea is free to run with □ So if anyone wants to take this on, I’d love to beta-test it with you, or be involved in any way. I’m nowhere close to being able to create an add-on myself, and I haven’t been able to find a solution that makes the above possible at the moment. And when online, any changes would be reflected instantly.īecause as great as the EE UI/UX has gotten (and it has gotten really great with EE 6) I think most people like to write longer entries in a real editor, if given the chance. This would enable you to write your content in any editor you like, and work on your content as much as you want, having it just a click away from going online. md file updates the entry in EE and thus online. After you publish, any changes you make to the. md file on the server, ready to be filled with text. A system where any new entries created in a certain channel, would also make a new.Or you could do the reverse, which I think I actually prefer: md file updates the entry and thus is reflected online. You could then add any images, categories and so on you want, and then publish when it’s ready. md file you create there would create a new, closed entry in EE, with the markdown as the body of the entry. A system where EE monitors a folder on the server, for example /system/user/markdown/ and any.I could see it working in a couple of ways: Is there any way I could have the markdown files on the server, and have them auto-update the entries? Exactly like Templates work, where you first create a template in EE, it’s then available on the server as a file, and any changes made to this file is reflected on the site when you save.ĭoes such a system exist already? If not, perhaps an add-on could be made, or it could be a feature of ExpressionEngine in the future? This works great, but also means that any changes will have to be made in Typora first, and then copied over - even small typo corrections and such. When the content goes live (soon I hope) I have to copy/paste the body text from Typora, into a new EE entry with a markdown formatted textarea field. ![]() I’m writing a lot of ExpressionEngine related guides and content at the moment in Typora (a great markdown editor).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |