Today I can announce some big changes that we are ...
# suitecommerce
s
Today I can announce some big changes that we are going to be making to the developer portal https://developers.suitecommerce.com/announcement-changes-to-how-netsuite-serves-suitecommerce-developer-resources
❤️ 3
👍 6
k
Hi @Steve Goldberg, I reviewed the article about the changes to the developer portal. I have one concern about the audit that might result in the older blog posts becoming unavailable. My concern is that the old blog posts are still relevant when we’re working on or supporting old versions of SCA. It’s not uncommon for us to perform smaller enhancements on old versions or need to understand how the older versions worked. Would it be possible for NetSuite to port the old content, but place it under an archive type heading so it’s clear that the content may be out of date?
s
Good point and one I am already aware of. When I talk about retiring old content, that usually means killing URLs; but if there is content in those pages that is still useful (even to old versions) then they will migrated, but to new URLs
For example, I know that people still use the getting started tutorial I wrote for Denali, nearly five years ago
I will be keeping that, but organising it into a better context so that it is clear that it is for an old version
To give another example, I recently migrated the content for third-party libraries. Best practice is to use a commerce extension, but I know that's not available to a lot of sites. So, the new page contains information on what to do for all versions. The point is that we no longer have two different pages, that talk about what to do for the version that was new at the time the posts were written.
k
Perfect. You are a life saver. 🙂 It would be impossible to develop SCA without the SuiteCommerce Developer portal.
💯 1
s
I appreciate the kind words. I hope the new portal continues to meet the community's high expectations 🙂