ind event page, navigation, staging #28
Merged
Conversation
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
=> going to use wagtailmenus for the navbar/footer management
=> scrapped wagtailmenus because it didn't seem to have good multilingual support => edited via the home page, reflects on all pages; editing the navigation in another language's home page will reflect for that language's global navigation => still pending: upper header items showing in the tablet/mobile view navbar
=> still need aws login in order to get media functioning => also did minor changes to some styling things
=> when wagtail is started with production settings, it'll try to use an aws bucket for the images => pattern-library added (originally tried to use django-storybook which uses pattern-library as a dependency, but it seems to no longer function; pattern-library may function as a storybook alternative however)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
=> individual event page is pretty straightforward
==> currently the "more events" are selected by the user, but if need be, this can be changed to just be 2 latest events, or changed so that if the events are already over, the event will be hidden
=> navigation is managed through the home page
==> nav items can have children as well as grandchildren
==> base-level nav items can be selected to "show in footer", which will make them (and their children, but not grandchildren) appear in the footer
=> staging is now ready!! getting the fly.io to work properly took a good bit but we're finally here...
==> when in production, images are handled via an s3 bucket (.env.example adjusted accordingly)
==> will need to set up a branch for automatic fly.io deployment at some point with github actions; manual for now