• Introduction
• Setup
• Overview
• 1. Install the CLI
• 2. Create the App
• 3. Run the App
• 4. Setup the API
• Layout
• Overview
• 1. Install Bootstrap
• 2. Add Custom Styles
• 3. Add the Header
• Routing
• Overview
• 1. Convert Title to a Link
• 2. Add Feed to Routes
• Data Structure
• Overview
• 1. Add Mock Data to Feed
• 2. Create Tweet Component
• 3. Add Mock User Data
• Fetching Data
• Overview
• 1. Set API Location
• 2. Create Tweet Model
• Convention over Configuration
• 3. Connect Feed Component
• 4. Display Loading Message
• 5. Fetch User for Tweet
• Authentication
• Overview
• 1. Add Profile to Layout
• 2. Add Auth0 Config
• 3. Add Login Page
• 4. Redirect to Login
• 5. Add Callback Route
• 6. Add Logout Page
• 7. Fetch Current User
• 8. Save User to Context
• Server
• Overview
• 1. Clone the API Server
• 2. Parse the Collection
• 3. Parse the Model
• 4. Add Unauthorized Experience
• 5. Add Authorization Header
• Pagination
• Overview
• 1. Add Pagination Metadata
• 2. Paginate the Tweets
• 3. Add Pagination Links
• 4. Improve User Experience
• Infinite Scrolling
• Overview
• 1. Create Load More Button
• 2. Create Infinite Scrolling List
• 3. Convert the Feed
• Cleanup
• Overview
• 1. Remove Unnecessary Code
• Dialogs
• Overview
• 1. Add Create Button
• 2. Mounting Dialogs
• 3. Add Create Dialog
• 4. Simplify the Dialog
• 5. Generate Dialog via Hook
• 6. Add Edit Dialog
• 7. Add Delete Dialog
• Authorization
• Overview
• 1. Hide Edit Link
• 2. Hide Delete Link
• 3. Alternative Approach
• Optimistic Updates
• Overview
• 1. Freeze Pagination Data
• 2. Display New Tweets
• 3. Display Optimistic Tweets
• 4. Add Optimistic Values
• 5. Show Optimistic Visual Cues
• 6. Hide Deleted Tweets
• Normalization
• Overview
• 1. Normalize Tweet Response
• Filtering
• Overview
• 1. Add Filter
• 2. Display User Tweets
• WebSockets
• Overview
• 1. Add WebSocket Support
• 2. Send Client ID to API
• Publishing
• Overview
• 1. Create Production Build
• 2. Deploy to Production
• 3. Create Production Config
• 2. Redeploy to Production
• Next Steps
• Overview
• Misc
• Installing Node
• Completed Project

Next Steps

Congratulations! You've reached the end of the Quickstart.

At this point, you've now been exposed to most of the core features and functionality of Lore. If you enjoyed building the Quickstart, you're encouraged to try building your own application with Lore.

If you choose to do that, you may find yourself wanting a to gain better understanding of how Lore works and how to extend the framework to customize it's behavior. If that's the case, the documentation below will help you gain that understanding:

• If you'd like to develop a better understanding of how Redux works, you can find some recommended resources for learning it here.
• If you'd like to learn how to create your own hooks, in order to add custom behavior to your application, you can learn how to do that by following the custom hook tutorial.
• The Quickstart was able to rely on the built-in actions and reducers, but you may find yourself in a situation where you need to modify their behavior. In that case, you learn how to extract the built-in actions or extract the built-in reducers, so that you can see how they work and modify their behavior.
• You can learn more about creating custom actions here (todo), which can be useful if you need to create actions that don't map to a REST API endpoint.
• You can learn more about creating custom reducers here (todo), which can be useful if you need to store application state that doesn't map to a REST API endpoint.
• You can learn more about how the connect decorator works here, as well as how to extend it's behavior with new blueprints.

That's it! Thanks for investing your time to learn a little more about Lore, and we hope you learned something valuable along the way.

Questions & Issues

If you have any questions, issues, features requests, ideas to improve the user experience, or just want additional thoughts about how to solve a front-end challenge with Lore, don't hesitate to submit an issue with your thoughts!

Documentation is challenging to create, due to the diverse perspectives and knowledge of the people reading it. But if you're confused or struggling to understand something, you're probably not alone, so please don't hesitate to file an issue.