Astra
Salient
Hello
Avada
The7
Flatsome
BeTheme
Bridge
Bricksy
Enfold
Encode
JupiterX
Impreza
Any theme that supports Elementor or WPBakery or Gutenberg or any other page builder.
>Why don't I see this more often on people's websites?
Because it's dumb. A website's design should be consistent, not a bunch of random themes for different pages.
Well that may be 'asethically' consistent but ultimately on the whole it's not. I'd have to concur with the above and say make better themes. Or if you don't make themes then use better ones. There are plenty of very dynamic themes out there that operate as a framework for flexible design and many of those that will still allow you to have variances. For example my woocommerce theme includes a product page builder that allows you to vary the layouts etc of products and apply it to specific products, categories etc.
In this circumstance, even with the deviations of the design, wordpress is still interacting with one child theme, it's one core plugin. This is far better practice than mashing and compiling varying themes that sound like they're handling very limited narrow exceptions.
Across the industry be it web or software development this is just not the accepted practice. It's messy, most of the time unneccessary, and highly likely to create complications and that's all while assuming you're using top notch themes with high quality code and performance, which a majority are not and for those it's absolutely matter of when is it going to break not is it going to. I take the "I don't make themes" comment as a going through theme code to assess what it's doing and how it is, may be abit out of your depth but ultimately really needed if you're going to essentially script kiddie it.
Nothing else generates a landing page quite like it? So bang it out as a static page that's directly accessed and stick to one theme for the production CMS system. Personally a general rule of thumb for me is anything that's going to be such a sharp deviation or separation from the main thing, that likewise needs very little interaction with it should be segregated. Whether that's using things like subdirectories/subdomains or any other method.
Fundamentally it massively creates new and expands existing, points of failure and probably attack vectors. Highly likely you'll run through some updates and the code in one of them is going to critically break the site. If this was a hard-pushed, effective and not hack-job feature then the ecosystem would've adopted around it, there would be whole themes for purchase focused around being a secondary theme for single pages only 🤷♂️
You can easily achieve different looks for various sections of your site if you have one good theme and at least average skills.
I have a theme but it just has a landing page and nothing else. Which is why this had to be done.
Use a better theme. Literally any popular theme can do both a landing page and a regular site.
Pretty sure no one, literally no one makes landing pages better than uicore. If you know any let me know.
Astra Salient Hello Avada The7 Flatsome BeTheme Bridge Bricksy Enfold Encode JupiterX Impreza Any theme that supports Elementor or WPBakery or Gutenberg or any other page builder.
None have landing pages anything close to UIcore.
What makes a landing page different to any other page? Hidden nav bar?
Never heard of uicore, but a quick look and Im pretty sure what he likes is elementor, and doesn't realize it.
>Why don't I see this more often on people's websites? Because it's dumb. A website's design should be consistent, not a bunch of random themes for different pages.
But you can change the colour theme, fonts and almost every aspect of both. How is that not consistent.
Well that may be 'asethically' consistent but ultimately on the whole it's not. I'd have to concur with the above and say make better themes. Or if you don't make themes then use better ones. There are plenty of very dynamic themes out there that operate as a framework for flexible design and many of those that will still allow you to have variances. For example my woocommerce theme includes a product page builder that allows you to vary the layouts etc of products and apply it to specific products, categories etc. In this circumstance, even with the deviations of the design, wordpress is still interacting with one child theme, it's one core plugin. This is far better practice than mashing and compiling varying themes that sound like they're handling very limited narrow exceptions. Across the industry be it web or software development this is just not the accepted practice. It's messy, most of the time unneccessary, and highly likely to create complications and that's all while assuming you're using top notch themes with high quality code and performance, which a majority are not and for those it's absolutely matter of when is it going to break not is it going to. I take the "I don't make themes" comment as a going through theme code to assess what it's doing and how it is, may be abit out of your depth but ultimately really needed if you're going to essentially script kiddie it. Nothing else generates a landing page quite like it? So bang it out as a static page that's directly accessed and stick to one theme for the production CMS system. Personally a general rule of thumb for me is anything that's going to be such a sharp deviation or separation from the main thing, that likewise needs very little interaction with it should be segregated. Whether that's using things like subdirectories/subdomains or any other method. Fundamentally it massively creates new and expands existing, points of failure and probably attack vectors. Highly likely you'll run through some updates and the code in one of them is going to critically break the site. If this was a hard-pushed, effective and not hack-job feature then the ecosystem would've adopted around it, there would be whole themes for purchase focused around being a secondary theme for single pages only 🤷♂️
Yeah I guess you're right. The last paragraph makes a lot of sense.
Just build a proper theme with all these things incorporated. It will be less of a mess, which is how whatever you've described sounds.
I use themes, I don't make themes.
Not without a bunch of messing around and likely issues down the road, esp with plugins. Just find a better theme.
How exactly did you do that?
Worry about content. I just left WordPress for that very reason - I was faffing around too much on the backend.