|
1 | 1 | ---
|
2 | 2 | collapse: nav
|
3 | 3 | ---
|
4 |
| -# Community tools and services |
| 4 | +# Community tools and Services |
5 | 5 |
|
6 | 6 | !!! info "Obligatory disclaimer"
|
7 | 7 |
|
8 |
| - Please note that the table below contains a list of community projects and services that are not officially supported by CCP Games. We acknowledge the hard work and dedication of the developers who have created these services and give them a soapbox to promote their services. However, we do not endorse or guarantee the services listed below. If you have any questions or concerns about a service listed below, please contact the service creator directly. |
| 8 | + Please note that the tables below contains a list of projects that are not officially supported by CCP Games. We acknowledge the hard work and dedication of the developers who have created these projects and give them a soapbox to promote them. However, we do not endorse or guarantee the items listed below. If you have any questions or concerns about a service listed below, please contact the service creator directly. |
9 | 9 |
|
10 |
| -| Service Name | Creator | |
11 |
| -|-------------------------------------------------------------|----------------------------------------------------------------------------------------------| |
12 |
| -| [Abyss Tracker](./abyss-tracker/index.md) | [:octicons-mark-github-16: EVE Workbench Team](https://github.com/EVE-Workbench) | |
13 |
| -| [Alliance Auth](./alliance-auth/index.md) | [:simple-gitlab: Alliance Auth Team](https://gitlab.com/allianceauth/) | |
14 |
| -| [EVE Workbench](./eve-workbench/index.md) | [:octicons-mark-github-16: EVE Workbench Team](https://github.com/EVE-Workbench) | |
15 |
| -| [Innominate Appraisal](./innominate-appraisal/index.md) | [:octicons-mark-github-16: Mezoology](https://github.com/mezoology) | |
16 |
| -| [JitaSpace](./jitaspace/index.md) | [:octicons-mark-github-16: joaomlneto](https://github.com/joaomlneto) | |
17 |
| -| [RIFT Intel Fusion Tool](./rift-intel-fusion-tool/index.md) | [:octicons-mark-github-16: Nohus](https://github.com/nohus) | |
18 |
| -<!-- | [Sample Service](./sample-service/index.md) | [:octicons-mark-github-16: Developer McDeveloperface](https://github.com/@your-username-here) | --> |
| 10 | +{{ community_pages("service") }} |
19 | 11 |
|
20 |
| -# Libraries and resources |
| 12 | +# Libraries and Resources |
21 | 13 |
|
22 | 14 | These projects are intended for use as building blocks by other developers
|
23 | 15 |
|
24 |
| -| Name | Description | Creator | |
25 |
| -|------------------------------------------------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------| |
26 |
| -| [Django-ESI](./django-esi/index.md) | Django app for easy access to the EVE Swagger Interface (ESI) | [:simple-gitlab: Alliance Auth Team](https://gitlab.com/allianceauth/) | |
27 |
| -| [SDE REST API](./sde-rest-api/index.md) | REST API for the EVE Static Data Export (SDE) | [:octicons-mark-github-16: joaomlneto](https://github.com/joaomlneto) | |
28 |
| -<!-- | [Sample Tool](https://github.com/esi/esi-docs) | Crowd-sourced documentation | [:octicons-mark-github-16: Developer McDeveloperface](https://github.com/@your-username-here) | --> |
| 16 | +{{ community_pages("resource") }} |
29 | 17 |
|
30 |
| -# Submitting a Service |
| 18 | +# Submitting a Service or Resource |
31 | 19 |
|
32 |
| -If you would like to list your service here, please submit a pull request to this repository, adding your service to the table above, and creating a sub-page in this directory with more information about your service. Use the file in `src/docs/community/sample-service/` as a template. |
| 20 | +If you would like to list your service here, please submit a pull request to this repository, creating a sub-page in this directory with more information about your service. Use the file in `src/docs/community/sample-service/` as a template. The tables above will automatically update with the information you provide, assuming you follow the template. |
| 21 | + |
| 22 | +## Resources vs. Services |
| 23 | + |
| 24 | +The general rule of thumb is that if your project is something that a developer would use to build something else, it's a library or resource. If it's something that an end user would use directly, i.e. by installing it themselves, or through something already hosted, it's a tool or service. |
33 | 25 |
|
34 | 26 | ## Requirements
|
35 | 27 |
|
36 |
| -1. Your service must be directly related to EVE Online. |
37 |
| -2. Your service adheres to the [EVE Online Developer License Agreement](/license-agreement). |
38 |
| -3. Your service must be publicly accessible. :material-information-outline:{ title="No private services, please." } |
39 |
| -4. The creator of the service has an account in good standing. :material-information-outline:{ title="Yes, being banned counts as 'not in good standing'." } |
40 |
| -5. (Bonus) Your service is open source. :material-information-outline:{ title="This is not a requirement, but a nice-to-have." } |
| 28 | +1. Your service/resource must be directly related to EVE Online. |
| 29 | +2. Your service/resource adheres to the [EVE Online Developer License Agreement](/license-agreement). |
| 30 | +3. Your service/resource must be publicly accessible. :material-information-outline:{ title="No private services, please." } |
| 31 | +4. The creator of the service/resource has an account in good standing. :material-information-outline:{ title="Yes, being banned counts as 'not in good standing'." } |
| 32 | +5. Your service/resource is 'released', and not in an early alpha or beta state. :material-information-outline:{ title="We want to make sure that the service is stable and usable for the general EVE public. If you are working on a new project, drop by in discord, as there's bound to be other developers there that might be interested in what you're tinkering with." } |
| 33 | +6. (Bonus) Your service/resource is open source. :material-information-outline:{ title="This is not a requirement, but a nice-to-have." } |
41 | 34 |
|
42 | 35 | As always, we reserve the right to remove any service from this list at any time for any reason, or decline to add a service to this list.
|
43 | 36 |
|
44 | 37 | !!! note "A note about search"
|
45 | 38 |
|
46 | 39 | You might have noticed the search exclusion marker in the template file.
|
47 |
| - |
| 40 | + |
48 | 41 | This part is required.
|
49 | 42 |
|
50 | 43 | While we want to keep a list of community services, the primary function of this documentation site is to provide access to information about the EVE Online third-party development ecosystem.
|
51 | 44 | Adding community services to the search index would dilute the search results and make it harder for developers to find the information they need.
|
52 | 45 |
|
53 | 46 | If a service is deemed to be of particular interest to the community, one of the documentation maintainers may choose to remove this exclusion.
|
54 | 47 |
|
55 |
| -## Adding images to your service page |
| 48 | +## Adding images to your page |
56 | 49 |
|
57 | 50 | If you want to add images to your service page, be sure to add them to the same directory as your service page. Please keep the images small and optimized for the web, no larger than 250KB or 1024x768 pixels. Also try to limit the amount of images you use on a single page, preferably no more than 10 unless necessary.
|
58 |
| - |
59 |
| -# Submitting a tool or resource |
60 |
| - |
61 |
| -If you would like to list your tool or resource here, please submit a pull request to this repository, adding your tool or resource to the table above. Please keep the description of your tool or resource brief and to the point. If your tool or resource is big enough that you feel it needs its own page, this can be arranged, but please have a discussion about this on [discord](../support.md). |
62 |
| - |
63 |
| -## Tools vs. Services |
64 |
| - |
65 |
| -The general rule of thumb is that if your project is something that a developer would use to build something else, it's a tool or a resource. If it's something that an end user would use directly, i.e. by installing it themselves, or through something already hosted, it's a service. |
0 commit comments