# Dev Diary 79: Why we've removed the blog šŸ˜­ **URL:** \ **Category:** Elements\ **Created:** [May 8, 2025, 2:34pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465 "2025-05-08T14:34:49Z")\ **Posts on this page:** 18\ **Page:** 2
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 7:07am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/21 "2025-05-09T07:07:35Z")
> [@handshaper](#): > > the sample you showed where you were using the CMS to setup a header, will this sort of data that uses a custom field always be setup in the front matter? 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. > [@handshaper](#): > > Would the body of the markdown file then be empty as the data would all be in the front matter, correct? 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 šŸ™‚ ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 7:11am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/22 "2025-05-09T07:11:20Z")
> [@csmltd](#): > > Reference to [Elements](https://elementsapp.io/) resources continue within the videos - the resources can be warehoused items I assume? Yes! We already support ā€œRemote Resourcesā€, so you can add resources that are stored anywhere on the internet šŸ™‚ ![CleanShot 2025-05-09 at 09.08.56@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/6/d/6d6781bb800f062d558a1fd8ce462535fa7ded7e.png) > [@csmltd](#): > > In terms of an [Elements](https://elementsapp.io/) sitemap(s) are such sitemaps available and can these be manually configured to incorporate reference to images, videos, pdfā€™s etc? [Elements](https://elementsapp.io/) already produces a sitemap of pages for you. The CMS will be able to generate sitemaps for the content in your CMS. ---
**Author:** ![csmltd](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/csmltd/32/11293_2.png) [@csmltd](https://forums.realmacsoftware.com/u/csmltd)\ **Post date:** [May 9, 2025, 7:31am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/23 "2025-05-09T07:31:41Z")
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. Regards Paul ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [May 9, 2025, 7:35am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/24 "2025-05-09T07:35:46Z")
> [@csmltd](#): > > 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](https://elementsapp.io/) 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](https://elementsapp.io/)** (with clean structure and embedded media), **just including the pages is sufficient** , search engines will crawl the embedded resources automatically. ---
**Author:** ![Lion](https://avatars.discourse-cdn.com/v4/letter/l/57b2e6/32.png) [@Lion](https://forums.realmacsoftware.com/u/Lion)\ **Post date:** [May 9, 2025, 9:41am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/25 "2025-05-09T09:41:44Z")
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!!! ---
**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\ **Post date:** [May 9, 2025, 3:54pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/26 "2025-05-09T15:54:50Z")
> [@ben](#): > > 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. Editing the custom fields in the front matter is not a problem until such time as there is a UI for that editing. I was mainly asking because I wanted to get a jump on using the CMS by starting to create some of the files I know I will be needing. ---
**Author:** ![mrTablet](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mrtablet/32/21819_2.png) [@mrTablet](https://forums.realmacsoftware.com/u/mrTablet)\ **Post date:** [May 9, 2025, 5:05pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/27 "2025-05-09T17:05:39Z")
> [@ben](#): > > Unfortunately not. > > I donā€™t think weā€™re too far away from shipping this in [Elements](https://elementsapp.io/), however, we do have a few core features left to really nail down before we ship a first version. Hope youā€™re ready with a test for us in the build next week šŸ˜€ ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 6:16pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/28 "2025-05-09T18:16:39Z")
> [@mrTablet](#): > > next week Thatā€™s a bit too optimistic Iā€™m afraid. We hope to have something soon, just not quite that soon šŸ˜… ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 6:19pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/29 "2025-05-09T18:19:09Z")
> [@handshaper](#): > > I wanted to get a jump on using the CMS by starting to create some of the files I know I will be needing 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](https://elementsapp.io/)! ---
**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\ **Post date:** [May 9, 2025, 6:33pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/30 "2025-05-09T18:33:30Z")
@ben Advice taken. 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. ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 7:05pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/31 "2025-05-09T19:05:46Z")
> [@handshaper](#): > > Iā€™m defining a custom field in the front matter that is always going to be under my control 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 šŸ™‚ ---
**Author:** ![handshaper](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/handshaper/32/27373_2.png) [@handshaper](https://forums.realmacsoftware.com/u/handshaper)\ **Post date:** [May 9, 2025, 7:18pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/32 "2025-05-09T19:18:28Z")
> [@ben](#): > > 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](https://elementsapp.io/) 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. But Iā€™ll wait to see what you reveal next week. ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 9, 2025, 8:06pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/33 "2025-05-09T20:06:56Z")
> [@handshaper](#): > > Iā€™ll never be disappointed with [Elements](https://elementsapp.io/) ![image](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/b/b/bb48670aa8057eaa549a463d08f80bd575c637cd.gif) ---
**Author:** ![thominator](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/thominator/32/35233_2.png) [@thominator](https://forums.realmacsoftware.com/u/thominator)\ **Post date:** [May 10, 2025, 11:58am UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/34 "2025-05-10T11:58:14Z")
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. ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [May 10, 2025, 2:43pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/35 "2025-05-10T14:43:43Z")
> [@thominator](#): > > 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. 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. > [@thominator](#): > > 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. 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](https://docs.realmacsoftware.com/elements-docs/). Hereā€™s a [link to the User guide Playlist on YouTube](https://www.youtube.com/playlist?list=PLlqV01jBZsjA6LyBb9uY-H7EtHjgO1HcR). Hope that helps! ---
**Author:** ![AnasHyeee](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/anashyeee/32/27982_2.png) [@AnasHyeee](https://forums.realmacsoftware.com/u/AnasHyeee)\ **Post date:** [May 10, 2025, 6:07pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/36 "2025-05-10T18:07:58Z")
Hello šŸ‘‹ I appreciate your hard work in building a great CMS for [elements](https://elementsapp.io/). I like it because it has no installation complexities and safe data from hacking ---
**Author:** ![Beblebroks](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Beblebroks](https://forums.realmacsoftware.com/u/Beblebroks)\ **Post date:** [May 14, 2025, 12:44pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/37 "2025-05-14T12:44:14Z")
Would that been published by [Elements](https://elementsapp.io/) as a final result? Or is that php that generates it underneath? ---
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 14, 2025, 1:49pm UTC](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465/38 "2025-05-14T13:49:18Z")
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. [Previous page](https://forums.realmacsoftware.com/t/dev-diary-79-why-weve-removed-the-blog/47465.md?page=1)