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
bespoke home pages for our various documentation projects are made out of similar building blocks.
In the future, we would build a list of standard components which could be used to build custom pages without having to recreate them from scratch. Concretely, the only surface that we really want to customize is the home page, though we could create different surfaces as well.
If we have a gallery of standard components in Ocular gatsby, it's easy for a React developer to compose a custom page by importing them (as if they were in the local tree) and building the page from there. We could go one step further and allow the home page to be entirely customizable without having to code. As long as the home page is made out of known, standard components, it can be described in a configuration file (ie yaml, json). ie:
We can then write the code to generate the page from that configuration information. That configuration file could be standalone or exist within ocular-config.js.
The text was updated successfully, but these errors were encountered:
bespoke home pages for our various documentation projects are made out of similar building blocks.
In the future, we would build a list of standard components which could be used to build custom pages without having to recreate them from scratch. Concretely, the only surface that we really want to customize is the home page, though we could create different surfaces as well.
If we have a gallery of standard components in Ocular gatsby, it's easy for a React developer to compose a custom page by importing them (as if they were in the local tree) and building the page from there. We could go one step further and allow the home page to be entirely customizable without having to code. As long as the home page is made out of known, standard components, it can be described in a configuration file (ie yaml, json). ie:
We can then write the code to generate the page from that configuration information. That configuration file could be standalone or exist within ocular-config.js.
The text was updated successfully, but these errors were encountered: