home.social

#pagescms — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pagescms, aggregated by home.social.

  1. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-/repository-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    codedge.de/posts/hugo-with-cod

    toheine.net/posts/2023/website

    gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  2. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-/repository-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    codedge.de/posts/hugo-with-cod

    toheine.net/posts/2023/website

    gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  3. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-/repository-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    codedge.de/posts/hugo-with-cod

    toheine.net/posts/2023/website

    gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  4. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-/repository-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    codedge.de/posts/hugo-with-cod

    toheine.net/posts/2023/website

    gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  5. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-/repository-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    codedge.de/posts/hugo-with-cod

    toheine.net/posts/2023/website

    gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  6. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at
    Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    https://www.codedge.de/posts/hugo-with-codeberg-bunnycdn/

    https://toheine.net/posts/2023/website-deployment/

    https://gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  7. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at
    Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    https://www.codedge.de/posts/hugo-with-codeberg-bunnycdn/

    https://toheine.net/posts/2023/website-deployment/

    https://gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  8. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at
    Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    https://www.codedge.de/posts/hugo-with-codeberg-bunnycdn/

    https://toheine.net/posts/2023/website-deployment/

    https://gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  9. Off to new shores

    Now that I dropped Pure Blog from the list of projects to pursue as it is too limited for my purpose, I started to have a closer look at
    Hugo for a blog on webspace I own.

    Perhaps with something like Pages CMS on top of a Git-based workflow - for convenience.

    But I would prefer to have some non-US non-profit alternative for GitHub. And Codeberg (Forgejo) e.g. is exactly that.

    There are options.

    But I am grateful for more proposals how to bring this to life.

    https://www.codedge.de/posts/hugo-with-codeberg-bunnycdn/

    https://toheine.net/posts/2023/website-deployment/

    https://gohugo.io/tools/front-ends/

    #blog #pureblog #github #git #hugo #headless #CMS #codeberg #forgejo #pagesCMS #nonUS #nonProfit

  10. @Palleas @11ty nice! I'm not sure what the advantage might be of separating the data out into post files? You could probably dynamically created posts at build time if you wanted them to have their own pages.

    But the more important question is, are they unique dog counts or can you count the same dog more than once? 🐕

    Or actually, if you wanted to use something like #pagescms to manage your content that might be a reason to have seperate files, maybe.

  11. @Palleas @11ty nice! I'm not sure what the advantage might be of separating the data out into post files? You could probably dynamically created posts at build time if you wanted them to have their own pages.

    But the more important question is, are they unique dog counts or can you count the same dog more than once? 🐕

    Or actually, if you wanted to use something like #pagescms to manage your content that might be a reason to have seperate files, maybe.

  12. @Palleas @11ty nice! I'm not sure what the advantage might be of separating the data out into post files? You could probably dynamically created posts at build time if you wanted them to have their own pages.

    But the more important question is, are they unique dog counts or can you count the same dog more than once? 🐕

    Or actually, if you wanted to use something like #pagescms to manage your content that might be a reason to have seperate files, maybe.

  13. @Palleas @11ty nice! I'm not sure what the advantage might be of separating the data out into post files? You could probably dynamically created posts at build time if you wanted them to have their own pages.

    But the more important question is, are they unique dog counts or can you count the same dog more than once? 🐕

    Or actually, if you wanted to use something like #pagescms to manage your content that might be a reason to have seperate files, maybe.

  14. @Palleas @11ty nice! I'm not sure what the advantage might be of separating the data out into post files? You could probably dynamically created posts at build time if you wanted them to have their own pages.

    But the more important question is, are they unique dog counts or can you count the same dog more than once? 🐕

    Or actually, if you wanted to use something like #pagescms to manage your content that might be a reason to have seperate files, maybe.

  15. @chakie I'm a big fan of #eleventy if you like designing front ends. You can use something like #pagescms, or the eleventy-import plugin to import from WP and keep it as your CMS.

    (I say this as a very long-time WP dev)

  16. @chakie I'm a big fan of #eleventy if you like designing front ends. You can use something like #pagescms, or the eleventy-import plugin to import from WP and keep it as your CMS.

    (I say this as a very long-time WP dev)

  17. @chakie I'm a big fan of #eleventy if you like designing front ends. You can use something like #pagescms, or the eleventy-import plugin to import from WP and keep it as your CMS.

    (I say this as a very long-time WP dev)

  18. @chakie I'm a big fan of #eleventy if you like designing front ends. You can use something like #pagescms, or the eleventy-import plugin to import from WP and keep it as your CMS.

    (I say this as a very long-time WP dev)

  19. @chakie I'm a big fan of #eleventy if you like designing front ends. You can use something like #pagescms, or the eleventy-import plugin to import from WP and keep it as your CMS.

    (I say this as a very long-time WP dev)

  20. What I thought was an error in setting up #pagescms with post tags actually turned out to be an issue in #eleventy whereby I had one post with the tag 'CMS' and another with the tag 'cms'. It was trying to write two different tags to the same url /tags/cms and getting confused.

    I changed the lowercase one to uppercase (personal preference) and the site built. Not sure why it treated them differently but glad I got to the bottom of it.

  21. What I thought was an error in setting up #pagescms with post tags actually turned out to be an issue in #eleventy whereby I had one post with the tag 'CMS' and another with the tag 'cms'. It was trying to write two different tags to the same url /tags/cms and getting confused.

    I changed the lowercase one to uppercase (personal preference) and the site built. Not sure why it treated them differently but glad I got to the bottom of it.

  22. What I thought was an error in setting up #pagescms with post tags actually turned out to be an issue in #eleventy whereby I had one post with the tag 'CMS' and another with the tag 'cms'. It was trying to write two different tags to the same url /tags/cms and getting confused.

    I changed the lowercase one to uppercase (personal preference) and the site built. Not sure why it treated them differently but glad I got to the bottom of it.

  23. A follow up to my 'what CMS?' post the other day, I picked one to try out - #pagescms

    Apart from the fact I can't get my tags to work yet, so far so good.

    alansuspect.dev/blog/i-picked-

    #eleventy #cms #webdev #ssg

  24. A follow up to my 'what CMS?' post the other day, I picked one to try out - #pagescms

    Apart from the fact I can't get my tags to work yet, so far so good.

    alansuspect.dev/blog/i-picked-

    #eleventy #cms #webdev #ssg

  25. @kantel #PagesCMS sieht interessant aus. Wenn man nicht unbedingt GitHub als backend nutzen will macht auch #DecapCMS Sinn, das ist ein fork? des NetlifyCMS.

  26. @kantel #PagesCMS sieht interessant aus. Wenn man nicht unbedingt GitHub als backend nutzen will macht auch #DecapCMS Sinn, das ist ein fork? des NetlifyCMS.

  27. @kantel #PagesCMS sieht interessant aus. Wenn man nicht unbedingt GitHub als backend nutzen will macht auch #DecapCMS Sinn, das ist ein fork? des NetlifyCMS.

  28. @kantel #PagesCMS sieht interessant aus. Wenn man nicht unbedingt GitHub als backend nutzen will macht auch #DecapCMS Sinn, das ist ein fork? des NetlifyCMS.

  29. Pages CMS: Ein CMS für statische Seiten auf GitHub Pages

    Bekanntlich bin ich ja ein großer Fan statischer Seiten und auch dieses Blog Kritzelheft besteht aus von Quarto angetriebenen, statischen Seiten, die auf GitHub Pages gehostet werden. Leider mangelt es fast allen mir bekannten Generatoren statischer Seiten an der Einfachheit, die zum Beispiel ein Content Management System wie WordPress auszeichnet. kantel.github.io/posts/2024030 #StaticSite #GitHubPages #PagesCMS

  30. Pages CMS: Ein CMS für statische Seiten auf GitHub Pages

    Bekanntlich bin ich ja ein großer Fan statischer Seiten und auch dieses Blog Kritzelheft besteht aus von Quarto angetriebenen, statischen Seiten, die auf GitHub Pages gehostet werden. Leider mangelt es fast allen mir bekannten Generatoren statischer Seiten an der Einfachheit, die zum Beispiel ein Content Management System wie WordPress auszeichnet. kantel.github.io/posts/2024030 #StaticSite #GitHubPages #PagesCMS

  31. Pages CMS: Ein CMS für statische Seiten auf GitHub Pages

    Bekanntlich bin ich ja ein großer Fan statischer Seiten und auch dieses Blog Kritzelheft besteht aus von Quarto angetriebenen, statischen Seiten, die auf GitHub Pages gehostet werden. Leider mangelt es fast allen mir bekannten Generatoren statischer Seiten an der Einfachheit, die zum Beispiel ein Content Management System wie WordPress auszeichnet. kantel.github.io/posts/2024030 #StaticSite #GitHubPages #PagesCMS

  32. Pages CMS: Ein CMS für statische Seiten auf GitHub Pages

    Bekanntlich bin ich ja ein großer Fan statischer Seiten und auch dieses Blog Kritzelheft besteht aus von Quarto angetriebenen, statischen Seiten, die auf GitHub Pages gehostet werden. Leider mangelt es fast allen mir bekannten Generatoren statischer Seiten an der Einfachheit, die zum Beispiel ein Content Management System wie WordPress auszeichnet. kantel.github.io/posts/2024030 #StaticSite #GitHubPages #PagesCMS