Skip to content

Planning: Organizing docs for dark-next #380

@StachuDotNet

Description

@StachuDotNet

This repo, and the resultant docs site, is focused on dark-classic.
We need to make the division between the doc sections a bit more clear, and plan out what docs we want for -next.

Here are some semi-organized thoughts towards such:

  • how-to docs
  • discussion docs
    • how to write functional programs in darklang
      • immutability, how to model, options/results/howtodo error checking, how to do loopps
    • error handling
    • what typename to use is different places (enum match pattern, )
    • how dark is different from ... + cheatsheet (syntax and semantics)
      • js, ts, python rust
      • elm, ocaml, f#, haskell (less important)
    • how to do json stuff
    • how to do db stuff
  • reference docs
    • language
    • for each tool
    • changelog/release notes
    • library docs (e.g. docs.rs)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions