styled lightboxes further, changed FAQ to PAQ

This commit is contained in:
Connor Turland 2014-02-07 17:25:02 -05:00
parent 17fe5fa241
commit 2045220622
6 changed files with 87 additions and 12 deletions

View file

@ -703,12 +703,6 @@ function openLightbox(which) {
$('.lightboxContent').hide();
$('#' + which).show();
if (which == "forkmap" || which == "newmap") {
$('#lightbox_content').css('background','white');
} else {
$('#lightbox_content').css('background','silver');
}
$('#lightbox_overlay').show();
$('#lightbox_main').css('margin-top', '-' + ($('#lightbox_main').height() / 2) + 'px' );
}

View file

@ -1493,6 +1493,7 @@ background-size: 30px 30px;
position: relative;
top:50%;
background-color: transparent;
color:black;
}
#lightbox_screen {
@ -1532,8 +1533,9 @@ border: solid 2px #000;
}
#lightbox_content {
background: silver;
background: white;
padding: 20px;
border-radius:5px;
}
.lightboxContent h3 {
@ -1559,7 +1561,7 @@ border: solid 2px #000;
#about > p {
color: #000;
font-size: 16px;
line-height: 20px;
line-height: 24px;
margin:10px 0;
}
@ -1582,6 +1584,7 @@ border: solid 2px #000;
#invite p {
margin:10px 0;
line-height:24px;
}
#invite .green {
@ -1751,6 +1754,12 @@ font-family:arial;
font-style: italic;
width: auto;
padding: 0 30px;
cursor:pointer;
}
.onConsole .new_map button:hover, .onConsole .new_map input.add:hover {
background: #19C8E4;
-webkit-box-shadow: none;
box-shadow: none;
}
/* FAQ */

View file

@ -26,7 +26,7 @@
</p>
<ul>
<li><a href="/faq">FAQ</a></li>
<li><a href="/paq">P(ossibly)AQ</a></li>
<li><a href="http://blog.metamaps.cc" target="_blank">blog</a></li>
<li><a href="https://plus.google.com/u/0/communities/115060009262157699234" target="_blank">community</a></li>
<li><a href="https://twitter.com/metamapps" target="_blank">@metamapps</a></li>
@ -38,7 +38,8 @@
<div class="lightboxContent" id="tutorial">
<h3>Tutorial</h3>
<iframe width="510" height="383" src="//www.youtube.com/embed/0Bd8XxlNG3U?rel=0" frameborder="0" allowfullscreen></iframe>
<div>Coming soon...</div>
<!--<iframe width="510" height="383" src="//www.youtube.com/embed/0Bd8XxlNG3U?rel=0" frameborder="0" allowfullscreen></iframe>-->
</div>
<div class="lightboxContent" id="cheatsheet">

View file

@ -35,7 +35,7 @@
<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
<%= csrf_meta_tags %>
</head>
<body class="<%= action_name == "faq" ? "bodyFAQ" : "" %>" >
<body class="<%= action_name == "paq" ? "bodyFAQ" : "" %>" >
<% if notice %>
<p class="notice metamaps"><%= notice %></p>

View file

@ -0,0 +1,71 @@
<%#
# @file
# Located at /
# Shows 3 most recently created topics, synapses, and maps.
#%>
<% content_for :title, "Possibly Asked Questions | Metamaps" %>
<h1 class="index">
PAQ
</h1>
<div class="FAQ">
<div class="question">Who may use Metamaps.cc? <div class="switch minimizeAnswer"></div></div>
<p class="answer">You! We are currently in "beta" mode, meaning that the application is undergoing continuous testing and refinement. However, we welcome participants in this trial process with the understanding that things are evolving, and may hold a few surprises! Request an invite if you'd like to explore and build with us. Feedback is always welcome.</p>
<div class="question">What does it take to learn to Metamap? <div class="switch"></div></div>
<p class="answer off">While the interface may not seem familiar at first, we've designed it to be both intuitive and empowering after a bit of practice. There are only a handful of basic functions, like adding topics and drawing "synapse" connections, that are needed get your creative process started. A handy cheat sheet is available on the canvas for reference while mapping, and we have an online manual and tutorials to grasp more advanced functionality. The best way to learn is to start mapping, and to connect with other mappers in our online community.</p>
<div class="question">What is the platform being used for currently? <div class="switch"></div></div>
<p class="answer off">At a basic level, metamaps are great for laying out complex ideas and scenarios. We're seeing maps of design work, topical research, project management, and narrative storylines. Some users have been capturing live workshop event documentation, or organizing study groups. We're using it ourselves to organize collaboration and develop strategies for the project. Check out our Featured Maps! We'd love to see what else you can come up with.</p>
<div class="question">Who made this up? Why? <div class="switch"></div></div>
<p class="answer off">The Metamaps.cc project was launched as an emergent collaboration between artist Gavin Keech, architect Ishan Shapiro, and web developer Connor Turland over the years 2010-12, with input and inspiration from many other peers and projects. Its design draws from the fields of computational cognition, collective intelligence, and human-computer interaction. We continue to seek optimal and novel ways to connect people and ideas through visual information. </p>
<div class="question">How is MM different from other "mind mapping" apps? <div class="switch"></div></div>
<p class="answer off">First and foremost, metamaps bring people together into a shared knowledge environment. Topics and maps "in the commons" invite collaborative editing and shared insight. As new content and connections are made throughout the system, all users benefit from collective intelligence. Other distinguishing factors on the platform include a flexible visual categorization system via metacode icons, no built-in structural biases, and a powerful search tool to find content.</p>
<div class="question">Is this an open source project? <div class="switch"></div></div>
<p class="answer off">One of the core principles of our work is the enhancement of the pool of commons resources such as open source technology and shared knowledge. Our basic application framework is licensed as GPL open source on Github for anyone to build on, and this public platform is freely accessible online. Custom features and implementations may be added on to this framework under more restrictive licenses by the development team for partners and clients.</p>
<div class="question">How can I find out more about the project? <div class="switch"></div></div>
<p class="answer off">Reading here is a great first step. We also suggest browsing our blog, visiting the Google+ community, or getting in touch by submitting feedback through the site. We occasionally host online and in person meetups where you can interact with other mappers and see how people are using the platform. The story continues to unfold, and we'd be glad for you to take part.</p>
<div class="question">How can I participate, or support the project? <div class="switch"></div></div>
<p class="answer off">We welcome contributions in many forms. One of the easiest and best things you can do is to keep on mapping your ideas into the commons on the platform! If you're a developer interested in advancing the technology, please join on Github. Designers and others with professional skills should get in touch about opportunities for freelance collaboration through our innovative Open Value Network organizational structure for business development opportunities. Financial contributions are greatly appreciated in support of our work, and can be made through ______</p>
<div class="question">Are you making money from it? Do you plan to? <div class="switch"></div></div>
<p class="answer off">To date, the Metamaps.cc project has been supported by volunteers and small grants or donations. We intend to establish an open collaborative environment to pursue revenue opportunities in an agile and equitable fashion by configuring products and services based on the open source Metamaps technology. Stay tuned for further info via our blog and social media, or get in touch if you'd like to join the team!</p>
<div class="question">I'd like to have a new / different feature. Where can I make suggestions and requests? <div class="switch"></div></div>
<p class="answer off">Thanks for giving it some thought. New features and functions are continually added to the platform as we seek to optimize the experience there for all users. If you find that something is calling out for addition or improvement, send us a note via feedback form or in the online community. The more detail and context you can provide, the better! </p>
<div class="question">I made a cool map...want to check it out? <div class="switch"></div></div>
<p class="answer off">Yes! Send us the link via feedback form or flag us on social media. We're always curious what mappers are able to do with the platform, and we'd love to pass great examples around so that others can see.</p>
<div class="question">Someone else changed my cool map (or favorite topic) without asking me...sad face :( <div class="switch"></div></div>
<p class="answer off">If your map / topic was set to Commons permission for editing, than any other logged-in user on the site will be able to make changes. We consider this a feature, not a bug, which encourages collaborative maps and an evolving collective knowledge garden. You can easily avoid unwanted changes by setting your permissions to Public, which others may still view and copy to another version if they wish. Courtesy, care, and the benefit of the doubt will go a long ways towards maintaining a happy, healthy, and productive communal atmosphere on Metamaps.cc</p>
<div class="question">How do I "_________" on metamaps? <div class="switch"></div></div>
<p class="answer off">Link to our cheatsheet stuff...and manual.</p>
</div>
<script>
$(document).ready(function() {
$('.FAQ').mCustomScrollbar();
$('.FAQ .question').click(function() {
$(this).find('.switch').toggleClass('minimizeAnswer');
$(this).next().toggleClass('off');
$('.FAQ').mCustomScrollbar('update');
});
});
</script>

View file

@ -4,7 +4,7 @@ ISSAD::Application.routes.draw do
match 'request', to: 'main#requestinvite', via: :get, as: :request
match 'invite', to: 'main#invite', via: :get, as: :invite
match 'faq', to: 'main#faq', via: :get, as: :faq
match 'paq', to: 'main#paq', via: :get, as: :paq
match '/search/topics', to: 'main#searchtopics', via: :get, as: :searchtopics
match '/search/maps', to: 'main#searchmaps', via: :get, as: :searchmaps