Landing page (not landing page plugin)

Support

AI-generated summary

Landing Page Discussion Summary

User Timothy_Vail is trying to create a simple one-page landing page for his Discourse site, accessible at mysite.com/home. However, after attempting to use the Landing Pages plugin, his site broke, and he couldn’t achieve the desired result.

Merefield suggested an alternative solution using his Home Pages Add-on, which integrates static content from landing pages and adds dynamic pages.

The discussion revolved around the potential issues with the Landing Pages plugin, including a possible bug that caused Timothy_Vail’s site to break. Architect suggested that using a subfolder install for the landing page might be part of the problem.

Merefield asked Timothy_Vail to report the issue on the Pavilion website or the Plugin Topic, including any errors from the browser console and logs. However, Timothy_Vail didn’t save the error or report it.

Merefield later announced that his extension’s Home Pages feature is now merged with the main Landing Pages plugin, and users can install the unified package. However, Timothy_Vail is unsure whether to wait for further integration before installing the plugin.

Merefield explained that he’ll raise a Pull Request (PR) for the backend changes and might not merge the Theme Component (TC). Moin helped clarify the meanings of PR and TC for Timothy_Vail.

1

Hello, I am planning to have a short, simple one page landing page for my site, which is primarily a discourse site.

The main mysite.com is where discourse is at, not mysite.com/discourse.

I want the main site to direct to this main landing page, so mysite.com/home, which should have a different structure than a discourse page.

I have tried landing page plugin, but it has broken my site and does not work the way I want. I have looked at related threads but couldn’t find what I was looking for.

Any suggestions would be appreciated.

2

The landing pages plugin is not broken afaia.

You might like this extension I built:

3

Part of the issue may be using a subfolder install for a landing page instead of a subdomain. (site/page instead of page.site)

This is the plugin that broke your site?:

Might be some kind of a bug with that could be repaired.

4

Yes, it was that plugin. Here is the post about it Repeating header - support - Discourse Meta

I discovered the error was linked to the plugin in the dev console.

5

I’m seeing this in the rebuild (but don’t know if it is problematic) with the required additional plugin…

Plugin name is 'home-pages', but plugin directory is named 'discourse-home-pages'

6

@Timothy_Vail did you raise the issue on the Pavilion website using the bug report wizard or on the Plugin Topic Landing Pages Plugin 🛩?

Make sure you include any errors in the browser console and any obvious errors in logs.

7

I don’t believe this is an issue, it’s just a warning. I chose not to make these things identical because discourse-home-pages is a very unwieldy long string, especially as part of the path!

8

But he said:

Which suggests it is not a subfolder install?

9

Right the main site is not a subfolder, but the landing page was set as a subfolder:

Not sure if that would be a potential problem or not.

10

ah, I see what you are saying.

That’s not really a subfolder as such though, but a specific route.

Well that’s easily solved with my extensions anyway.

11

Thanks @angus for reviewing my FEATURE: Support new Discourse Home Pages Theme Component for highly integrated presentation by merefield · Pull Request #30 · paviliondev/discourse-landing-pages · GitHub, this is now merged, so you can use the main repo of landing pages from now on for the Home Pages feature.

Note you still need the Home Pages Theme Component and the Home Pages plugin installed.

I’ll follow up with another PR to merge the Home Pages plugin code to further simplify things.

12

I did not save the error or report it. I was just trying to fix the issue. If you are rolling your plugin into the landing pages plugin, and it doesn’t cause any further issues, that might be my solution.

Should I wait for everything to be integrated before I go ahead and install the plugin as a unified package?

13

Up to you. I’ll probably raise PR for the backend this weekend.

I don’t think I’ll merge the TC. That will always remain optional.

14

Okay, my apologies, I’m not sure what PR and TC are :slight_smile:

15

Explanation

PR stands for “Pull Request”. It is a way to propose changes to code in a software repository hosted on platforms like GitHub, GitLab, or Bitbucket. A pull request allows developers to review and discuss the proposed changes before merging them into the main codebase.

I really do like the explain feature of the AI helper.

TC is Customization > Theme component