if i can't decide this, how can i even get a FULL v1 out?
You can: by following the
MotherFuckingWebsite.com's principles.
(1)I happened to have a software, which is a sort of proof-of-concept reverse-engineering project; and
I have released it on the WWW with full homepage and everything, despite the fact that I still haven't worked out what decor to use for its website-- even now!
Instead of taking the easy way out like many "kids these days" would do
(2), I simply
designed the site as if it was a report printed on a paper-- but instead of typing it in the word processor, I typed it up by hand, in HTML and only HTML; no styling at all.
The thing I kept in mind while making that is that "what exact set of information I have to give to people" who passed by in order to be informed enough about my software
(3), and type them in as bare prose.
And the result has been perfectly serviceable as a software homepage; it got description, it got screenshot, it got downloads (including binary downloads), it got full manuals. It's readable without JavaS'creep on desktop and mobile, including on the crummiest feature phone limping along on a 6 KiB/sec 2G connection.
User who wish to experiment could go download and test that out without having to second-guess; and developers can even read the reverse-engineering whitepaper that come with it without a hitch.
(4) I dare say that this site is more user-informing than 75% of code-barfed "projects" on Micro$oft GitHub.
Thus this is considered "Mission Freaking Accomplished"... without any sort of "theming" at all.
Of course, styling and
illustrating that site are still on my TODO list; but now I could do them at my leisure
(5), since the "actual project" was the software, and not the site design itself. Websites with complete and worthwhile information are treasure, no matter how unstyled that was.
On the flipside, I have a future section planned for my personal website dedicated for music playlists. I have already "finished" arranging and writing about the first playlist I would like to add for like half a year now, but I have yet to finish styling and illustrating the pages of that section. And for this one, I decided to hold off the entire section's release, until I have finished all that.
Why?
Because I treat this as an "unofficial fanmade indie music album" project. Which for such thing, it wouldn't be just audio and playback order that mattered: presentation, aesthetics, and vibe were all in the play. Unlike software project which what mattered was the functionality and factual information on how to operate it; music is about experience. Simply linking a playlist file from a bland webpage would make it a very mundane experience indeed.
I intend for this to be special; so I'm going to make sure that the first impression I made being
precisely nailed.
To style or not to style, that is the question; but once you could determine whether you aim at making a site to disseminate information, or making it to impress someone; I trust that a suitable answer for the first question will come to you.
P.S. The "unstyled style" of websites is known in some literature as
"Prof. Dr. Style".
(1) If carpet F-bomb-style of manifesto isn't your jam, see
this one instead.
(2) Which comprises of barfing it onto the code-launderer-disguised-as-forge-platform GitHub and call it a day.
(3) Note that the I didn't say "to use my software", because I'm not trying to convince them. If they think it fitted their bill, then that's nice for them; but if they don't think so, that's fine too. That's also a reason why I "advertise" the list of
limitations up front; I wish more programs actually do that instead of having users find out about them the hard way.
(4) And I believe it is the most complete description of file format used in this family of program that you could find online.
(5) I consider the lack of documentation a
blocker-priority in my own software release. If the manual and website wasn't satisfactory
information-wise, I hold off releasing that software.