----- Original Message ----- > From: "Ankur Sinha" <sanjay.ankur@xxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Cc: "For participants of the Documentation Project" <docs@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Friday, January 15, 2021 2:03:46 PM > Subject: Re: Migrating the Fedora Developer Portal to Fedora Docs > > On Fri, Jan 15, 2021 07:37:23 -0500, Pavel Valena wrote: > > > > Hello, > > Hi Pavel, > > Thanks for chiming in. > > > I'm afraid I'm the only one left who's currently active. > > > > <snip> > > > > Let me repost what I said in the issue: > > > > If it's up to me (as there're no notes from the other/previous > > maintainers), feel free to migrate the content. > > > > I'd be hower sad to see the current functionality to go away, mainly: > > > > - mentions of individual page's authors > > How important is this and what function does this serve? Is the idea > that the listed authors serve as points of contacts---they're in-charge > of the information on the page? Well, the main idea is that author's name is enouraging more people to help with updates / editing. Having a POC is nice as well, but I'm not sure whether this option was ever used. Nor am I sure lot of people noticed, so this is not a hard requirement. > > I don't think this is currently a requirement of the docs, but depending > on how important this is, we could look into whether the Antora system > allows this. Of course, one can go to the git history of the page etc. > to see who edited the page and so on. You're right, git provides this, that's where we generate it from. > > > - edit button on the page, leading to directly editing the page > > The docs have this. If you click the "Edit this page" link in the top > right corner, it takes you straight to the source of the page in the > respective Pagure repository. > > > - web editor > ^ > Pagure has a web-editor too. When you click "Edit this page", you'll see > multiple options "Fork and edit" (or "Edit in your fork" if you already > have the fork) will take you to the web-editor on Pagure. Well, that's all great then. > > > - no git knowledge needed to submit changes > > Could you clarify on this? One has to fork and open a PR to contribute > to the devportal too, right? Yes, you're right, but I think the process for github is intuitive, and the contributor does not work with commandline (was my main point). Pagure needs require FAS though, right? What are the ACLs? Can anyone open a PR? The process seems a bit more complicated, and I'm not sure how many people already have github account, compared to FAS (does any of them support oauth from 3rd party? I'm unsure). > > > Unfortunately, I don't have any spare cycles to do anything like that > > (I don't have much for the maintenance either). > > I think that's another reason to merge it with docs, which will be > managed by the community, both infrastructure and content wise. Agreed. Well, if it migrates well :), anyway. IMO the UX seems a lot friendlier with Developer Portal, with several overviews, and it's also more granular (more sub-pages). Is there such feature (or a limit) in quick-docs? Also, there's no search (which limits the usability for me at least). I don't want to end up with few monolithic pages noone reads. (And it's aimed at developers, so english is almost natural I expect.) We could duplicate the content, however (for a while) and see how it compares, if you insist. Some automated translation (mirroring) would be a win-win IMO. Though I'm unsure it can be done. Regards, Pavel > > -- > Thanks, > Regards, > Ankur Sinha "FranciscoD" (He / Him / His) | > https://fedoraproject.org/wiki/User:Ankursinha > Time zone: Europe/London _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx
