Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve organization and content of microsite #148

Open
jdegoes opened this issue Dec 10, 2019 · 6 comments
Open

Improve organization and content of microsite #148

jdegoes opened this issue Dec 10, 2019 · 6 comments
Assignees

Comments

@jdegoes
Copy link
Member

jdegoes commented Dec 10, 2019

Some ideas can be found here in PureConfig which does a pretty good job organizing content.

Some ideas:

  • Central link on the home page should be "quick start", and it should be a short 1 page file with the bare minimum necessary to get someone started. There will be very little explanation, mostly very tiny code snippets and 1-3 sentences for each code snippet. Quick start will have:
    • How to add project to SBT / Mill / etc. build file
    • How to add optional dependency with Magnolia to SBT / Mill / etc. build file
    • How to create config descriptor (links to "creating config descriptor" section)
      • How to derive descriptor config from data type using Magnolia
      • How to create descriptor config "by hand" with added docs
    • How to specify where config information should be read from (links to "specifying config source" section)
    • How to use config descriptor (links to "using config descriptor" section)
      • How to get readers from config descriptor
      • How to get documentation from config descriptor
      • How to get report generation from config descriptor and value
      • How to get writers from config descriptor
    • How to consume config from from ZIO environment
  • Section on creating configuration descriptor
    • Subsection on creating configuration descriptor by hand
    • Subsection on creating configuration descriptor by Magnolia
  • Section on specifying config source
    • Specifying source as map
    • Specifying source as properties
    • Specifying source as environment variables
    • Specifying source as hocon file
    • Specifying source as json file
    • Specifying source as yaml file
  • Section on using configuration descriptor
    • Subsection on deriving readers for various file formats (properties, env vars, json, yaml, hocon)
    • Subsection on deriving documentation for various formats (html, markdown, plaintext)
    • Subsection on deriving report generation for various formats (html, markdown, plaintext)
    • Subsection on deriving writers for various file formats
  • Section on consuming config from ZIO environment
    • The Config module
    • Creating the config module
    • Adding the config module to the whole application environment
    • Accessing application config from anywhere in app using module helpers
  • Section on interop
    • Interop with HOCON
    • Interop with etc...
@afsalthaj afsalthaj self-assigned this Dec 10, 2019
@jdegoes
Copy link
Member Author

jdegoes commented Dec 17, 2019

@afsalthaj It could be useful to split this ticket up into subtickets, too.

@afsalthaj
Copy link
Collaborator

@jdegoes Sure, that's a good idea

@afsalthaj
Copy link
Collaborator

@jdegoes , I think we are good without splitting the tasks after giving a giving a kickstart to re-organising the website.

The commits can be seen in documentation branch
https://github.com/zio/zio-config/tree/documentation

@afsalthaj
Copy link
Collaborator

The above changes were actually made and merged

@afsalthaj
Copy link
Collaborator

Will close the issue, once we review with @jdegoes

@afsalthaj
Copy link
Collaborator

@jdegoes Could we review the website again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants