7️⃣/2️⃣3️⃣

• Noticed that you added "/", but not sure that it makes sense :)
• Added space between the header titles and the thin line in the header
• Noticed that you kept the thin line, which now it makes sense to have it to separate with bread crumbs. (keep)

7️⃣/2️⃣4️⃣

• Can we remove the "/"?
• Can we change the font for "Developers" to "Courier New" in bold? to give a bit dev feel.

7️⃣/2️⃣9️⃣

• update the title from "Documentation" to "Reference"

7️⃣/2️⃣3️⃣

• It looks to me a little busy there.. i suggest that we remove the social media icons as they don’t apply directly to “developer portal” anyway.

7️⃣/2️⃣4️⃣

• Can we work on the spacing of the items? Why is the font size of privacy and t&c so much smaller?

7️⃣/2️⃣5️⃣

• like the spacing and visually separate the contents!

7️⃣/2️⃣3️⃣

• I am still working on creating the content for it...

7️⃣/2️⃣3️⃣

• looks good, only in bread crumbs, API or APIs?

7️⃣/2️⃣3️⃣

• in bread crumbs, API or APIs?
• missing “news/latest updates” section
• but i like “create an account and get started” at the bottom of the page
• need more discussion..

7️⃣/2️⃣4️⃣

• recommend a different style for "news/latest updates" section, see elasticsearch breaking changes and release note

7️⃣/2️⃣5️⃣

• like the style for "Latest updates". Are you planning to add more content to this section? If not, can we make the box shorter?

"Add to my app", let's leave the button there for now but only if the user is logged in.

7️⃣/2️⃣6️⃣

• is there a way to make "View Documentation" closer to the content? It appears to be on the side and can be missed..

7️⃣/2️⃣9️⃣

• "API Documentation" in a box works for now. However can we call it "Developer Reference" and replace in all places where we refer to "Documentation"?

7️⃣/2️⃣3️⃣

• search within documentation page, do we need another search?
• Messaging overview will not have "Download OpenAPI specification" link as it will be in each individual API documentation page

7️⃣/2️⃣5️⃣

• left panel navigation sections look good
• Can we add vertical scroll bar for left panel navigation

the ideal is to make documentation 1 single page (for the right section). Left panel navigation would be sectioned and have a vertical scroll bar. I don't quiet understand your question here.. let's talk about this over the call?

7️⃣/2️⃣6️⃣

• looks good for the Tracker API v3 Overview + Change Log page, where it's not one single page from top to bottom. I don't think we have to make it one page, what's the real benefit of doing that actually?

7️⃣/2️⃣9️⃣

• on the left navigation menu, can you add "Versions" below "Authentication"?
• on the left navigation menu, when "Sandbox" is clicked on, it is changed to "Messaging API"
• on the left navigation menu, change "Messaging API" to "Messaging", "Compliance API" to "Compliance"
• on the left navigation menu, change "SWIFT Sandbox" to "Overview", it will have a small paragraph there. So under "Sandbox", there will be "Overview" and "Getting started"
• on the left navigation menu, change "gpi for Corporates" to "Tracker g4c API"
• can we make the header static (not disappearing) when we scroll down?
• on the left navigation menu, "Documentation" is really needed? Or replace it with the bread crumbs? I think it's better to show only one of the two.
• update the title from "Documentation" to "Reference"

7️⃣/2️⃣3️⃣

• looks good!

7️⃣/2️⃣3️⃣

• I am still working on creating the content for it...

7️⃣/2️⃣3️⃣

• looks good
• can we remove links in the header?

7️⃣/2️⃣4️⃣

• i think it looks cleaner to leave out "Get quick access to your..."
• can you create wireframe for "forget my password" page?

7️⃣/2️⃣9️⃣

• can we update the "Sign in" button link on the landing page to point to the right Sign in page? I believe it's pointing to swift.com login at the moment.

7️⃣/2️⃣5️⃣

• looks good for success which redirects to Sign in page, and error when email not found

7️⃣/2️⃣3️⃣

• Can we move "Are you a swift.com user?"" to the top of the box right below "Create account"?

7️⃣/2️⃣4️⃣

• looks good

7️⃣/2️⃣5️⃣

• i like the field check for "gmail" etc, can we also check for "swift.com"? and prompt them to directly sign in?

7️⃣/2️⃣3️⃣

• "Sandbox", "Live" status icon looks good to me

7️⃣/2️⃣3️⃣

• "Redirect URIs" looks good to me

7️⃣/2️⃣4️⃣

• Can you provide the look and feel for when one URI is added?

7️⃣/2️⃣5️⃣

multiple URI looking good!

7️⃣/2️⃣3️⃣

• Ready to go live? (i like this), but instead of "Register your app at swift.com", it's better to say "Contact your account manager" (need to think on that)
• Can you also provide the look and feel when the app is in "Live" status?

7️⃣/2️⃣5️⃣

• Can you provide multiple URIs in the app info section?

7️⃣/2️⃣3️⃣

• If you have time, could you update the color where it's "burn orange" now to "Rose pink (#970254)" and "Tarragon Green (#B5A300)"?

7️⃣/2️⃣4️⃣

• Can you put these swap the "burn orange" with these two colors for the "Support" page and "GPI test app" page?

7️⃣/2️⃣9️⃣

• if time permits, can you update the Sign in page with the two colors?
• if time permits, can you update the "Contact Us" button color to match with the "rose pink" and "terragon green"? i suppose use a lighter version of these two color?

7️⃣/2️⃣4️⃣

• Can you provide the look and feel of a simple page for this page?

7️⃣/2️⃣5️⃣

looks good to me in term of the layout of the page. The content on this "getting started guide" will slip between "Sandbox" section (where we explain the URL and how to get access to sandbox) and "Overview" section (where postman collection goes here) on the documentation page. This is more of a note for myself, I don't see any additional design work needed here.

7️⃣/2️⃣6️⃣

• like the sandbox section including the sandbox URL and getting started section. let's keep it in that structure.

7️⃣/2️⃣5️⃣

• Let's first rename "Release versioning" or "Release notes" to "New features and bug fixes" since the content will go on each version of the API.

💥💥 It makes me wonder how can we make all the information in one page but having a "version" dropdown on the tracker documentation page?

7️⃣/2️⃣6️⃣

• change log section looks very good inside each API reference overview section

7️⃣/2️⃣5️⃣

• still in evaluation :)

7️⃣/2️⃣6️⃣

• I want to propose some small changes, let's talk on the call, much easier that way :)