New Year New Site

Showcase
1

So I thought it was time to update the site, inspired by one of the great themes in Bootstrap Studio. Managed to get it pretty much ‘Lighthouse’ friendly.

Added a basic rough ‘guide’ pricing calculator. Added some rich text and created an AMP page in the hope it may help with SEO… hmmm. I also integrated a Wordpress blog so I could start talking the wonderful language of geek :wink:

Anyway enough of my jibber jabber.

4 Likes
2

Nice, love the pricing calculator. BTW the link to “Contact us” on that page gives a 404 (linked to general.html)

1 Like
3

Thanks R, and for the heads up on the bum link, all sorted now.

1 Like
4

This looks nice, good showcase! Can I ask what you’re using for the blog? Is it just static without a CMS? I see some WP in the source code but I wasn’t sure.

1 Like
5

I added a Wordpress install and edited the footer/header.php to mirror the style of the site.

6

Nice. My only criticism is that the exposed plain text email is like rolling out the welcome mat for spammers.

1 Like
7

Thanks for that, all sorted now.

8

The mobile menu button does not work when you’re on the Blog page.

9

I’ve been analyzing your blog page and noticed a few interesting things about how it’s set up. First, it looks like your main website is built using Bootstrap Studio, and the blog section is integrated using WordPress, which is embedded via an iframe within the static blog page. This approach comes with some unique challenges and questions, and I’m curious to know more about how you’ve managed it.

Observations and Questions:

  1. URL Behavior:

    • When navigating within the blog (e.g., viewing different posts), the main page URL (https://flexxit.co.uk/fl-blog.html) remains static and does not reflect the specific post or category being viewed in the iframe.
    • This can impact user experience as users cannot directly share or bookmark specific posts since the main URL does not change. How do you handle this, or is this an intentional design decision?

  2. SEO Considerations:

    • When users or search engines access the WordPress blog directly through URLs like https://flexxit.co.uk/blog/post-name, they encounter a page without the main site’s header or footer. This may create inconsistencies in user experience and could potentially impact SEO.
    • Additionally, embedding content via iframe might limit search engines’ ability to associate the embedded content with the parent page. Have you taken any specific measures to address SEO for these embedded blog pages?

  3. Dynamic Content Loading:

    • It appears that the blog content is loaded dynamically using an iframe, which has some drawbacks, such as the inability to change the URL based on user navigation. One alternative approach could be using AJAX to dynamically load blog content directly into the static page. This would allow the URL to be updated with history.pushState() for a more seamless experience.
    • Have you considered or tried any AJAX-based loading techniques, or do you rely solely on iframe embedding for simplicity?

  4. User Experience:

    • The current setup where blog pages are displayed without consistent headers and footers when accessed directly might confuse users. Have you thought about applying custom WordPress templates to include the site’s main header and footer when users visit blog pages directly?

  5. Potential Solutions for SEO and URL Issues:

    • Implementing server-side rendering (SSR) or pre-rendering can help search engines properly index dynamically loaded content.
    • Another option is dynamic rendering, where the server provides pre-rendered content to search engines while users see the standard AJAX-loaded page. Is this something you’ve considered implementing?

I hope these points help communicate my observations and questions clearly. I used ChatGPT to summarize and express these ideas since I’m not fluent in English, so please let me know if anything is unclear. I’m eager to understand how you’ve approached these technical aspects!

10

Hi, thank you for your feedback.

The blog was a test to see if I could integrate a basic WordPress install as an iframe, and while it worked, I realize it’s not the ideal solution. Your observations have highlighted areas where a more integrated setup could enhance the user experience and SEO, should I decide to keep the blog in its live state. For now, this was more of an experiment, but I’ll consider these improvements if I choose to develop it further.

Thanks,
Kirby