acid-info / logos-documentation-website-template Goto Github PK

• UI component
• automatic fetch
• Include the configs in docu configs file?

• Usecase - how a person from our team can develop and work on Theme and components
• Usecase - how a person from our team can develop and work on framework itself
• Usecase - how a person from another team can work on their content locally

Considerations

• Embedded React blocks need to be addressed properly in documentation

What happens with a variation of customization per project level? For example, some needs sandbox and some do not! I proposed to put this on hold and for now just develop one monolithic repo

should be keep the language menu? if yes we need to use shorter name version, for example English becomes En

• font families
• sizing and spacing
• type specimen - h1, h2, ...