Deliverable D4.1 - DREAM public collaborative website is the first deliverable at M1. It matches the online presence of our team and team work, including:
Ted Nelson’s assistant Keith Shapiro failed to reply the simple question and instead told me that “Dr Nelson has no time for other people’s projects. Sorry” which I interpret as DWTFYWWI. Unless Dr Nelson suddenly has an urge to cringe about other people’s projects, we’re safe to assume our logo is fine as it is. If something else happens, we at least have a public record of the matter at hand.
There’s not a single line of JavaScript here – except for displaying the Discourse topics.
Note: the footer (in misty rose) is actually fixed, so it always appears at the bottom of the window.
background suggestion: #fff6d6 – I prefer lighter/warmer/less prominent colors as background – I took the lemon curry color from there and made it lighter
also, I like this palette: https://github.com/morhetz/gruvbox#light-mode-1
though it looks already good just by using the lighter background i mentioned above,
perhaps the blue could be changed to #076678 from this palette
and the button background to #9d0006, it has too much contrast currently
I like the direction you’ve taken the design of the website, @how.
Especially happy to see you using semantic HTML and modern (but uncomplicated) CSS patterns such as variables, to keep things clean and easy to maintain.
I mentioned this in our chat room, but in case you missed it, I would love it if you took a look at the website I made for my NLnet-funded project “secushareBOX”:
Another fun thing to note on the box.secushare.org site is the “tooltips” which popup when you hover over the bold text with the dotted underlines.
Please note that there is no javascript used anywhere on this website.
I like your approach @dvn. We use similar minimalist techniques. I did not use CSS Grid this time.
In the latest installment which just went live, I prepended the CSS with Normalize.css: an oldie and goodie that remains a user-made fix to browser differences so that the site appears about the same across browser vendors – hopefully: I did not check yet.
There are still a few known issues:
no support for vendor-specific CSS attributes (esp. for flex items, e.g., there must me some --webkit-foo-stuff lyring around in older versions), but maybe I’d like bug reports for those
the topics list inclusion could be bettered. I’m especially interested in considering including all Work Package reports and making the titles stand out a bit more.
the button links lack contrast (OK, you can see the flame color, but the text color lacks contrast)
I find the contents lacking a bit for a home page. But do we really need more? Maybe download links, links to specs, etc. when we have them. It would be easier to think about it in advance to be able to add them easily…
The styling of the pages behind, served from Discourse, should match this one.
Another minimalist approach you can see at p2pcollab.net.
It’s using pandoc with Tufte CSS and a pandoc template, and a Makefile that generates html from org/md files. I’m planning to look into AsciiDoc and make a similar template for it.
First impression feedback from a friend on the content of our website, which I’ve distilled into some points:
Lots of buzzwords/lingo
Unclear if the group will be distributing (3rd party) end user applications, or developing them, or simply developing a decentralized framework for existing collaboration apps
Not sure what level the work is being done at.
What is the relation to MirageOS? Is it a fork?
Is this a containerization system for a decentralized cloud?
