이 가이드는 Discourse에서 페이지 게시(Page Publishing) 기능을 사용하는 방법에 대해 다룹니다. 이 기능을 사용하면 스태프(Staff) 사용자는 토ピック을 사용자 정의 스타일링이 적용된 독립형 정적 페이지로 변환할 수 있습니다. 예를 들어 서비스 약관 및 개인정보 처리방침 페이지 등이 있습니다.
필요한 사용자 권한: 스태프(Staff)
Discourse에서 정적 페이지 게시하기
페이지 게시(Page Publishing) 기능은 스태프(Staff) 사용자가 토ピック에서 독립형 정적 페이지를 생성할 수 있도록 합니다. 이는 서비스 약관이나 개인정보 처리방침 페이지를 생성하는 과정과 유사합니다.
요약
이 문서에서는 다음 내용을 다룹니다:
페이지 게시 활성화
토ピック을 페이지로 게시하기
토ピック 게시 해제
일반적인 문제 및 해결 방법
자주 묻는 질문(FAQ)
추가 자료
페이지 게시 활성화
Admin > Settings로 이동합니다.
enable page publishing 설정을 활성화합니다.
로그인 필요 시 페이지 게시 활성화
사용자가 로그인하지 않은 상태에서도 게시된 페이지가 표시되도록 하려면:
Admin > Settings에서 show_published_pages_login_required 설정을 활성화합니다.
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.)
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.
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.
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?
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.
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?
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-links CSS class.
Customize CSS to hide this element by default and show it only for published pages
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>
이 가이드는 Discourse에서 페이지 게시(Page Publishing) 기능을 사용하는 방법에 대해 다룹니다. 이 기능을 사용하면 스태프(Staff) 사용자는 토ピック을 사용자 정의 스타일링이 적용된 독립형 정적 페이지로 변환할 수 있습니다. 예를 들어 서비스 약관 및 개인정보 처리방침 페이지 등이 있습니다.
필요한 사용자 권한: 스태프(Staff)
페이지 게시를 허용하려면 secure upload 사이트 설정을 비활성화해야 합니다.
호스팅 사이트의 경우 secure uploads는 Enterprise 플랜에서만 사용할 수 있습니다.
