-
Notifications
You must be signed in to change notification settings - Fork 0
Who Uses OneFeed
OneFeed isn't quite ready to use yet, but when it is, here's a rough outline of how you might identify as a user:
OneFeed's users are separated into two main categories, End Users and OneFeed Developers:
OneFeed's End Users are those concerned with hosting the app and consuming its output. End Users are defined as assuming one or both of the roles below:
Administrators provide OneFeed's functionality to Consumers. An administrator would be responsible for building a copy of OneFeed source code and hosting the app on a server for others' or their own utilization as Consumers.
Consumers utilize OneFeed's endpoints and consume its data. Consumers look like site or app developers hitting OneFeed's endpoints.
OneFeed Developers customize and extend the functionality of this OneFeed repository's source code to provide additional behaviors or features that other users benefit from.
As OneFeed is still actively in development and not yet completed, please do not take anything listed here as final (yet). As OneFeed inevitably changes, so will this wiki's content.
- Wiki Home
- What is OneFeed
- Who Uses OneFeed
- OneFeed's Development
- Symbol Key
- Glossary of Terms
- OneFeed for Consumers
- OneFeed and Your Application
- OneFeed's Default Endpoints
- OneFeed for Admins
- OneFeed for Your Clients
- Tailoring the Experience
- Configuring OneFeed
- Customizing OneFeed
- Add New Feeds
- OneFeed's Terms
- Appropriate Usage
- Assurances
- Assumed Risks
- OneFeed for Devs
- How OneFeed Works
- App Structure
- Data Handling
- Data Modeling
- Data Flows
- Standard Operations
- Handling Requests
- Retrieving Content
- Processing Content
- Content Mapping
- Text Formatting
- Loading Configurations
- Loading Customizations
- OneFeed's Development Principles
- Develop Customizations
- Default Extension Points
- How to Develop Content Sources