Feedback on the landing page

[skorokithakis]

@callahad has requested feedback on the landing page, so I figured I'd make an issue about it (I think issues are a bit more permanent than the mailing list, as I can never navigate the Google Groups UI).

Let's keep this issue open for a few days to give people a chance to post feedback, if someone notices that at some point there has been no activity in two weeks or so, feel free to close it.

CCing @djc, @onli, @buro9, @jleclanche, @TazeTSchnitzel, and please feel free to CC anyone I might have forgotten.

I will post my feedback as a reply shortly.

[skorokithakis]

My feedback:

• "Email addresses are decentralized, self-hostable, and the lowest common denominator for identity on the Internet." So? Does portier host them? What does it do? Saying something like "that's why they are the basis of Portier" would clarify this sentence in my mind.
• "Portier does not hide or obscure email addresses." This seems like a downside? What other services hide email addresses? From whom? If I'm a user, I probably want my email address to be obscured!
• The "Why?" link in "Never" points to a document on Github, I think it would be a bit nicer if it were just a page on the site.
• The design page is very clear on everything, and gives a good overview of Portier.
• The specifications page is pretty light, but still good. I'd prefer it if all the Markdown pages were rendered, though. Jekyll/Lektor?

[onli]

We are talking about https://portier.github.io/, right?

I think your feedback is on point. In general it is a very useful page to have.

[callahad]

Great points. Will fix most of them shortly.

I'd prefer it if all the Markdown pages were rendered, though. Jekyll/Lektor?

We should absolutely do this eventually. But for right now, a bunch of .md files have a much lower barrier to me actually getting content online than a static site generator; no bike-shedding about design or fussing with CSS and formatting. I can just write. Plus, if it's good enough for https://webassembly.github.io/ ... 😉

Once the content is relatively complete, we can figure out what form best suits it and port it to Jekyll for easy GitHub Pages support.