Hi henrique,
Good news: your page setup is almost right. The three pages are generated, so the hard part works. The problem is only in the expressions that read the fields
The problem is where the expressions start: The node (posts{}) you picked is a different field that happens to have the same name. That is why your title and excerpt come out blank. Your Permalink uses that same field, so it has the same problem
On a collection page, Silex gives you the items of the current page as a value called Pagination items. In the expression menu you will find it in the group Website's states, at the top of the list. Every expression on this page has to start there.
Here is what to change, on the Blog-Post page only.
Select the title text. In HTML content, remove the current expression, then build this one step by step: Pagination items, then first, then node, then title.
first is a filter. Pagination items is a list, and with Size 1 it holds only the current post, so first takes it.
Same for the excerpt: Pagination items → first → node → excerpt.
In the page settings, CMS tab, fix the Permalink the same way, and add the folder and the file name around it:
Pagination items → first → node → slug → prepend "/blog/" → append "/index.html".
The file name at the end is needed, Silex refuses a permalink that ends without one.
Preview, then publish.
One thing that is on us: the Collection pages page in the docs uses post → title in its examples and says the exact name depends on your setup. That name does not exist in the editor, so it could only send you the wrong way. Those docs are still being written, and I am reporting this so the page gets fixed.
Something else worth knowing: this extra node field is only in your list because your source is set to the Generic GraphQL type, which was the workaround Alex gave you. Once his fix is in canary and you set the source back to Supabase, that field disappears from the list.
About Adobe Fonts: the Fonts dialog only handles Google Fonts, so you cannot install an Adobe font there. You can add one through the site head code.
- Click the gear icon in the top bar to open the site settings, then the Code tab. Careful not to use the Code tab of the page settings, that one would only apply to a single page.
- Paste your Adobe web project embed code, plus a style block that applies the font - I added a
.fonts css class, so that you can add it to the body or to any element you want to use this font:
<link rel="stylesheet" href="https://use.typekit.net/xxxxxxx.css">
<style>
h1, h2, .fonts { font-family: "your-adobe-font-name", sans-serif; }
</style>
- Click Apply. This code goes in the head of every published page, and Silex also puts it in the editor canvas, so you see the font right away.
Two things to keep in mind. The font will not appear in the font family list of the Style panel, that list only contains fonts installed through the Fonts dialog, so you apply it with CSS as above. If you want it on one element only, give that element a class in the Style panel (the selector field at the top), for example post-title, then target .post-title in the style block. Also check that your published domain is listed in your Adobe web project, Adobe only serves the font to domains you declare there (for silex desktop preview use localhost:6805).
Tell me how it goes, and if the publish fails, paste the log like you did the first time.
Chris
