search

canonical-web-and-design / practices

Guides and principles from the web team at Canonical and Ubuntu
https://canonical-web-and-design.github.io/practices/
Other
44 stars 30 forks source link

New document: Choosing a framework #97

Closed nottrobin closed 5 years ago

nottrobin commented 5 years ago

This document lays out the reasons for choosing one application structure over another - e.g. Jekyll vs Flask, Flask vs Django.

I've also restructured the documents slightly to create a new section called "project structure".

Please read it and let me know what you think.

nottrobin commented 5 years ago

Thanks @Lukewh, I've addressed those two.

squidsoup commented 5 years ago

Hey @nottrobin, I don't see anything in here about building apps in js. That seems like a significant omission. Do we need another heading for client-side options?

nottrobin commented 5 years ago

@squidsoup yes, I haven't mentioned client-side software choices much, deliberately, I'm not the right person to write that part. I'd welcome a follow-up PR to add guidelines on client-side code after this one is merged (or even in parallel), but I'd rather keep the scope limited to the topics I've already covered in this PR itself.

nottrobin commented 5 years ago

@hatched just BTW, approving PRs on this repo is a bit different than on most repos:

https://github.com/canonical-webteam/practices/blob/master/CONTRIBUTING.md#approval-criteria vs https://github.com/canonical-webteam/practices/blob/master/workflow/github.md#merging-process

jpmartinspt commented 5 years ago

Looks good.

nottrobin commented 5 years ago

@b-m-f I created https://github.com/canonical-webteam/practices/pull/107 for your suggestions.