I found myself constantly opening these in VS Code or converting them just to read comfortably.

So I built mdfocus: a zero-config local reader that you point at any folder and start reading instantly (npx mdfocus ~/notes).

It's not a static site generator or a publishing tool—just a clean, focused way to consume Markdown locally.

Includes live-reload, auto-generated table of contents, Mermaid diagrams, dark and other modes, and reading status tracking with color tags.

MIT licensed.

Comments URL: https://news.ycombinator.com/item?id=46411342

Points: 2

# Comments: 0

Meet Mootivator, a CLI tool to print geek jokes in cowsay style.

GoTo https://github.com/tzador/mootivator, follow the easy install instructions, and enjoy.

Here is one:

     ------------------------------
    ( The future of software isn’t )
    ( no-code, it’s new-code.      )
     ------------------------------
           \
            \    \__/
             \   (oO)_________
              \ (_.._)        )\
               \_ U  ||---w-||  *
                    _||    _||
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

But of course those all have generated by LLM, with a bit of forced prompting to get better jokes (self rating and picking the top).

I hope it puts smile on your face, even just for a little bit )))

Comments URL: https://news.ycombinator.com/item?id=45492151

Points: 1

# Comments: 0

Just enter a query or a URL, it will search and scrape the web, to produce one markdown file with all the results.

Searching for a URL prefix to get result from a particular site only.

Example:

- https://llminer.deno.dev/?q=https%3A%2F%2Fdocs.deno.com%2F

- https://llminer.deno.dev/?q=cocktail%20recipes

Once the markdown file has been downloaded, you can insert it into LLM of your choice.

WIP, looking for feedback, thank you.

Comments URL: https://news.ycombinator.com/item?id=42424499

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=42269284

Points: 2

# Comments: 0

It could work as follows:

- Go to HN and find a post you like, visit the post page like https://news.ycombinator.com/item?id=1 - Add it to your favorites list by clicking [favorite] right at the top

The following signup needs to be done only once:

- visit https://todo-hn-notifier.com - sign in with email - provide your HN username

Whenever a new comment appears in one of the favorite posts, an email is being sent. (With an easy unsubscribe link)

WDYT? Would you find such a web service useful? Any extra features would be cool to add?

Thank you.

Comments URL: https://news.ycombinator.com/item?id=42218521

Points: 2

# Comments: 2

Sorry, here is screenshot of a prototype IDE in browser with live preview.

The idea is to use TailwindCSS for prototyping UI, similar to Figma, but instead of drag-and-drop, you use a low-code approach with Tailwind-powered notation (inspired by Pug templates). The editor lives in the browser, with a live preview of the UI on the side, so you can instantly see changes as you type.

https://github.com/user-attachments/assets/661916c1-f604-47b...

There are some key benefits I think this approach could offer:

Consistency: Using Tailwind ensures consistent design across components.

Reusable Components: Easily define and reuse component collections and design systems.

Responsive Mocks: Prototypes can be responsive by default thanks to Tailwind.

Interactive Navigation: You can add navigation between screens to simulate user flows.

Real Device Preview: Since it's just HTML/CSS, the prototypes can be loaded on real devices for a realistic view.

Text-Based Mocks: This makes the tool LLM-friendly, potentially allowing integration with AI to generate code from prompts or even create designs from UI screenshots.

I’m also thinking about adding GUI controls to simplify the low-code experience for non-developers by letting them pick and add Tailwind classes via buttons instead of typing.

Here’s a quick prototype screenshot: [screenshot attached]

I'd love to hear your thoughts—does this sound like something worth investing time in? Any advice, suggestions, or concerns would be super helpful!

Thanks in advance for your feedback!

PS. I am still trying to decide if this approach is worth working on. So the question is, what do you think, is it worth the time to work on?

---

Here is a login screen example of low-code mock/prototype notation:

    // Main container for the login screen
    .bg-gray-100.min-h-screen.flex.items-center.justify-center.p-4
      // Login card container
      .bg-white.p-8.rounded-lg.shadow-lg.max-w-md.w-full
        // Title of the login form
        h2.text-2xl.font-bold.mb-6.text-center Login

        // Login form
        form(action="/login" method="POST")
          // Email input field with label
          label.block.mb-2.text-gray-700(for="email") Email
          input#email.w-full.px-4.py-2.border.border-gray-300.rounded-md.mb-4(type="email" placeholder="Enter your email" required)

          // Password input field with label
          label.block.mb-2.text-gray-700(for="password") Password
          input#password.w-full.px-4.py-2.border.border-gray-300.rounded-md.mb-4(type="password" placeholder="Enter your password" required)

          // Submit button
          button.bg-blue-500.text-white.w-full.px-4.py-2.rounded-md.text-lg.font-semibold(type="submit") Login

        // Link for forgotten password
        p.mt-4.text-center.text-sm.text-gray-600
          a.text-blue-500.hover:underline(href="/forgot-password") Forgot your password?

Comments URL: https://news.ycombinator.com/item?id=42098510

Points: 1

# Comments: 3

What would be pros and cons of implementing it in:

    - bash/zsh
    - keep in python
    - rust/go

What do you mean by capture output, like if i have ```bash echo "hello" ``` hello would appear in the rendered markdown?

    # [clean]() Clean build directory

    ```bash
    rm -rf ./build
    ```    

    # [format]() Format the source code

    ```bash
    npx prettier --write .
    ```

    # [build](clean format) Build the project

    ```bash
    npm run build
    ```

    # [deploy](build) Deploy to surge.sh

    ```bash
    surge ./build my-project.surge.sh
    ```

Thank you for feature suggestion.