$HOME every 30 minutes.
bash(1) related dotfiles to https://adi.onl/.*.html!
> We all learn it at the infantry school at Benning: hope is not a course of action.
https://mobile.twitter.com/WarintheFuture/status/1497716050799980545/retweets/with_comments
https://twitter.com/WarintheFuture/status/1497716050799980545?t=f757CvpAGfsx1iUkXBSiRQ&s=19
I'm just saying... You can do some research on that guy, Major General in the Australian Army.
@prologic @david @jlj
mk(1) version https://adi.onl/bin/mkfile !
mkws is my solution, you could replace the main script with make(1) or Plan9's mk(1) if the build time gets too long, but it makes sense it works well, you're basically compiling "source code", .upphtml files to "binaries", .html files using a compiler, pp. All the tooling fits well.
m4(1), altough I'm not a big fan of the syntax?
HTML then if you're getting into more complex stuff? Why insist on Markdown? Use Markdown for blog posts or similar content and use HTML for the complex stuff?
vi implementation: https://github.com/kyx0r/nextvi
HTML in Markdown? I believe most of the times, no, but again Markdown is mostly for blog post like content.
Markdown by default in a ssg?
mkws http://s.minos.io/ (and other stuff too), but I don't see any http server or Markdown editor (smu, lowdown, cmark, discount) inside.
mkws http://s.minos.io/ (and other stuff too), but I don't see any http server or Markdown procesor (smu, lowdown, cmark, discount) inside.
mkws http://s.minos.io/ (and other stuff too), but I don't see any http server or Markdown editor (smu, lowdown, cmark, discount) inside.
Ok, I misunderstood the term “landing page”, but the main idea is Markdown is for blog posts.
>That is of course your opinion bud 😆 And one I don’t share 🤗
Not opinion but quotes form the authors!
>That is of course your opinion bud 😆 And one I don’t share 🤗
Not opinion but quotes from the authors!
> The basic idea behind all weblog software — reduced to a nutshell — seems so simple in retrospect. Rather than managing a web site as a collection of pages, you manage a collection of posts, and the weblog software takes care of turning the posts into pages for you.
https://daringfireball.net/2004/03/dive_into_markdown
> The idea was to make writing simple web pages, and especially weblog entries
> We’ve tested it extensively: on our blogs, in my comments form, in our emails.
http://www.aaronsw.com/weblog/001189
And by "simple web pages" he means this kind of _simple_ https://mkws.sh/docs.html !
Markdown is not for landing pages like https://mkws.sh or https://peguero.xyz/ or https://www.andrewjvpowell.com/.
> The idea was to make writing simple web pages, and especially weblog entries
> We’ve tested it extensively: on our blogs, in my comments form, in our emails.
http://www.aaronsw.com/weblog/001189
And by "simple web pages" he means this kind of _simple_ https://mkws.sh/docs.html!
Markdown is not for landing pages like https://mkws.sh or https://peguero.xyz/ or https://www.andrewjvpowell.com/.
and
> Markdown is a text-to-HTML conversion tool for web writers.
> Markdown is a text-to-HTML conversion tool for web writers.
Markdown was made mostly for content less for presentation.
Markdown based static site generator!
mdoc(7) is also nice if you're on OpenBSD to get a nice mdoc template.
Markdown you start to see its limits, that it's not that flexibile and you have to get in the internals of the static site generator, complicating things.
mkws I used HTML by default because using Markdown as most static site generators do feels limiting. That's why people complain they of the lack of customizability. In the About Me, My Projects, Other Stuff _presentation_ pages you can go as wild as you prefer with HTML, on the blog side, do Markdown.
Markdown when you're updating often, like blog posts, Markdown is easier on the fingers indeed (less to write) but when doing the _presentation_ part, do HTML.
Markdown, don't nitpick on words, whereas HTML is doing a good job there.
HTML is evidence enough.
Markdown was that great for everything, we would all be writing Markdown, not HTML.
> fact that for complex pages Markdown is ill suited
Do you believe
Markdown is suited for something like this https://git.suckless.org/9base/log.html or this https://git.suckless.org/9base/commit/09e95a2d6f8dbafc6601147b2f5f150355813be6.html? Those are statically generated btw.
HTML from Markdown as far as I remember.
Markdown is ill suited as you yourself saw when building https://prologic.shortcircuit.net.au/
Your name's initials, or your _chosen_ initials?
Markdown by default falls short when it comes to customizability.
Markdown by default falls short when it comes to customizability, if you have lots of pages, then yes and maybe writing often (blog), I agree, it's a good idea to use Markdown, but if you have a 3-4 page site, that you don't update often, HTML is enough IMO and _the good tool_. Having to do all this in Markdown https://peguero.xyz/ might not work so great! I'm pretty sure he's using Markdown for the blog posts tho.
And if you have stuff you "don't know where to put", just replicate your operating system's directory structure
hier(7).
Or if you have complexity, keep it as close to the reader's eyes as possible.
bin, simple, shared stuff goes in share, again, familiar and simple, and in plain view, you KNOW the directories are there, no looking for them, plain ls just works, you don't have to ls -a.
bin, simple, shared stuff goes in share, again, familiar and simple.
mkws has a _familiar_ directory structure, you kinda intuit where stuff goes.
zs, I disagree with the hidden directories .pub, .zs, especially considering that hidden directories in UNIX where a _mistake_. Looks clean, but it's not. Plan 9 doesn't have them.It's like _hiding_ complexity, best is not to have complexity to hide.
> The name stands for 'zen static' as well as it's my initials.
Rename it to
jm please! 😛
> without any esoteric bells and whistles
Yes!
> now if i could take a course in css and html. i’m an old backend engineer who cannot draw stick figures :)
Here is a good starting CSS https://envs.sh/EpE.txt, this will give you a decent looking page. Or this if you prefer a Monospaced version https://envs.sh/EpQ.txt
HTML.
I disagree, I'm saying your worldview is unrealistic! 😛
lua as an alternative to js in the browser.
mkws and lua?