このガイドでは、Discourse のページ発行機能の使用方法について説明します。この機能により、スタッフユーザーはトピックをカスタムスタイリングが施されたスタンドアロンの静的ページに変換できます。利用規約やプライバシーポリシーのページなどがこれにあたります。
必要なユーザーレベル: スタッフ
Discourse での静的ページの公開
ページ発行機能により、スタッフユーザーはトピックからスタンドアロンの静的ページを作成できます。これは、利用規約やプライバシーポリシーのページを作成するプロセスと似ています。
概要
このドキュメントでは、以下について説明します。
- ページ発行の有効化
- トピックをページとして発行する
- トピックの発行を解除する
- 一般的な問題と解決策
- よくある質問 (FAQ)
- その他のリソース
ページ発行の有効化
管理>設定に移動します。ページ発行を有効にする設定を有効にします。
ログインが必要な場合にページ発行を有効にする
ユーザーがログインしていない場合でも公開されたページを表示できるようにするには:
管理>設定でshow_published_pages_login_required設定を有効にします。
トピックの発行
公開トピックの最初の投稿に移動し、省略記号アイコン (
...) を選択します。
レンチアイコンを選択します。
「ページ発行 (Page Publishing)」オプションを選択します。
モーダルダイアログが表示され、スラッグ（投稿タイトルから事前入力可能）を確認し、発行されたページの URL をプレビューできます。
ページ発行を許可するには、セキュアアップロード (secure upload) サイト設定を無効にする必要があります。
⋌small>:information_source: ホストされているサイトの場合、セキュアアップロードはエンタープライズプランに制限されています。
公開されたトピック
公開 (Public)オプションがチェックされている場合、public ラベルが表示されます。
公開されたトピックには、その発行設定へのアクセスを許可する通知がタイトルの下に表示されます。
公開されたページ
トピックの発行を解除する
通知の下にある
発行設定 (Publishing Settings)を選択します。
発行解除 (Unpublish) をクリックします
ページが発行解除されます。
一般的な問題と解決策
ログアウト時に公開されたページが表示されない
管理>設定でshow_published_pages_login_required設定が有効になっていることを確認してください。公開されたページに Discourse のヘッダーを追加する
現在、静的ページは最小限にすることを意図しており、標準の Discourse のヘッダーとフッターは含まれていません。
よくある質問 (FAQ)
FAQ ページや「概要」ページを公開できますか?
必要なコンテンツで新しいトピックを作成し、それをページとして発行できます。サイト設定内のリンクをこれらの新しいページに向けるように変更してください。
公開されたページの見た目をカスタマイズするにはどうすればよいですか?
HTML ドキュメントの構造と対応する CSS セレクターを使用して、
管理>カスタマイズ>テーマ>CSSの下でカスタムスタイルを適用します。その他のリソース
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!
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:
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.
Something that would go nice with this feature is to make publications onebox-compatible such that people could easily share the content.
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!
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.
GTM not loaded on published pages? Would be nice.
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?
Yes I think we already support having a text/javascript in the theme fields, so there are certainly solutions in this area.
That would be great.
So it’s currently impossible to have responsive published pages, and this site particularly wants
- images made available when sharing to public media, and
- responsive/resizing images displayed, especially on mobile–oh, mobile could just resize the image with CSS–that should work, right?
+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…
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!
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 ?
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…
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?
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.
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?
Unfortunately, the “Page Publishing” feature doesn’t meet my needs. For me to use it, I would need published pages:
- 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
- to be rendered like normal (decorated) topics, i.e. supporting bbcode and plugins.
In the meantime I used the default Discourse customization facility:
- Identify the added element, e.g., with a
published-page-footer-linksCSS class. - Customize CSS to hide this element by default and show it only for published pages
- Add the element in the
Footerspace
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>