Pubblicazione Pagina

[Discourse]

Questa guida illustra come utilizzare la funzione di pubblicazione delle pagine su Discourse. Questa funzione consente agli utenti Staff di convertire un argomento in una pagina statica autonoma con stile personalizzato. Esempi includono le pagine Termini di servizio e Informativa sulla privacy.

Livello utente richiesto: Staff

Pubblicazione di pagine statiche su Discourse

La pubblicazione di pagine consente agli utenti Staff di creare pagine statiche autonome a partire da argomenti. Questo è simile al processo per la creazione di pagine Termini di servizio o Informativa sulla privacy.

Sommario

Questa documentazione coprirà:

• Abilitare la pubblicazione delle pagine
• Pubblicare un argomento come pagina
• Depubblicare un argomento
• Problemi comuni e soluzioni
• FAQ
• Risorse aggiuntive

Abilitare la pubblicazione delle pagine

1. Navigare su Admin > Settings.
2. Attivare l’impostazione enable page publishing.
   

Abilitare la pubblicazione delle pagine quando l’accesso è richiesto

Per consentire la visualizzazione delle pagine pubblicate anche quando un utente non ha effettuato l’accesso:

1. Attivare l’impostazione show_published_pages_login_required su Admin > Settings.
   

Pubblicare un argomento

1. Andare al primo post di un argomento pubblico e selezionare l’icona dei puntini di sospensione (...).
   

2. Selezionare l’icona della chiave inglese.
   

3. Scegliere l’opzione “Page Publishing” (Pubblicazione pagina).
   

   

4. Apparirà una finestra di dialogo modale, che consente di confermare lo slug (che può essere precompilato dal titolo del post) e di visualizzare in anteprima l’URL della pagina pubblicata.
   

   

Per consentire la pubblicazione delle pagine, è necessario disattivare le impostazioni del sito relative agli upload sicuri.

Per i siti ospitati, gli upload sicuri sono limitati al piano Enterprise. (secure uploads are limited to the Enterprise plan.)

Argomento pubblicato

• Se l’opzione Public (Pubblico) è spuntata, apparirà un’etichetta public.
  
  

  

• Un argomento pubblicato mostrerà una notifica sotto il titolo che consente l’accesso alle sue impostazioni di pubblicazione.
  

  

Pagina pubblicata

Depubblicare un argomento

1. Selezionare Publishing Settings (Impostazioni di pubblicazione) sotto la notifica.
   

   

2. Cliccare su Unpublish (Depubblica)
   

   

3. La pagina è stata depubblicata.
   

   

Problemi comuni e soluzioni

Impossibile visualizzare le pagine pubblicate quando non si è connessi

Assicurarsi che l’impostazione show_published_pages_login_required sia attiva su Admin > Settings.

Aggiungere un’intestazione di Discourse alle pagine pubblicate

Attualmente, le pagine statiche sono pensate per essere minimali e non includono l’intestazione e il piè di pagina tipici di Discourse.

FAQ

Posso rendere pubblica una pagina FAQ o Informazioni?

È possibile creare un nuovo argomento con il contenuto desiderato e pubblicarlo come pagina. Modificare i link nelle impostazioni del sito per puntare a queste nuove pagine.

Come posso personalizzare l’aspetto di una pagina pubblicata?

Utilizzare la struttura del documento HTML e i corrispondenti selettori CSS per applicare stili personalizzati in Admin > Customize > Themes > CSS.

Risorse aggiuntive

• 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>