We are a startup of 140+ employees, building a decentralized network of food distribution communities, each community is managed by a Host. We have around 1000 in Europe. We want the Hosts, the Farmers, and the Members to collaborate online.
After a year of internal testing, La Ruche qui dit Oui ! (The Food Assembly in UK) is ready to bring our network on our Discourse.
What would you like done?
We need a fullstack dev to implement a bidimensional navigation feature.
Donāt be afraid, Iāll explain :
we want a plugin
GPL2 is fine
enabling the creation of custom tables
either in content or a new kind of pages
the table creator configures one tag per column, on tag per line
the table is published
the table cells contain a list of all the topics which have both tags (column & line)
Alright, an example:
I create a table, declaring the tags āTODOā āDOā āDONEā as 3 columns.
declaring the tags āDESIGNā, āCODEā, āDEPLOYā as 3 lines.
I publish my table
I get something looking like
the table would be sexy, with hover on links, icons, etc.
I like this because it is very very quirky and different
Overall, once we have table support this should be fairly straightforward except that keeping the data in the table āfreshā is going to be tricky especially if it is embedded in a post.
How āfreshā do you need the data to be?
Always up to date?
Can be up to 1 day old?
Somewhere inbetween?
Also, security is a concern, what if some āDesign/TODOā topics are in a private category?
Daily make sense for us (we want to use it to organize a knowledge base, an lag of 12h average wonāt hurt much).
The above Kanban example, which is not our primary use, would be nice to have real-time.
But itās probably better to start simple (daily), and iterate to speed up refreshing.
I am not confident enough on our needs to give a precise answer, sorry.
In a perfect world, each user can only see topics he/she can access, obviously. But Iām pretty sure the code complexity will be overwhelming for a first iteration.
In the real & ugly world, we donāt really care some users can see a topic link/titleā¦ they wonāt be able to access the content anyway. And we say it is the author responsibility to build a table users can browse.
In a quick & smart world, we could do : the table only index posts of its own category. That seems fairly easy to achieve, and solves all security concerns. But degrades the feature quite drastically.
Itās an open question, but as the feature is supposed to ease the organisation/navigation between posts, it could be seen as counter-intuitive to put it within a post. Maybe it should be looked at like a new kind of topic listing pageā¦
@sam I was really happy to get your approval on this job and thought to get many candidates. I had a couple only. Is it expected on this category ? Or is there an issue with my proposal ?
Thanks for your advise
Just one or two freelancers getting in touch sounds quite normal. The Discourse ecosystem is growing steadily, but thereās not yet any independent developers whoāre making a living off of doing Discourse work 5 days a week. Iād say thereās about 20 regular devs around who could do this kind of job, but their times of availability vary greatly.
