Right now it’s possible to build a public website from fibery public docs, but google will probably not show it to anyone, defeating the purpose.
The editing experience is fantastic and beats the pants off wordpress. Wouldn’t it be good to have clean urls, basic SEO, and a ‘static’ (not js-dependent) page that google would love?
The fantastic thing about fibery is that being an all-purposes tool it beats specialized tools at their own game. Clear example: editing a complex website. A bunch of docs in fibery beats the pants off of any CRM that I know, with things like versioning, auditing log, references, embedded youtube, etc
It’s not only ‘editing articles for public consumption’ (aka wordpress) where I think fibery has the upper hand. Also for notes, I think the UX in fibery beats the best-in-class tools (For me, tangentnotes.com, but for the general population, it’s obsidian)
Currently needing to restructure our website, and looking for tools that allow to pull info from Fibery. (Not easy)
The ideal would honestly be to just have Fibery as the website. Sure, it might be a bit boring in terms of layout, but it would be the easiest way for the team to make quick changes to the website. And it would have all info needed! It’s got a built in CMS (fibery databases), with one of the best relation views out there. (List of articles in a certain category for example).
It could really be not a nice website… But the lack of SEO and no custom domain makes it not ideal to work with…
Concrete request:
Set the entity title to a h1 tag, then the “H1” in RTF’s to really be an H2 tag.
Allowing user to set meta fields and title. Usually the title of the entity won’t be the optimized html title. Allowing a formula field to create the titles would be lovely. Name + " | Org Name | Location" For example. I think a “Metadata” field makes most sense.
Sitemap.xml
Nicer URLs (not sure how and I think this might be unrealistic…)
I’m aware this is probably very far from the current theme or direction but it would be quite nice eventually.
