Publicación de página

[Discourse]

Esta guía cubre cómo usar la función de Publicación de Páginas (Page Publishing) en Discourse. Esta función permite a los usuarios del Staff convertir un tema en una página estática independiente con un estilo personalizado. Ejemplos incluyen las páginas de Términos de Servicio y Política de Privacidad.

Nivel de usuario requerido: Staff

Publicación de páginas estáticas en Discourse

La Publicación de Páginas permite a los usuarios del Staff crear páginas estáticas independientes a partir de temas. Esto es similar al proceso para crear páginas de Términos de Servicio o Política de Privacidad.

Resumen

Esta documentación cubrirá:

• Habilitar la Publicación de Páginas
• Publicar un tema como página
• Despublicar un tema
• Problemas comunes y soluciones
• Preguntas frecuentes (FAQs)
• Recursos adicionales

Habilitar la Publicación de Páginas

1. Navega a Admin > Settings (Ajustes).
2. Activa la configuración enable page publishing (habilitar publicación de páginas).
   

Habilitar la publicación de páginas cuando se requiere iniciar sesión

Para permitir que las páginas publicadas sean visibles incluso cuando un usuario no ha iniciado sesión:

1. Activa la configuración show_published_pages_login_required en Admin > Settings (Ajustes).
   

Publicar un Tema

1. Ve a la primera publicación de un tema público y selecciona el icono de elipsis (...).
   

2. Selecciona el icono de llave inglesa.
   

3. Elige la opción “Page Publishing” (Publicación de Páginas).
   

   

4. Aparecerá un cuadro de diálogo modal, que te permitirá confirmar el slug (que se puede rellenar previamente con el título de la publicación) y previsualizar la URL de la página publicada.
   

   

Para permitir la publicación de páginas, es necesario desactivar la configuración del sitio secure upload.

Para sitios alojados, las cargas seguras están limitadas al plan Enterprise.

Tema Publicado

• Si la opción Public (Público) está marcada, aparecerá una etiqueta public.
  
  

  

• Un tema publicado mostrará un aviso debajo del título que permite acceder a su configuración de publicación.
  

  

Página Publicada

Despublicar un Tema

1. Selecciona Publishing Settings (Configuración de Publicación) debajo del aviso.
   

   

2. Haz clic en Unpublish (Despublicar)
   

   

3. El tema se despublica.
   

   

Problemas comunes y soluciones

No se pueden ver las páginas publicadas al cerrar sesión

Asegúrate de que la configuración show_published_pages_login_required esté activada en Admin > Settings (Ajustes).

Añadir una cabecera de Discourse a las páginas publicadas

Actualmente, las páginas estáticas están pensadas para ser mínimas y no incluyen la cabecera y el pie de página típicos de Discourse.

Preguntas frecuentes (FAQs)

¿Puedo hacer pública una página de Preguntas Frecuentes o Acerca de?

Puedes crear un tema nuevo con el contenido deseado y publicarlo como una página. Cambia los enlaces en la configuración del sitio para que apunten a estas nuevas páginas.

¿Cómo puedo personalizar la apariencia de una página publicada?

Utiliza la estructura del documento HTML y los selectores CSS correspondientes para aplicar estilos personalizados en Admin > Customize (Personalizar) > Themes (Temas) > CSS.

Recursos adicionales

• Making custom CSS changes on your site
• Secure Uploads

[downey (Michael Downey)]

I still need to try this out first hand so the following may not be grounded in reality, but:

It strikes me that this permission model sets up a scenario where you always see two copies of the pages’ content – one in the relevant Discourse category, and one in the published pages themselves. This of course seems duplicative if you’re wanting to publish pages for the general population that is similar to, or identical to, your Discourse user base.

OTOH, if pages had the “world readable” flag available, you could then restrict who can see/edit them to a small group, and the only place the content would be available to other Discourse users would be in the published links themselves.

(I’m thinking of a use case of a “documentation site” here.)

Otherwise, I’m pretty excited to test things out!

[nathank (Nathan Kershaw)]

Awesome stuff, and thanks again for listening to your users. I love the ‘lets make this better for us all’ vibe that Discourse has! We’ll make heavy use of this.

When discussing one use (patching up an install that went a bit awry), another user pointed out a remaining bit of icing that could do with going on the cake:

@Paul_King

not sure why FAQ is omitted from sign up dialog, but you can also set this url here as well - though not sure purpose of this feild/what otherwise links to it if not included in signup dialog?

Hey, is there any way to include the ability to make /faq and /about public as well, as they are currently hidden in Login Required sites. We can of course use the existing functionality that you’ve just released for /faq by making our own, changing the link in settings, and explicitly linking to it. However, this is not pretty and the existing navigation to it remains hidden. We can’t do that at all for /about of course.

[core]

Something that would go nice with this feature is to make publications onebox-compatible such that people could easily share the content.

