Proposed Website Changes - Datatables about cdnjs HOT 7 CLOSED

Will create a new page called /browser simliar to npmregistry and implement using dataTables. In the first top left column we will invite users to try the new beta search.

Probably always keep everything as a single page app because we won't benefit from SEO unless we split the packages.json into actual HTML.

cdnjs.com will stand as the info page that links to the /browse page

this could have been a standard for cdncss.com but someone has registered it hrm

from cdnjs.

I registered cdncss.com

from cdnjs.

lol perfect,

well I have a great design idea and will do beta this afternoon. Gym at 8ish

from cdnjs.

Also if we can move packages.json to the CDN, we don't have to worry about moving it to the website all the time. What were the cons of this again?

from cdnjs.

That's up to CloudFlare. I can't personally think of any cons. To be honest,
I think it would open things up for a whole lot more innovation.

On Thu, Sep 8, 2011 at 2:10 PM, Thomas Davis <
[email protected]>wrote:

Also if we can move packages.json to the CDN, we don't have to worry about
moving it to the website all the time. What were the cons of this again?

Reply to this email directly or view it on GitHub:
#97 (comment)

from cdnjs.

We wouldn't actually be moving packages.json to the CDN. We'd only be moving each individual package.json.

packages.json would require manual updating to stay in sync with the repository.

from cdnjs.

Lol we used datables

from cdnjs.