You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As teams implement these standards on specific technology stacks, they can contribute back to the rest of the organization by demonstrating what type of coding or configuration was necessary. They could document these in "implementation profiles" or "implementation playbooks".
For example, how do you "Enable CORS" with node.js/express? How do you put the version in the path for JAX-RS?
I am currently doing this for a technology stack in IC and it is a similar process to what we did previously on the Prototype City Pairs API standards page.
The text was updated successfully, but these errors were encountered:
Would be good to create a blank template for this that teams could clone and add to the repo for each technology.
Sample template might be something like:
Standards Item
Implementation tips
Notes or limitations
Enable CORS
Some setting here
Some note about it
After going through this exercise a couple of times, It occurs to me that some numerical structure on the standards might make this easier. For instance, if we update the standards with 1.A.I, or something like that.
As teams implement these standards on specific technology stacks, they can contribute back to the rest of the organization by demonstrating what type of coding or configuration was necessary. They could document these in "implementation profiles" or "implementation playbooks".
For example, how do you "Enable CORS" with node.js/express? How do you put the version in the path for JAX-RS?
I am currently doing this for a technology stack in IC and it is a similar process to what we did previously on the Prototype City Pairs API standards page.
The text was updated successfully, but these errors were encountered: