Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
integrate instructions about github and AWS hosting for gigapixel to FAQ
- Loading branch information
Showing
129 changed files
with
7,026 additions
and
2,988 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,3 +15,6 @@ s3analysis/mirror | |
s3analysis/*csv | ||
|
||
env.sh | ||
local_only.key | ||
local_only.crt | ||
|
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Hosting your Gigapixel through Amazon Web Services | ||
|
||
Before you can begin this process, you wil need to have generated Zoomify images. You can learn more about how to make one [here](/gigapixel/). | ||
|
||
Note: While Amazon supports free web hosting through its Free Tier option, after a year, you will have to pay to use their hosting services. It's relatively cheap (~$.03 / month for 1 GB, using their [pricing calculator](https://calculator.s3.amazonaws.com/index.html), but if you want an entirely free option, you can check out our GitHub hosting tutorial [here](https://github.com/NUKnightLab/StoryMapJS/blob/master/GITHUB_HOSTING/GITHUB_HOSTING.md). | ||
|
||
1. Sign up to create an account on [Amazon Web Services](https://aws.amazon.com/). If prompted, choose the 'Basic' account setting. | ||
![](1.png) | ||
2. Once your account has been created, choose the 'Host a Static Website' option on your dashboard. You can also click [here](https://console.aws.amazon.com/quickstart-website/new) to go to the same place. | ||
![](2.png) | ||
3. On your computer, navigate to the folder where you've stored your Gigapixel tiles. Inside the directory, create an empty file called 'index.html.' | ||
![](3.png) | ||
4. Compress your Gigapixel image folder. On Macs, you can right-click and select the 'compress' option. On PCs, you should right-click and then select send > to compressed file. | ||
![](4.png) | ||
5. Now, go back to the quickstart web hosting page, and upload your compressed folder. | ||
![](5.png) | ||
6. Amazon will spend ~15 minutes to publish your Gigapixel to their servers, but once Amazon is done, they will provide you a link to your hosted webpage. The location of the link is highlighted in the red box below. | ||
![](6.png) | ||
|
||
You're done! Use the [Storymap authoring tool](/select/) to create your Gigapixel and include the link to your Amazon webpage. If you need more information on best practices after creating your Gigapixel, you can read our documentation [here](https://github.com/NUKnightLab/StoryMapJS/blob/master/BEST_PRACTICES/BEST_PRACTICES.md). | ||
|
||
![](7.png) | ||
/ |
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
#Storymap Gigapixel Best Practices# | ||
|
||
|
||
After you’ve created a Gigapixel image through the process described [here](https://storymap.knightlab.com/gigapixel/), there are two options for displaying your Gigapixel in the Options Panel: ‘Image’ and ‘Cartography.’ While most of the features are the same in each mode, there are a few quirks of each mode that you might want to be aware of when creating your StoryMap. | ||
|
||
![Options Panel](1.png) | ||
|
||
##Best Practices for Image Mode:## | ||
|
||
|
||
In Image Mode, StoryMap markers are displayed only on hover, and path lines between markers are removed. Since these lines are removed, you should use this option if there is no spatial relationship between consecutive slides. | ||
|
||
|
||
For the overview image, your Gigapixel will be resized to fit only the left hand pane of your StoryMap. If you’re using an image that has a dimension that’s more than 5x the size of the other dimension, the image may be difficult to see. Thus, when choosing images for your Gigapixel, you should try to use images that have a width:length ratio of 3:1 or less. You may also want to avoid images that have excess margin, if you want to maximize the size of your image in the overview panel. | ||
|
||
|
||
![Proper Size](2.png) versus ![Improper Size](3.png) | ||
|
||
|
||
If you want the image to fill the entire panel, you should choose an image that is sized in portrait view (2:3 or 1:2), rather than landscape. If none of these options work for you, you can use Cartography Mode instead. | ||
|
||
|
||
##Best Practices for Cartography Mode:## | ||
|
||
|
||
In Cartography Mode, StoryMap markers will always be displayed, and path lines between consecutive markers will be displayed. You should use this mode if you want to emphasize the spatial relationship between events, or if you want to customize sizing without the constraints of Image Mode. | ||
|
||
|
||
For the Cartography overview image, your Gigapixel will be resized so that all of your markers will be displayed in the left hand pane, making it possible for your image to fill the entire screen. | ||
|
||
|
||
If you want to have your map fill the entire screen in the overview, the best way to do this is to have your markers concentrated on a single area of your map. For example, in the Arya’s Journey Gigapixel, the map markers were concentrated in the left-hand side of the map, allowing the right-hand side to fill up the rest of the screen. | ||
|
||
![Cartography Sizing](4.png) | ||
|
||
|
||
|
||
If you’re having trouble aligning your map, you can also tweak the maximum width and length of your map in the ‘Options Panel,’ which will adjust the display sizing. | ||
|
||
|
||
![Max Width/Height Adjustment](5.png) | ||
|
||
|
||
If your StoryMap is not displaying as described above, or if you have any other questions/bugs regarding Gigapixel displays, reach out to us at Zendesk! | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
body{background:#fff;color:#000} |
Large diffs are not rendered by default.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.