remotestorage / website Goto Github PK

See also https://community.remotestorage.io/t/community-call-redesigning-the-remotestorage-homepage-other-stuff/705

The idea is to use special (wiki-editable) topics in Discourse that can be rendered as static pages via a plugin. @rosano has already tested the basic setup for that (see test page).

For production use, we can then also set up a simple Nginx vhost to serve those pages on the main domain, as well as redirect wiki pages to new URLs.

https://remotestorage.github.io/website/ is missing the topbar content, it's blank for me.

Would be great i think for newcomers to have a "Quick start" shortcut in homepage that points to https://wiki.remotestorage.io/RemoteStorage.js:Beginners%27_Guide

• gh-pages for staging/dev
• 5apps for production

If you hit "Get Storage" (or any wiki link) from the frontpage, the topbar changes font and padding.

https://opensourcedesign.net/jobs/job-form/

The current version of the new site doesn't give any pointers for where to go next. Some things could also still be added to the frontpage (like "check out some apps" with a link to "browse more apps" etc.). I guess it's mostly just adding "learn more"-type links to the various sections.

Sometimes when scrolling down, the content overlays the forums header (mostly saw it in PMs iirc).

Currently, it doesn't really work on phones.

https://www.mediawiki.org/wiki/Extension:MobileFrontend is the official extension with the styles they use on Wikipedia as well.

https://kosmos.social/@remotestorage

Seems like Jekyll supports contributors to the current repository or organization_members which exclude people from commits. Ideally there would be something like organization_contributors to show people from commits in all repositories across an organization.

I found some ways to show this information via the GitHub API:

• https://daquinoaldo.github.io/organization-contributions/?org=remotestorage
• https://api.github.com/orgs/remotestorage/repos
• https://api.github.com/repos/remotestorage/website/contributors

and will try to either integrate directly with our project, create a plugin, or PR to Jekyll. Will post updates here.

Though the spec says

The URI itself only provides identification; access to the resource is neither guaranteed nor implied by the presence of a URI.

I think it would be nice, as they are http URIs, to have some content on them.

So I would suggest adding these two pages

• http://remotestorage.io/spec/version
  • Maybe a list of versions
• http://remotestorage.io/spec/web-authoring
  • An explanation of what web authoring is and how this property is used

Main site or wiki.

CleanTalk is warning us about an outdated extension in their UI. We need to update it.

encryptic-team/encryptic#168
litewrite/litewrite#304

• Main site
• Forums
• Wiki

  <script type="text/javascript">
    var _paq = _paq || [];
    _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
    _paq.push(["setCookieDomain", "*.remotestorage.io"]);
    _paq.push(["setDomains", ["*.remotestorage.io"]]);
    _paq.push(["disableCookies"]);
    _paq.push(['trackPageView']);
    _paq.push(['enableLinkTracking']);
    (function() {
      var u="//analytics.5apps.com/";
      _paq.push(['setTrackerUrl', u+'piwik.php']);
      _paq.push(['setSiteId', '5']);
      var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
      g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);
    })();
  </script>

Since we have moved all relevant wiki content to the new website in #59, we can now retire the wiki.

I have already re-configured the Discourse server to use Nginx on the host instead of the Discourse container, and added and tested a new wiki vhost to redirect certain pages to the new ones, and all others simply to the frontpage.

Only opening this to switch DNS, configure TLS with Let's Encrypt, and test again that everything works, and to have the removal of the wiki documented properly.

From a forum comment:

in the architecture diagrams you use the colours red and green to discern between developer- and user-managed entities, respectively. However, those two colours are the ones that are hardest to keep apart for most colour blind users, so you might want to change one of them

At the moment, only the main links from the left side are shown, but not the additional ones from the right. I think they should all be part of the mobile view as well.

What I understand:

• The aims of this project (in general)
• This is a protocol used for web apps without server interaction (what you call https://unhosted.org/ apps)
• This is about data storage somehow
• The data is not stored on a server (?)
• You have some kind of email for "login", but it is no real mail

What I do not understand:

• How can I register for that mail? If I enter any mail, I do not get far…
• Where is the data really stored? I mean, if not locally, it must be on some kind of server in the web, so it must be somewhere, huh?

It may miss:

• some (easy) demo/tutorial, so I can see what to do
• some funky SVG or animated SVG/HTML or whatever showing a graphic of the technical things in real time (points flying around, you get that, yeah… like "How does it work?" at the bottom of https://matrix.org/ to name an example)

Running a very outdated version. Upgrade howto:

https://cleantalk.org/help/update-mediawiki

E.g. clear distinction between headline levels (see Beginners Guide for why). Maybe use Open Sans, like everywhere else, and so on.

bring your laptop please

... or add in development builds. Whichever is simpler.

At least NLnet and Wau Holland Stiftung who sponsored a lot of RS work in the past.

Apparently the wiki is still using an older version, where the user-created hook is a bit broken (shows the user name twice).

Thanks to @rosano for reporting this to me. It looks like Namecheap's redirection service is rather unreliable, so we should just move that to a self-hosted nginx somwhere.

Not entirely sure, but I think it would be nice to communicate at least some of these:

Backend as a Service

Develop your web app without worrying about hosting or even developing the backend for it: your users will connect their own backend at runtime.
Infinite Scalability

Infinite Scalability

No matter if 5 hundred or 5 million users are using your app, your backend scales automatically and never costs you a single cent.

Wheels Included

remoteStorage.js is a JavaScript library that does all the heavy-lifting of connecting to any remoteStorage backend, caching, synchronizing and storing user data.

RUBY_GC_MALLOC_LIMIT=90000000 is the recommended value for conservative installations.