dropdog / docs Goto Github PK

Mobile first means that all of the development/design/content strategy needs to follow this. Not only the css/html. If we can totally follow the "mobile first" methodology then I am with it too. Here are some basic things that need to take under consideration for the "design" process.

• Content (which are the components of the content, which are the fields, how long are the texts etc)
• css (how easily can we "break" the pieces of the design into individual, standalone elements?)
• html tags (which are the wrappers, how should content behave on different positions on the page?)
• media queries (which breakpoints make sense?)
• html meta tags (initial scale etc)
• the target group of the distro (will the target group do a heavy use on mobile?)
• testing (can we test the mobile behavior easily, do we have ready tests to do this?)
• design mockups (should begin from mobile for every new feature designed)

So for me it is good to follow the mobile first design if the above (and probably many more) parameters can be satisfied. Content (user generated content) plays a major role here...

cc @Vaggos

A question for the db backups.

Do you know if there is any issue with unix and other host servers when using files with the ":" symbol?

livedb-2016-01-29T14:04:46+02:00.sql

I found an old but clean Styleguide of basic html elements at https://github.com/theodorosploumis/styleguide/blob/master/codes.html.

Notice that the Styleguide need to meet the Parameters.

cc @Vaggos

I realized we have no license for these docs. We have to decide asap because Google indexes the pages. Proposed licenses are:

• Creative commons
• Open Publication License
• GNU Free Documentation License

Please propose yours and let me know.