Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML Code #93

Open
tpcolson opened this issue Jan 12, 2016 · 3 comments
Open

HTML Code #93

tpcolson opened this issue Jan 12, 2016 · 3 comments
Assignees

Comments

@tpcolson
Copy link
Owner

Preparatory for migration and regression/functionality testing, html code used for the "Full" version should reflect what is used for the standard NPMap Builder project, such as view-source:http://www.nps.gov/maps/full.html?mapId=b32e4c79-caac-4266-9d6e-5b5cee8fa5d8 with the custom html only going inside the body elements. Head elements, as well as css references, should be same as view-source:http://www.nps.gov/maps/full.html?mapId=b32e4c79-caac-4266-9d6e-5b5cee8fa5d8. Continue using same GA code. For now, script source paths should be updated to the Fully qualified path on NPS web servers (e.g. http://www.nps.gov/maps/assets/libs/reqwest.min.js).

The top of the "Full" page should be as http://www.nps.gov/maps/full.html?mapId=b32e4c79-caac-4266-9d6e-5b5cee8fa5d8 with the only text change being "Species Mapper" on the second line under "Great Smoky Mountains National Park".

@tpcolson
Copy link
Owner Author

In addition the "bottom" of the full version needs to look as http://www.nps.gov/maps/full.html?mapId=b32e4c79-caac-4266-9d6e-5b5cee8fa5d8, as well as the disclaimer font. I consider the grey bar "middle" of http://www.nps.gov/maps/full.html?mapId=b32e4c79-caac-4266-9d6e-5b5cee8fa5d8 to be replaced by the much thicker middle div of the custom page.

@evilkermit
Copy link
Contributor

Migrated to this template with commit 52cf386. Here's the link for quick access: http://seelab.eecs.utk.edu/species_mapper/full/

Also, as an FYI, the CSS provided for that fullscreen template inherits the font rather than explicitly providing one. Because of this, I used the same font as the rest of our tool for the sake of consistency, which is why it will look slightly different than the link you provided.

I'm going to leave this issue open as it seems likely to me that I'll need to make minor changes once you all have a chance to test on your side.

@KendraStraub
Copy link

Status? @tpcolson - this can be closed, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants