O Plugin Landing Pages permite criar pĂĄginas de destino independentes para sua instĂąncia do Discourse. VocĂȘ pode exibir tĂłpicos, usuĂĄrios e outros conteĂșdos do seu fĂłrum. Ă possĂvel restringir pĂĄginas a grupos, aplicar temas do Discourse, definir caminhos personalizados e gerenciar pĂĄginas em um repositĂłrio git dedicado.
Did you include (or can you include) a site setting to change the Discourse root route to make the root route the specified landing page for the site?
This is a small addition (if it is not included already) and would help users who do not want to fiddle around with their web server and do redirects, etc; and therefore, I think would make this plugin even better.
Yes, Iâm hoping to do that soon. Would you want that in all circumstances though? A list of desired outcomes for guests v users and any other factors would help me think it through.
And we havenât redirected you to /welcome in the last 5 minutes.
The only way currently is via a zip upload or a repo connection. You canât do that via the admin UI yet. But yes, the plan is to add a new âpageâ for site wide settings.
Are there any known incompatibilities with other plugins? Iâm having issues installing this and suspect the procourse static pages might be the culprit.
I havenât tested it, but there shouldnât be any conflicts. The ProCourse static pages plugin is fundamentally different from this plugin from a technical perspective.
Share the specific issue youâre having and weâll see if we can help.
I was having issues with the plugin so I deleted the git from app.yml.
I reinstalled it but all the previous data is still in there.
How can I delete it?
(Basically at the moment when I create a new page. I can add some html but all this over stuff shows like my logo and some footer from pavilion) But I cannot find out where this is being pulled from.
As the global pages.json is proving to be the most confusing / limiting piece of this plugin so far (Iâve received a fair bit of feedback about that), Iâve added it to the Admin UI. Note the âSee furtherâ links in the notes that will take you directly to the relevant part of the docs.
The header and footer attributes will be further defined extended over time (and be editable via a UI instead of via JSON), however at this early stage some flexibility there is best.
hm, not sure whatâs going on there. That console error is unconnected to the landing pages Admin UI. Does this happen every time? Does it happen when you updated specific attributes?
The update is working fine for me in production, for example I just added to the ânoticeâ in our landing pages header: Pavilion | Welcome
{
"root": "/welcome",
"notice": {
"href": "/join",
"text": "We're looking for new members đââïž"
}
}
edit: @Paul_King1 youâre attempting to use bootstrap right? Iâll use this opportunity to create a set of example pages using bootstrap which you can base yours off of. Give me a week.
Thanks for the reply, Iâll have to fiddle with it then. Itâs probably something specific to my installation if I had to guess. Iâll have to see if thereâs a specific error being report, but it wonât let me rebuild the app with this plugin added.
Hey @Paul_King1 sorry for the delay, itâs been a busy few weeks. I decided to make you a little video on the easiest way of using bootstrap with the plugin. Itâs a bit late here and I wasnât using a script, so apologies for any rambling!
Hope that helps you get started. The example page from the video is here: Try Pavilion | Bootstrap
Hey Angus, thanks for this superb plugin. Iâm trying to implement the home redirect patch to redirect / to /welcome. I added your rudimentary patch to the plugin.rb of discourse-landing-pages plugin repo but it isnât working.
This is most likely due to my lack of understanding of how it actually works.
Could you point me in the right direction to implement this? I am a experienced JS dev but just started to learn ruby and discourse architecture.
to the ânoticeâ in our landing pages header: 
