zyncco / website Goto Github PK

Our SSL is valid on zync.co, which is fantastic. Chrome and Firefox both love it. However, our certificate is issued to glowsync.com, which is another site being hosted on Firebase. No clue what's going on there, but it might be something we have to look into.

Vilsol, [07.03.17 14:17]
    can we please use something other than GIT to organize the fucking API
Vilsol, [07.03.17 14:17]
    so PITA to navigate
Vilsol, [07.03.17 14:18]
    no
Vilsol, [07.03.17 14:18]
    like
Vilsol, [07.03.17 14:18]
    use GIT
Vilsol, [07.03.17 14:19]
    but use some visual html generator
Brandon Currell, [07.03.17 14:20]
    As in like Doxygen or Sphinx, or gh-pages?
Vilsol, [07.03.17 14:21]
    gh-pages, but im choosing a generator atm
Vilsol, [07.03.17 14:21]
    Swagger looks pretty good
Vilsol, [07.03.17 14:24]
    Brandon try http://editor.swagger.io/
Vilsol, [07.03.17 14:25]
    its really nice

I agree with him, Swagger is nice. Here's my idea.

We use our static site (zync.co) as more than just a landing page. We also host a pretty HTML version of our API spec on it using a mixture of Jekyll and Swagger. All of the work is already done for us (see links below), we just need to create the Swagger JSON file. I do not think that this should be an alternative to the Git repo with all of the Markdown files though. I think we should provide both. It wouldn't be too difficult to manage both sets of data since Swagger will take a single JSON file with all of the endpoints and information in it. We might even be able to create a script that populates the Swagger JSON file for us from the Markdown, or vice-versa, but in my opinion, that won't be necessary since we shouldn't need to change the Spec much once it's finished.

Thoughts?

https://help.github.com/categories/customizing-github-pages/
https://jexhson.github.io/jekyll-swagger/

Use firebase hosting to host website.

• Main Page
• Team Page
• Downloads Page

CSS is being cached hard. Since GitHub pages is designed to host dynamically-built content, I'm blaming CloudFlare. We want zero caching happening on the apex site, and TBD caching on the assets site.

As discussed during the second meeting, we are going to have a section of the static site introducing the team. I don't really know any of you too well, so I don't know what to put. Please provide me (via comment here) with a picture / avatar, your preferred handle, your title relating to this project in your words (developer, designer, code monkey, whatever) and 1-3 sentences about you. If you would like links to your github profile, twitter or other external site included, please provide those too. I will find appropriate sprites to accompany them.

Please keep everything SFW, preferably G- or U-rated. Whilst unlikely, there's a chance that our userbase will be younger than we are.

Once you have done that, feel free to unassign yourself.

Thank you.

Edit: At request of Amir, please provide the name you wish to have listed (first or full, your choice), and optionally your online handle. For example, I have put "Brandon (Yeti)" and I assume Amir will put "Amir Omidi".

It'd seem the zync.co firebase isn't deployed. I don't know if this was Intensional, though I thought I'd report it anyway.

This website will ultimately decide how are apps are going to look like.