dylansp/purely-functional-blog

Gatsby Starter Blog with Typescript

This project attempts to make Gatsby's starter blog type-safe. In addition, styled components are used in favor of inline jsx styles.

Features (in addition to the Gatsby Starter)

• Typescript
• Styled Components
• Graphql Codegen
• Gatsby Transition Link

Roadmap

• Make onCreateNode type-safe
• Improved grapql typings generations

Currently, the type graphql type definition file has everything as nullable, so a lot of nested non-null assertions are used when accessing data from queries.

purely-functional-blog's Issues

Add tagging system

See https://www.gatsbyjs.org/docs/adding-tags-and-categories-to-blog-posts/

Adapt licensing/copyright for prose

I may want to use a more restrictive license for what I actually write. Crafting Interpreters may be a good example, where the prose is under Creative Commons Attribution-NonCommercial-NoDerivatives.

Topic: How I incorporate testing into my development

How I use and don't use TDD
Refactoring against the red bar
Use of Cypress for the frontend

Topic: How I solved the three-pass-compiler kata with Haskell

Repo: https://github.com/DylanSp/three-pass-compiler

Display time to read on each post

Add to graphQL query; see https://egghead.io/lessons/egghead-display-reading-time-for-gatsby-blog-posts-using-gatsby-transformer-remark and https://github.com/gaearon/overreacted.io/blob/master/src/templates/blog-post.js#L267 for setting up pageQuery, see https://www.gatsbyjs.com/docs/reference/graphql-data-layer/graphql-api/ and https://github.com/gaearon/overreacted.io/blob/master/src/templates/blog-post.js#L166 for usage.

Implement objects

Possibly data only? Maybe as pure syntax sugar for closures?

Add comments section

See https://www.gatsbyjs.org/docs/adding-comments/.

Add footer with link to GitHub

Add optional dark mode

See overreacted.io.

Topic: Plans for core1, alabaster, etc.

Topic: What I want and need out of a new programming language

What I want: features
What I need: nonfunctional requirements
What I don't want
What I don't care about

Series: React tutorial (tic-tac-toe)

Start with overview post containing links to each part:

Posts:

• Part 0: Game logic (no React).
  • How to design game API? Class-based vs. functional/POJO, mutable vs. immutable
  • Development
  • Testing
• Part 1: React ideas and fundamentals
  • Component-based
  • Top-down data-flow through props
  • JSX/TSX
  • Class and function components
  • Hooks
• Part 2: Static site iteration 1 - static site, passing state with prop-drilling, hooks, no Redux
  • Sketch UI (Excalidraw?)
  • Break design down into components
  • Build page structure (without attaching logic)
  • Wire in game logic, event handlers
• Part 3: Testing with Cypress, ensuring stability when refactoring
• Part 4: Static site iteration 2 - using Context to avoid prop-drilling
  • Motivation and concepts
  • Implementation
• Part 5: Static site iteration 3 - IoC, composition of components
  • Motivation and concepts
  • Implementation
• Part 6: Static site iteration 4 - Redux
  • Motivation and concepts (model-view-update)
  • When to use, when not to use
  • Implementation
• Part 7: Full-stack environment setup
  • Opaque backend - go over routes/API provided (distribute through Docker Compose, with container for backend and container for DB)
• Part 8: Full-stack site design
  • Sketch expanded UI
  • Introduce react-router
  • Scaffold out site
• Part 9: Full-stack iteration 1 - useEffect + Redux (or Context/IoC)
• Part 10: Full-stack iteration 2 - RTK query

Topic: Future of version control systems

Two avenues for major (not incremental) improvement: working with non plaintext, working with large repos
Pijul is neat, but probably not more than incremental improvement.

Topic: "style guide" for code

How I write and low-level design code.

• Syntactic stuff - use an auto-formatter i.e. prettier
• Prefer lack of mutation
• Prefer declarative code
• Variable scopes as limited as possible
  etc.

Topic: The role of controllers in MVC server-side frameworks

Write about my views of controller as mapping between HTTP and business logic, thin controllers, thin models, thick services.