You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2019. It is now read-only.
The about section on the new site has a bunch of sub-sections: What We've Made, Our Team, Blog, and Job Board. For launch, we can just link all of these to their existing destinations, i.e. ship.cc, the existing team page, the existing blog (or the new one on tumblr if that's ready), and the existing job board. All we'll have to do is update the nav on the squarespace site so that the user, when she goes to the pages on that site that we're still using, she isn't suddenly able to navigate to the squarespace pages that are outdated.
Post launch, of course, we'll want to clean all this up. But designing the about page, because of how much content it has, will be a project in itself. We'll either have to figure out a UI for making all that content work within the single page model, or (more likely) we'll have to design sub-pages, which will involve a new template and designing the navigation system for linking the homepage and the sub pages.
The text was updated successfully, but these errors were encountered:
Re "All we'll have to do is update the nav on the squarespace site so that the user, when she goes to the pages on that site that we're still using, isn't suddenly able to navigate to the squarespace pages that are outdated.": anyone want to take a stab at this? @AbhiAgarwal @Maltor124
Other than the squarespace stuff (which we'll have to tweak post launch, since I don't think Squarespace lets you set up changes in advance and then push them later), the about page is getting close for launch.
Post launch, we'll want to show the latest blog posts and job board posts inline.
The about section on the new site has a bunch of sub-sections: What We've Made, Our Team, Blog, and Job Board. For launch, we can just link all of these to their existing destinations, i.e. ship.cc, the existing team page, the existing blog (or the new one on tumblr if that's ready), and the existing job board. All we'll have to do is update the nav on the squarespace site so that the user, when she goes to the pages on that site that we're still using, she isn't suddenly able to navigate to the squarespace pages that are outdated.
Post launch, of course, we'll want to clean all this up. But designing the about page, because of how much content it has, will be a project in itself. We'll either have to figure out a UI for making all that content work within the single page model, or (more likely) we'll have to design sub-pages, which will involve a new template and designing the navigation system for linking the homepage and the sub pages.
The text was updated successfully, but these errors were encountered: