| .. | ||
| _layouts | ||
| assets | ||
| _config.yml | ||
| analytics.md | ||
| ci.md | ||
| content-security-policy.md | ||
| customization-checklist.md | ||
| customization-guide.md | ||
| deploying-to-production.md | ||
| env.md | ||
| extend-listing.md | ||
| extended-data.md | ||
| folder-structure.md | ||
| google-maps.md | ||
| icons.md | ||
| improving-performance.md | ||
| map-providers.md | ||
| README.md | ||
| redux.md | ||
| routing.md | ||
| search-filters.md | ||
| sentry.md | ||
| static-pages.md | ||
| styling.md | ||
| terms-of-service-and-privacy-policy.md | ||
| testing.md | ||
| translations.md | ||
Flex Template for Web: Documentation
Why Saunatime?
Short answer: Demonstrate the features of Flex with a marketplace for renting saunas. Because why not.
Long answer: Saunatime works as a template for a marketplace user interface. It can be used as a marketplace client out of the box but is intended to be modified to match the requirements of each marketplace built on top of the Flex API. Also, marketplaces that do not use Saunatime as a template for building a client can use this template application as a reference on how the Flex API can be used in a browser environment using the JavaScript SDK.
Marketplace features included in Saunatime:
- Location search shows the user if there are saunas available in a given location.
- The listing page gives a detailed view about what a particular sauna offers.
- Transaction process: Saunatime uses nightly booking.
- Notifications: Emails are sent during the booking process to alert customers and providers about changes in the booking state.
- Inbox lists orders and sales.
- Reviews can be given after a completed transaction.
- User profiles provide detailed information about a given user.
- Extended data: The listing and user data models are modified using extended data.
How to customize this template
The easiest way to start a customization project is to read through the customization guide. After that, you probably should start with changing translations, common styles in marketplace.css, and then create static pages and modify Terms of Service and Privacy Policy pages.
Documentation for specific topics can be found in the following files:
- Customization guide
- Folder structure
- Integration to map providers
- Translations
- Styling a marketplace
- Static pages
- Terms of Service and Privacy Policy
- Routing
- Redux and duck files
- Extended data
- Extend the listing data model
- Search filters
- Testing
- Error logging with Sentry
- Analytics
- Continuous Integration (CI)
- Content Security Policy (CSP)
- Original create-react-app documentation
- Customization checklist
- Icons
- Improving performance
- Deploying to production
The application was bootstrapped with a forked version of create-react-app. While most of the original documentation still applies, there are some important differences listed in the sharetribe-scripts NPM package.