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

Reformat Homepage and creating place holder landing pages #4839

Merged
merged 3 commits into from
Mar 16, 2022

Conversation

ladoramkershner
Copy link
Contributor

Reformat Homepage and creating place holder landing pages

Description

I have created a new homepage structure and created user targeted "Getting Started", "Learn More", "Explore in Detail", and "Get Inspired" landing pages. In this initial commit the latter three landing pages are just replicates of the "Getting Started" landing. That is intentional, to make my structure and naming convention transparent to the team, following commits will update the replicated landing pages.

Related Issue

No related issues.

Motivation and Context

In accordance to ASC's documentation IAA with NASA we are implementing a new documentation structure that is more intuitive for new users.

How Has This Been Tested?

Documents have been built locally and all new links were tested.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation change (update to the documentation; no code change)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have read and agree to abide by the Code of Conduct
  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have added myself to the .zenodo.json document.
  • I have added any user impacting changes to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

  • I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

@jessemapel jessemapel merged commit 25e25be into DOI-USGS:dev Mar 16, 2022
@ladoramkershner ladoramkershner deleted the doc_restruct branch March 16, 2022 18:48
jessemapel pushed a commit to jessemapel/ISIS3 that referenced this pull request Apr 14, 2022
)

* Reformat Homepage; place holder landing pages

* Updating landing pages

* updating landing pages and BuildDocs.cmake
jessemapel pushed a commit that referenced this pull request Apr 14, 2022
* Reformat Homepage; place holder landing pages

* Updating landing pages

* updating landing pages and BuildDocs.cmake
@jessemapel jessemapel mentioned this pull request Apr 14, 2022
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants