[Request] Author field

[milkyjoe90]

First I wanted to say this is a wonderfully creative and awesome use of Cloudflare's tech, well done!

Now on to the feature request - would it be possible to add a field to the item which either takes the user's details from Cloudflare Access, or, as a stretch request, have an Author schema which can be tied to an item, and in the schema give the ability to upload an avatar/profile pic for the author so that the metadata of the post can be enriched?

Once again, thank you very much!

[kenara]

Hey @milkyjoe90, it looks to me like a default Microfeed channel assumes the author of all items to be the logged in user who uploads the items. As @wenbinf describes it, "microfeed makes it easy for individuals to self-host their own feed".
So the author details you ask about would be the Channel settings. For now at least, it's geared to podcasts with the Podcast-specific fields providing the relevant metadata.

It would indeed be nice if each content type, for example images, could provide some of the properties here but as it is, Microfeed fulfills the promise of a lightweight CMS.

Myself, I'll be using the Microfeed API as a gateway to R2 for multiple users, with metadata stored in my own db.

[milkyjoe90]

Hey @kenara interesting take, from what I can see author isn't recorded anywhere with the possible exception of the Publisher setting in the Channel settings. I don't see any author from the logged in user information recorded in D1 against any of the items, so I think that the logged in user is purely being used to authenticate against the back end, rather than being used for any meta data.

I guess if I know enough Javascript I could do it myself, I'm just not quite there yet!! 😄

[kenara]

Right, the author info isn't associated with each item, just with the channel itself. It's assumed that the Channel operator is the author, which is the stated purpose of the software. If you open the little right-arrow thingy on the Edit Channel page, you'll see { "authors": [{"name": "Publisher Here"}] }

In my case there are content types that will probably never be supported and @wenbinf has explained somewhere that a multi-user environment such as I need is not on the roadmap. So I'll use the API as part of my own system. The project looks good and I'll let the author and contributors keep improving it. And I don't know React so there's that..