I would like to replace procourse-static-pages with “page publishing”. Is it somehow possible to add the default discourse header to “published page”? I mean, show the logo on the left side, the search, hamburger icon, avatar and the related functionality for theses buttons on the right side. Then it would be a replacement of procourse-static-pages.
Additionally, it would be great to use DiscoTOC for the published page, too.
Thanks a lot for this feature! It allows to build great landing pages apart from the homepage. So it would be nice to have the appropriate metadata that you need for sharing on social media, SEO or Google Discover (the latter apparently became more important than Google search in my country during the last months when it comes to traffic). Are there any plans to provide a meta title / description and the custom meta tags for the big social networks or even make them editable?
May I ask, Is there a url that can list all the published page for Admin ? So Admin can easily see all the page they published.
Something similar to wordpress ?
If not, It would be great if the url example.com/pub/. list all the page published.
Are there any plans to allow rendering of these published pages inside the normal Discourse Ember layout? It seems a shame that you can’t just pull them into the layout like the other app sections. I’ve seen a number of others ask this in this thread but nobody seems to have given a direct answer yet.
All of the other static pages plugins that I’ve seen in my research seem to be also rendering their static content in their own Rails layouts, too. Is this a limitation of the Discourse platform, or just that nobody has coded it in yet?
If there is no hard limitation against rendering the published pages inside the normal app layout (with header), where should I start when it comes to getting this feature moving?
Thank you @hellekin. However, this does not address the main point of my reply. I asked if it’s possible to render the published pages within the normal Ember.js app layout (with the logo, search, hamburger nav, and user nav), not how to customize the separate published pages layout.
I want the static content to render within the normal app layout the same way that a category or topic detail page would load. I would like to use of all the existing plugins and theme components that interface with the main Ember app layout.
I think the purpose of published pages is to remove the Discourse UI.
Although I agree that it would be great to have some features (e.g., from theme components or plugins), I think linking to topics would work better in your case. Maybe you want to explore styling closed topics instead?
Page publishing is really cool–the topics look great as standalone pages. But I haven’t been able to use it like I had hoped:
I thought one cool use would be to set up page publishing as a landing page for the forum–so before users login they get to see a topic I have published and styled to be the page they see. Is that possible?
Is there a preferred way to link back to the original post from the published page?
I find myself willing to do this quite often, to encourage replies from readers, while keeping control over the style of the read-only, published page. I tried several ways, including linking to the topic prominently or simply with a ‘discuss’ link.
Maybe an option to add a discuss button that would remain visible at all times (but still be modifiable with CSS) could work. Did someone implement such a CSS trick already?
You can “simulate” a button by codding CSS for a specific tag, like I did for the header of this category:
Ciudadanos con la convicción de que la República Argentina puede, debe, y va a ser un lugar mejor, si trabajamos todos Unidos en pos de la Libertad.
<mark> [**Afiliación**](https://foro.enunionylibertad.com/t/formulario-de-pre-afiliacion/92) </mark>
(the important part are the <mark> tags)
CSS for said <mark> tags:
/* Code to CHANGE "mark" tag render to something that looks like a "menu bar" */
background-color: #E1E1E1 !important;
border-radius: 20px !important;
Tags in the composer can be used to selectively apply formatting to a specific Topic Post.
For example, on my site I achieve this by pasting the following CSS into my theme’s CSS in the Common tab:
I’m also using this trick on my site extensively, to style content and embeds on-the-fly inside the composer…
I have a section of my site where I document my developments (mainly so my future self can recall and find what I have already done, so I don’t continue to reinvent my own wheels!) But anyone is welcome to visit and/or subscribe to that category if you’d like…