El plugin Landing Pages le permite crear páginas de destino independientes para su instancia de Discourse. Puede mostrar temas, usuarios y otro contenido de su foro. Puede restringir páginas a grupos, aplicar temas de Discourse, establecer rutas personalizadas y gestionar páginas en un repositorio 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
¡Hola Angus, gracias por este excelente plugin! Estoy intentando implementar el parche de redirección de inicio para redirigir / a /welcome. Añadí tu parche básico al archivo plugin.rb del repositorio del plugin discourse-landing-pages, pero no funciona.
Esto se debe muy probablemente a mi falta de comprensión de cómo funciona realmente.
¿Podrías indicarme el camino correcto para implementarlo? Soy un desarrollador de JS con experiencia, pero acabo de empezar a aprender Ruby y la arquitectura de Discourse.
to the “notice” in our landing pages header: 
