Hello everyone,
Imagine you’re building a CMS website for a client. On the homepage, you connect a CMS item to a Markdown file, for example, welcome.md. The client can write something new in this file—unless they rename or even delete it in the editor. If they do either of those things, the CMS loses its connection to the file. That makes sense, of course. Now, if we think from the client’s perspective (working in the editor), who doesn’t realize they’re not supposed to do anything to that linked file except change the content, they could end up crashing the website. You could avoid this by using the Component Collection feature. But since the homepage only has one section for a welcome text, the Component Collection doesn’t make sense here. That text is only changed occasionally; the homepage isn’t a blog page.
Maybe the ITEM component could be designed so you can select either a folder or a Markdown file—for instance, for the homepage, welcome.md would be in the “start” folder. If you specify only the folder, the CMS could always read just the newest file in that folder based on its date. That way, you could easily avoid this potential problem with the client. And in Elements, you’d only have to create the folder structure for the CMS and all the actual content directly in the editor. (Elements currently doesn’t export empty folders.)
Best regards,
Romano
English
@dan
Not a bug, but a potential minor issue.
Hi everyone. Imagine you’re building a CMS website for a client. On the homepage, you link a CMS item to a Markdown file—say, welcome.md. The client can then write new content in it—provided they don’t rename or delete the file within the editor. If they do either of those things, the CMS loses the connection to the file. That makes sense, logically. However, if we consider the client (working in the editor) who doesn’t realize they shouldn’t do anything to that linked file other than edit its content, they could end up crashing the website. You could work around this by using the “Component Collection” feature, but since the homepage only has a single area for a welcome message, a collection doesn’t really make sense there. The text is only updated occasionally; the homepage isn’t a blog page.
Perhaps the “ITEM” component could be designed to allow selecting either a specific folder or a specific Markdown file—for instance, having welcome.md inside a start folder for the homepage. If only the folder were specified, the CMS could simply read the most recent file (by date) from that folder. That would easily avoid this potential issue with the client. Plus, you would only need to set up the folder structure for the CMS in Elements and create all the actual content within the editor. (Elements doesn’t currently export empty folders.)
Alternatively, one could define “sections” to which an MD file is then assigned via the editor.
Best regards,
Romano