Seems amazing, but more demos/examples would be nice, and installation instructions right on the homepage. Web editor would be great. Seems to be written for jvm :( The language spec is amazing and styling is slick.
HN user
timz
Amazing.. Would be nice to have something like that for Redis to replace Lua
Fantastic, would love to see same js support for redis as oposed to lua scripts.
very nice. a somehow similar project https://englishell.js.org/
https://www.assemblyscript.org/ is somehow similar, but targets only webassembly now
Not sure why, but seems very interesting and creative. What is the logic behind it?
yes, indeed, they are. but within those 2 weeks notifications could still be useful, i think.
Amazing, great product and slick implementation. Not sure if it is allowed to play youtube videos in custom player though, since ads are skipped.
https://i.ibb.co/Jt7mjXW/screenshot.png
Sorry, here is screenshot of a prototype IDE in browser with live preview.
Hey everyone! I'm experimenting with a UI prototyping/design/mocking tool concept and would love to get your feedback.
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?Currently implementation is in python, since it is available in many places, but not all.
What would be pros and cons of implementing it in:
- bash/zsh
- keep in python
- rust/goThis is useful idea, will examine in detail
Could you elaborate please?
What do you mean by capture output, like if i have ```bash echo "hello" ``` hello would appear in the rendered markdown?
Added support for dependency between commands. So one can now write:
# [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
```
This doesn't include file time modification between files as in Makefile.Thank you for feature suggestion.
Thinking about the suggestion regarding command dependencies, possibly we could add something similar to Makefile:
## [clean]() Cleans the generated files
```bash
rm -rf ./build
```
## [init]() Initializes the build folder
```bash
mkdir -p ./build
```
## [build](clean, init) Builds the project
This command depends on clean, and init, which are executed in that order beforehand.
gcc magic.c -o ./build/magicnow commands are defined like this withing any header, and end on the next header.
### [my-command-name]() My command short description
A longer command help
```typescript #!/usr/bin/env deno run console.log("hi") ```
if hashbang is missing, it is infered from the markdown codeblock lang speck, with fallback to bash.
This is really cool approach.
I see where you are coming from for C/C++ based projects, but for more higher level ones, this is being taken care of by the compilers themselves.
Updated, makedown it is
I see, good point. Currently I implemented it in python for portability reasons, since it is available on most POSIX systems by default.
The stripped Docker containers are used mostly for runtime to my understanding, building is done in a different container where more build tools are available.
In case of single binary (now it is single python file), what would be the best way to distribute it to users, since pypi and npm cannot be used?
Which language you would suggest?
- renamed to `makedown` - rewrote in python, since it is available out of the box on most POSIX and in GitHub actions - Updated to `### [my-command]() Explanation of command` syntax, this way GitHub highlights the commands nicely
Thank you for all the feedback
Love the makedown name, renaming.. As for a short name available in terminal, we can add alias m="makedown" as part of zsh completion script. Both: $ makedown deploy-to-production and $ m deploy-to-production --help will work
Aditionally we can generate html out of the, now `makedown.md`, right in the tool: $ makedown --html makedown.html or $ m --pdf makedown.pdf
published 0.3 version pnpm install -g @tzador/x.md
- better --help messages with or without command - ## level 2 headers are used - the temp file is created in current folder, like that importing npm modules from current project works
Great suggestion. On it
When --help is provided, the help text from x.md is printed. Otherwise all the command line parameters are passed to the actual script that implements the command.
should be working now https://github.com/tzador/x.md
Great App, saves time and focus. Would love to see it evolve with more features, like discovery of new related feeds, freshness vs relevance tradeoff, or even email digest once a week or so. Keep it up, great work.
That is a cool trick, i should add an option to copy that code as well.
Thanks for the feedback, will tweak the prompts.
Not sure tpdne would allow to use their images