I am redesigning a rather large website I'm in charge of, and is looking for inspiration on how to organize and display large amounts of posts, in a way that is not terrible on mobile. Lately I've...
I am redesigning a rather large website I'm in charge of, and is looking for inspiration on how to organize and display large amounts of posts, in a way that is not terrible on mobile.
Is there some similar 'framework' behind these sites? Something I might just be able to install on my webhost and start populating the site?
My current site is Wordpress but would like to leave it for Classicpress or another longterm-minded CMS system that doesn't jeopardise stability (AI, crypto) and generally shove unwanted features down my throat.
Your pointers and suggestions are much appreciated!
Do you actually expect content to change frequently? If yes, are those content updates on a very specific part of the site - like blog posts or something? Does a non-technical person need to be...
Do you actually expect content to change frequently? If yes, are those content updates on a very specific part of the site - like blog posts or something? Does a non-technical person need to be able to make updates?
For sites that change once a year or less I've found great success with static sites. You can host and cache a static site extremely cheap.
If you have frequently changing blog posts you may be able to use a headless CMS that triggers a deployment process of the static site.
Every time I've built something with a full featured CMS because the "business wants to be able to make updates" they've had me make every subsequent update anyways. Just through some UI that slows me down. The only advantage I've seen in using some of these CMS is that they might have some sort of integration or widget that cuts down on overall work - but that's been kinda rare too.
The business people are actually right to request full CMS, unfortunately. There are tons of marketing agencies who quite simply refuse to write content for websites that are not running...
The business people are actually right to request full CMS, unfortunately. There are tons of marketing agencies who quite simply refuse to write content for websites that are not running Wordpress. In my old job we literally couldn’t find any who would be willing to use an HTML template for a small business.
If you use a headless CMS it may solve this issue and let you move away from WordPress. Going without a full featured CMS/WordPress doesn’t mean the marketer has to write HTML. You can also setup...
If you use a headless CMS it may solve this issue and let you move away from WordPress.
Going without a full featured CMS/WordPress doesn’t mean the marketer has to write HTML. You can also setup conversion processes to happen automatically. There are several libraries that convert Microsoft Word to markdown for example.
One would think, but even when telling them to just give us copy for us to convert ourselves, we still got no bites! To put things charitably, having a website without Wordpress is like being a...
One would think, but even when telling them to just give us copy for us to convert ourselves, we still got no bites!
To put things charitably, having a website without Wordpress is like being a print shop that doesn’t accept photoshop files. You’ll be missing out on your ability to do business with some important entities.
To put things the way I personally feel, marketing companies are all staffed with slimy inflexible individuals who don’t know what they are doing and the price of doing business is often to sink down to their level.
Make a WordPress backend and use it as a headless CMS to automatically deploy a static site. Best of both worlds! I do understand the struggle. I’ve had to build lots of sites in expensive and...
Make a WordPress backend and use it as a headless CMS to automatically deploy a static site. Best of both worlds!
I do understand the struggle. I’ve had to build lots of sites in expensive and complicated CMS for no reason. I had a company pay for Kentico and then pay a software engineer for every single change to the site afterwards. Nobody from the business ever logged into Kentico. So frustrating.
I assume this is largely Vitepress doing the work, judging from the package.json files in these projects. Edit: ah I see I didn’t refresh this thread before posting
I assume this is largely Vitepress doing the work, judging from the package.json files in these projects.
Edit: ah I see I didn’t refresh this thread before posting
Oh apologies, I poked around the source code and found out the name of it is VitePress
https://vitepress.dev/
Oh that’s cool, thanks for posting the link to it. Static sites generated from good old-fashioned Markdown are a great idea.
I am redesigning a rather large website I'm in charge of, and is looking for inspiration on how to organize and display large amounts of posts, in a way that is not terrible on mobile.
Lately I've been noticing a few sites converging on the same type of structure, that I think might be useful for my purpose:
https://fmhy.pages.dev/
https://dan.valeena.dev/
https://www.debian.club/en/
Is there some similar 'framework' behind these sites? Something I might just be able to install on my webhost and start populating the site?
My current site is Wordpress but would like to leave it for Classicpress or another longterm-minded CMS system that doesn't jeopardise stability (AI, crypto) and generally shove unwanted features down my throat.
Your pointers and suggestions are much appreciated!
Do you actually expect content to change frequently? If yes, are those content updates on a very specific part of the site - like blog posts or something? Does a non-technical person need to be able to make updates?
For sites that change once a year or less I've found great success with static sites. You can host and cache a static site extremely cheap.
If you have frequently changing blog posts you may be able to use a headless CMS that triggers a deployment process of the static site.
Every time I've built something with a full featured CMS because the "business wants to be able to make updates" they've had me make every subsequent update anyways. Just through some UI that slows me down. The only advantage I've seen in using some of these CMS is that they might have some sort of integration or widget that cuts down on overall work - but that's been kinda rare too.
The business people are actually right to request full CMS, unfortunately. There are tons of marketing agencies who quite simply refuse to write content for websites that are not running Wordpress. In my old job we literally couldn’t find any who would be willing to use an HTML template for a small business.
If you use a headless CMS it may solve this issue and let you move away from WordPress.
Going without a full featured CMS/WordPress doesn’t mean the marketer has to write HTML. You can also setup conversion processes to happen automatically. There are several libraries that convert Microsoft Word to markdown for example.
One would think, but even when telling them to just give us copy for us to convert ourselves, we still got no bites!
To put things charitably, having a website without Wordpress is like being a print shop that doesn’t accept photoshop files. You’ll be missing out on your ability to do business with some important entities.
To put things the way I personally feel, marketing companies are all staffed with slimy inflexible individuals who don’t know what they are doing and the price of doing business is often to sink down to their level.
Make a WordPress backend and use it as a headless CMS to automatically deploy a static site. Best of both worlds!
I do understand the struggle. I’ve had to build lots of sites in expensive and complicated CMS for no reason. I had a company pay for Kentico and then pay a software engineer for every single change to the site afterwards. Nobody from the business ever logged into Kentico. So frustrating.
I assume this is largely Vitepress doing the work, judging from the package.json files in these projects.
Edit: ah I see I didn’t refresh this thread before posting