yes, custom fields will be in the front matter of the markdown file. Once we have a better UI for editing front matter, it will be less daunting. There will be a UI to edit all the custom fields associated with your file.
You can leave the body of the file empty ā if you donāt need/want any ābodyā content.
The body can be used for short pieces of text (as I showed in the Meet the Team example) or full page content (like a blog post).
The flexibility is already there to use the data from your content as you see fit
Hi Ben - thanks for getting back to me - however you have not confirmed if the sitemaps will specifically reference images, videos, pdfās etc as requested - can you please address this also.
Elements will not reference āresourcesā in the sitemap. It only lists pages, this is standard practice.
In most cases, just pointing to pages is enough, as long as those media files (images, videos, PDFs) are embedded or linked on those pages and are indexable by search engines.
For most websites built in Elements (with clean structure and embedded media), just including the pages is sufficient, search engines will crawl the embedded resources automatically.
This is truly a great improvement and am excited about how this CMS is looking to be. Thank you for the effort and always looking at improving. Greatly appreciated!!!
Proceed with caution ā this weekās video was a very early preview of the CMS. Things can and will change, so please donāt assume anything you saw in the preview will be exactly the same as to when we ship the CMS in Elements!
But it seems if Iām defining a custom field in the front matter that is always going to be under my control as Iām the one defining it. At this point Iām merely interested in figuring out what the custom field are that I will need and whether it will be unwieldy to do what I hope to do.
That is true, but weāre not sure if/how we will expose ācustom fieldsā yet.
I just donāt want you to be disappointed if what we ship isnāt exactly what I previewed ā however, I should have more updates on the CMS next week, so stay tuned for that
Iāll never be disappointed with Elements and the reality is if things end up different from what I have done, it will not be the end of the world to change to the final solution. I have lots of practice.
This brings up an issue Iāve grappled with a few times: some videos that have been posted here are still current and useful, some videos either no longer perfectly describe the feature, are wrong, or the feature has been removed/redesigned. I donāt know which is which until I view a video and try to do what is shown.
A lot of us use the Dan (and now Ben) videos to help us understand something when we find that we donāt quite understand something. It would nice to know which videos really should be deprecated.
Thatās one of the unfortunate side effects of developing an application in public. While things have changed, the general principle of a of the videos (especially those in the past 6 months) are usually very valid.
The user guide videos are usually a good bet. They donāt cover all the features (yet), but weāre adding new videos most weeks as we work towards building out the full-documentation.
The underlying system to fetch data from your markdown files is powered by PHP ā so you will need a server that has PHP installed for the CMS to work.
