Section for Standard Config

[ZakAyesh]

Brief Description of the Docs Request

We should have a section describing the standard configuration.

Description of the Documentation You'd Like

I see this as a section to add under the "OP Stack" section which explains what standard configuration is. We can then explain that OP-Deployer does a lot of the work to ensure you are deploying a standard config-compliant chain. We should also link out to the superchain registry.

Links to Related Pages

https://specs.optimism.io/protocol/configurability.html
https://github.com/ethereum-optimism/superchain-registry

Additional Context

In dev support we get many questions asking what is and isn't standard configuration. i.e. we had a partner asking if custom gas token is currently considered standard config (it isn't).

[sbvegan]

Good call out! Here's a PR that will address this issue: #1125

[krofax]

@sbvegan This PR doesn't seem to align with the standard configuration @ZakAyesh mentioned. Would you like me to create a new PR?

If it meets expectation then we can close this issue?

[sbvegan]

Description

To address this issue, lets add a sub section to the blockspace charter/standard charter section of our documentation to address devsup's recurring question about standardization.

User story

• A chain governor should be able to understand what defines a standard chain (on a technical and governance level)

Resources

• Standard Rollup Configuration Page
• Zak and other developer support engineers who have gotten this question
• Tess is the product manager on the superchain registry and knows a lot about standarization

Acceptance Criteria

• A new section that describes what a standard chain is and links out to the specs to explicity defines the technical stuff
• Information about the op-deployer and how it helps with standardization
• Why standardization is important
• Context on what is and what is not standard

Action items

1. Reach out to Zak and devsup if you need more context
2. Open a PR to add context that addresses the acceptance criteria
3. Get review from zak and tess
4. peer review merge
5. If needed, open a new issue for next sprint about opening a PR to the specs site to organize the standard config info.

[krofax]

@ZakAyesh @tessr @sbvegan Ready for review.