It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: SkepticOverlord
originally posted by: DexterRiley
Can you provide a couple of Use Cases?
Perhaps a vision of the workflow might be a better starting point.
1) an independent journalist is registered with the new site, and also an ATS member
2) via interaction with members on ATS, journalist gets an idea for a new investigative piece
3) on ATS, journalist puts together his ad-hoc research team
4) journalist and team move to the new site's private area for collaboration
5) the new site has tools to organize research, assign roles, and manage schedules and communications
6) the new site has authoring tools for the journalist to create content optimized for delivery
7) journalist and team review the finished article, and approve for delivery
8) new site delivers the content, optimized for all screens, connections, and social networks
9) journalist interacts with audience on ATS for feedback, new information, and revises the original content accordingly
The above should hold true for video, audio, comic, op-ed, and any other type of content supported by the new site.
One of the most important parts are to facilitate the creation of an ad-hoc research team... giving independent investigative journalists something they've rarely had before, a research department. The other most important part is a nimble front-end that intelligently refashions content delivery specific to the user's form factor from desktop to everything else including smart watches and in-dash car entertainment systems: IoTJ - Internet of Things Journalism.
Make sense?
originally posted by: EvillerBob
There are plenty of frameworks for responsive layouts that are constantly being developed, improved, and updated for modern technology. I'm always a big fan of quadrupling my workload by needlessly reinventing the wheel, but even I stick to Bootstrap for responsive UI. Like far too many of us, I've been guilty of finding myself spending more time on making projects pretty than making them work.
originally posted by: SkepticOverlord
I get why people use the responsive frameworks, but I despise them! Bootstrap, ResponsiveUI, and all the others, in my opinion, foster a mindset of design compromise along with sending unused CSS3/HTML to mobile devices. I'm an advocate of distinct versions of CSS3/JS/HTML5 for each device category: desktop, tablet, phone, and small-screens (watches). That way, each use-case only receives the front-end code specific to their needs, with no responsively-ignored overhead. It's a bit more work, but it removes the compromise thought process from designing for each device category.
originally posted by: EvillerBobWhat happens when you serve to a tablet and the user decides to rotate it from vertical to horizontal? You end up needing some element of responsiveness anyway.
originally posted by: SkepticOverlord
originally posted by: EvillerBobWhat happens when you serve to a tablet and the user decides to rotate it from vertical to horizontal? You end up needing some element of responsiveness anyway.
That's easily handled in the CSS. But the point being, that person on the tablet with a bandwidth cap from a wireless carrier will get a smaller payload than the person at home on their laptop/desktop.
Google mobile detect code (PHP and Python) is very good, and constantly updated.