anthonyshew / maestros Goto Github PK

I'd love to be able to come up with a reading list or list of prerequisites for each technology for each page in the reference.

Will probably draw this out with Excalidraw first to see what it would take and then move on from there.

Add an .env.example file with all required environment variables to generate builds.

To improve DX for copying and pasting cli snippets, it might be useful to add tabs for different package managers.

https://orm.drizzle.team/docs/quick-start

Both as an example and to keep this repo fresh!

I had a moment where it appeared to be not doing it's job correctly. Let's check in that.

The favicon from my portfolio is being shown. Am I able to use a different one for Maestros?

If so, will need to come up with a logo or design.

Would love some help with this one because I really haven't used GraphQL beyond a Hello, World!

I recently moved to distributing args to their respective workspace scripts. I need to update my guidance.

This doesn't have to be deployed and can be for demonstration's purpose.

I already have a script for it at pn spellcheck; just need to get it automated!

We're sticking with pnpm in this repo today for dogfooding purposes.

Once there is a "package manager switcher" in Maestros, we could dogfood Bun!

ui.shadcn.com, you know the drill.

I suppose we should be dogfooding, although it may be overkill for this repo specifically.

I'll probably split my portfolio and Maestros into two apps strictly for demo purposes.

He's the best so mind as well ask. :)

I'd love to be able to pop a modal for any key term within the reference.

The key term would have a dotted underline and, on click, you'd get a quick modal showing the term.

The absolute best way to do this would be with intercepted routes. That way, the modal would be a window to the Glossary page and I'd be ensuring consistency on the definitions. I don't know how feasible this is, though, so it will take some exploring.

Going to be essentially the same exact thing as this! It will involved parsing the Markdown, looking for lines that start with #, ##, ###, etc. and then rendering the links to those.

• Tools
• General
• Services
• Feature requests

This is perfect for what we need. Definitely worth trying out.

https://codehike.org/docs/installation/contentlayer

Would it be worth adding some subsections for tools, so that there is a top level which outlines the why to use this, and then different subpages for the relative implementation.

E.g.

• Tooling
  • ORM's
    • DrizzleORM,
    • Prisma,
    • etc

(Also a minor point on this, we should probably just alphabetise the lists so that it's not showing a particular preference? Depends how opinionated you want to be.)

I will work on filling on the section about projects for MonoRepo implementations.
Projects flag helps with:

• Enforcing Monorepo standards and best practices
• Forcing the project to explicitly define files to compile
• Improves performance which in growing Monorepos is critical

This doesn't have to be deployed and can be for demonstration's purpose.

I was using Turboviz through npm. But it seems like it makes way more sense to let folks add it to their repo using turbo gen.

Investigate.

https://www.npmjs.com/package/@ashew/turboviz

First of all big fan of what are you doing with "Monorepo Maestros"!

I've read your TypeScript docs and wondering if we need to have a baseUrl in the tsconfig.json file that references @repo/tsconfig?

Meaning:

// packages/logger/tsconfig.json file
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "@repo/tsconfig/base.json", // Using our base config!
  "compilerOptions": {
    "tsBuildInfoFile": "node_modules/.cache/tsbuildinfo.json",
    "baseUrl": ".",
  },
  "include": ["."],
  "exclude": ["node_modules"]
}

If we don't need it, in which scenarios do we need it in monorepo? In conjunction with paths maybe?

From #29 (comment)

We'll never know where to add your scripts. Maybe the answer was "in our hearts" all along.

https://www.npmjs.com/package/@vercel/toolbar