After working on the Discourse Notifier mobile app I realised, one killer feature for the app would be to improve discoverability. A shared index would help with this (and would also help when you know the forum but cant remember the URL).
MVP app would have:
a user facing form to register your site. The form would only have a URL field, and we would retrieve data automatically
a GET /sites API endpoint with a q params to filter results and probably some pagination logic
implement create/update api endpoints to allow some automation, like auto register/update your board to the Discourse Index
What do you think? Am I missing something and it’s already possible to achieve this?
I’m all about this. I’ve been wanting a more exhaustive overview of our many “partners” for quite some time. “What are some good example Discourse sites?” is also a very frequent question here in the community.
This is jumping ahead a little bit, but I just wanna clear up real quick:
Do you have some tech in mind already? Some sort of lightweight single-page application?
Just wanted to point out that at least the v1 of this sounded like something like Jekyll + jekyll-get could handle with ease, but
no I dont have any tech in mind, as I said in my first post my basic goal is to improve discourse notifier app by providing better discoverability and autocomplete, so I need one api endpoint to accomplsih this. Im not very familiar with jekyll, but with a server, a db and some programming language we can certainly accomplish this.
@erlend_sh I’m considering working on this to showcase some frontend work, would you want to mentor me on this? My only requirement would be “no ruby”, I have enough projects to showcase with ruby, and would like more projects in JS (whatever framework) or Elixir/Phoenix/Elm.
I’d love to help spec this out, but I’m not a programmer so I don’t think you’d want my guidance on that part I’m sure @sam or someone else from the team will be able to lend a hand on this though.
Let’s just make one thing clear right away:
We are now talking strictly about a web app, correct? I.e. a directory app that would live somewhere like directory.discourse.org.
Just need to make that clear, since I realised after my initial reply that your original post was actually about extending the Discourse Mobile App, and not the general purpose directory that I started talking about.
Incorporating a directory into the app would be great, but I think it makes sense to build this as a web app first, because:
@erlend_sh ok no problem if you are not a programmer, we can find someone else, or I can just start and improve with time But I do need you for the user facing part.
So my general idea is:
an API to improve discoverability in the DiscourseMobile notifier app
to have data for this API we need something to fill it, so yes probably some kind of form and as I said earlier, we could maybe have an API endpoint so people can directly opt-in from Discourse admin to appear in this index
and then I discovered that you wanted to display this data to users via the “discourse hub”
So as I see it, we need a frontend (sites listing, form, auth) and some backend with few api endpoints and a database to store the…data.
Concerning the backend, I said “no ruby”, but if it’s easier for you to host we can use ruby, I would advocate for elixir or node, as this is where I want to gain xp, but I’m open, and I would understand you would want to keep your stack simple.