[DanDevine]

Please excuse my ignorance, as I am very much a beginner in the HTML/CSS space… however, how would we go about applying our theme colour choices to published pages. At its simplest, I’d like to use the dark background/white text to give the published pages the same darkmode experience as accessing our forums.

Is this already in the product, or do I need to play with HTML/CSS? If the latter, could anyone give me some pointers in the right direction? Thanks!

[j.jaffeux (Joffrey Jaffeux)]

@nathank

Hey, is there any way to include the ability to make /faq and /about public as well, as they are currently hidden in Login Required sites. We can of course use the existing functionality that you’ve just released for /faq by making our own, changing the link in settings, and explicitly linking to it. However, this is not pretty and the existing navigation to it remains hidden. We can’t do that at all for /about of course.

Can you make this a separate feature request please? This is not related to page publishing, as in I wouldn’t have to change anything related to page publishing to make it possible. I do agree it would be better if all these “static” pages could have more or less the same behaviour, but there are multiple solutions here (do nothing? add site settings? migrate these to page publishing?), so we might want to have a dedicated topic for this.

[Terrapop]

GTM not loaded on published pages? Would be nice.

[RGJ (Richard - Communiteq)]

@j.jaffeux

but wouldn’t that cause error with other themes trying to load code which is not available?

Hmm that is a really good point.

Just trying to think of a solution here… would it work if type="text/javascript" and type="text/discourse-plugin" were treated differently? The API needs the latter, right?

[j.jaffeux (Joffrey Jaffeux)]

Yes I think we already support having a text/javascript in the theme fields, so there are certainly solutions in this area.

[Terrapop]

That would be great.

[pfaffman (Jay Pfaffman)]

@j.jaffeux

at the moment page publishing is not designed to support theme components or anything using plugin api and especially decorateCooked.

So it’s currently impossible to have responsive published pages, and this site particularly wants

1. images made available when sharing to public media, and
2. responsive/resizing images displayed, especially on mobile–oh, mobile could just resize the image with CSS–that should work, right?

[syl]

+1 for having the Discourse header in published pages. I’m missing my website logo, custom header links and beloved hamburger menu

Another oddity: in posts, my lightboxed images open in a nice popup, whereas in published pages, they open in a new tab…

[pfaffman (Jay Pfaffman)]

I think what’s needed is a set of theme components that add such. The last client I had to use this wanted the topic creator removed. I think it’s hard to guess what will meet people’s needs for this!

[RGJ (Richard - Communiteq)]

Are there currently any ongoing efforts for adding “simple” (non-API) Javascript support to published pages? Or should we forget about this near- to mid-term ?

[ddf]

Can i display external non-Discourse JSON on this page? Because we can’t use php code here and discourse strip most of html so i do not know how to do it…

[Ed_Bobkov (Ed)]

I have a problem with a published page - the button to copy the content of the code block is not visible on a published page. Screenshot: Screenshot by Lightshot. I move the mouse over the block, but the button doesn’t appear. When logged in - everything works as usual - ok.

Can anybody repeat the problem? Any solution?

[RGJ (Richard - Communiteq)]

Thank you @riking !

It indeed seems that “regular” text/javascript is executing on published pages when it’s in the header or footer of a theme component.

[hellekin]

Ha! So it seems that there’s a hacky way to make some theme components work with page publishing.

I’m looking into adding some header/footer to the published pages, and theme components seem to be the way to go. But it seems bad to go on and implement something that would potentially break in the near future.

@riking, it looks like the text/javacript type in header or footer working on published pages was unintented. Is it going to be fixed or used to extend published pages?

@syl, author of DiscPage, mentioned the possibility to re-implement the DiscPage plugin using Page Publishing functionality. Do you still have this in mind, @syl? What do you think would be the path of least resistance to integrate both functionality @riking?

[syl]

@hellekin

@syl, author of DiscPage, mentioned the possibility to re-implement the DiscPage plugin using Page Publishing functionality. Do you still have this in mind, @syl?

Unfortunately, the “Page Publishing” feature doesn’t meet my needs. For me to use it, I would need published pages:

1. to be displayed within the normal Discourse layout, i.e. with the standard Discourse header (just like the Terms of Service and the Privacy Policy), and
2. to be rendered like normal (decorated) topics, i.e. supporting bbcode and plugins.

[hellekin]

In the meantime I used the default Discourse customization facility:

1. Identify the added element, e.g., with a published-page-footer-links CSS class.
2. Customize CSS to hide this element by default and show it only for published pages
3. Add the element in the Footer space

2. In CSS, add:

/* Only show footer links on published pages */
.published-page-footer-links { display: none; }
.published-page .published-page-footer-links { display: block;}

3. in Footer, add:

<nav class="published-page-footer-links">
Hi there! This is the footer for published pages!
</nav>