Closed PsychoData closed 1 week ago
Hey - just found another one! Outlook Dev Center - OAuth Sandbox
and this site that would also fit the Dev portal JWT/MS Token Decoder - jwt.ms Microsoft Graph Toolkit
While I listed this in my other feature request, there is also https://status.dev.azure.com/ (for status purpose)
I say we add the ones we have, and if it becomes too much, Dev Portals get their own page - then hopefully more Devs submit more portals :)
and Playgrounds! I LOVE the playgrounds for testing out cards and such
OK I think we might juuust have enough room for a Developer button :)
Overall, I kind of think we're getting to a level where there are several overlapping cross-sections
For Example, Visual Studio portals and Designer tools don't show up when you search "Dev" but show under the Developer Portals section. And then Azure DevOps Status, Azure Lighthouse, and Customer Digital Experiences are under "Other" portals right now - but could definitely be useful for non-devs. Same for a lot of the sandbox/playground/designer tools
"Developer Portals" section on the default page - this
But if you Search for "dev" on the same page - this
I get your point, a lot of these admin portals are hard to categorise in a single area, and what about DevOps :P . I guess the favorites option helps people pick the ones they want to see for a condensed view. Doubling up entries across different pages to address it seems like a bad idea, which now I think of all that, was probably why I left the developer stuff under the standard admin portals section :)
This would likely get fixed as part of #91
The developer stuff - updated Some of these fit Admin or User and ALSO Dev, but I think at least all of these would make sense on a Dev page/category if we made one
Nice work - I think we just have to put them where they best fit, and I'd hope most people just use the filter anyway so the sections arent overly useful, just makes it a bit cleaner overall
Yeah, part of it for me is that I don't think a lot of Devs would have access to many admin portals.
For example Power platform - they would have maybe the end user portal, a solution, and maybe independent software vendors - but I think most would not have the Power Platform Admin portal to manage all of the solutions across the whole environment
I think one day have the "one page" approach and a "dev" tag might be useful - but that would take some rewriting
On Fri, Dec 10, 2021, 9:02 PM Adam Fowler @.***> wrote:
Nice work - I think we just have to put them where they best fit, and I'd hope most people just use the filter anyway so the sections arent overly useful, just makes it a bit cleaner overall
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/adamfowlerit/msportals.io/issues/69#issuecomment-991410516, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4L7THIWT5U7ZK5SV5JMLLUQKWLLANCNFSM4VBHKASA .
I suspect trying to define what a developer uses and doesn't use is going to have too much grey area, so I'm going to close this one
Just had a couple issues created for more developer-oriented endpoints/portals.
https://github.com/adamfowlerit/msportals.xyz/issues/66 Adaptive Cards https://github.com/adamfowlerit/msportals.xyz/issues/67 Actionable Messages Developer Dashboard
These do seem useful and it would be nice to get them added, however I worry we're going to start accumulating Dev portals very quickly if we go down this route.
So far we have these that strike me as developer/development-related
but there are also several that are mixed-purpose like Graph explorer - or the Adaptive cards portal above - I use it as an IT Admin.
The whole category or "Playground" sites is kind of deep in itself in a few minutes of Googling around I found these ones I believe are new
and there are probably several more I don't know of. It might be worth making a whole "developers" page/tab