- removed version
Atlasboard extension points
Does Atlasboard have a roadmap of any kind - and does it include better support for extendability? Having latest commits in August 2014 the project may look somewhat stalled.
When starting to build something on top of Atlasboard, the issue for not having a clear extension points in Atlasboard quickly rises. For example, it should be possible to do for example following (without forking the project):
- Add custom middleware (authentication, error handling)
- Add custom loggers (error tracking)
- Introduce static resources (img, font etc.) in widgets/packages
- Add custom storage backends
- Communicate from jobs to Atlasboard instance, for example via events
Having extendability would help the project keep evolving
Comments (6)
-
reporter -
Hi Juha,
The project is moving slower but it has not stopped at all. Currently we are implementing custom themes.
Indeed better extension points (a better way to include static resources is one of the hot ones) would improve Atlasboard considerably.
Thanks for raising them. We will definitely have them in mind. Also, feel free to send PR this way with any improvements you feel to add in that direction.
-
reporter Hi,
Thanks for the response. I'll ensure the reusable code from our development will get published back to project / as extensions. And I honestly believe the better extendability of the platform, the more contribution you'll get.
-
- changed component to Extensibility
-
1.0 is coming up with a few improvements and extension points for routes, support for themes, richer configuration options, etc..
Feel free to checkout the pre-1.0.release branch and submit feedback! https://bitbucket.org/atlassian/atlasboard/src/9708e0c69b616619baef85444851f40adaa66d1f/README.md?at=pre-1.0-release
-
Account Deactivated - changed status to resolved
- Log in to comment
Removed the version 0.5.0 info (after all, the current version is 0.8.0 but cannot be found from version options)