This is my first time writing a post, and although I feel bad that my first ever post is a request, I hope that this request is something that other people could relate!
If I am not wrong, the current Ads extension does not have a feature where the host could present different advertisement for different pages / tags, meaning that single advertisement will be present every single pages within Flarum
This scheme is useful when the host is applying Google ad, etc, but not quite effective in providing more personalized advertisement scheme / or job positing.
Recently, I bumped into @Justoverclock 's new extension Job cards, and it occurred to me that it would be nice to have an advertisement scheme applied on various job positing websites.
This is how it works
1. Every job listings are randomly, or manually listed
the reason that job listings are randomly organized is to provide equal chance of being exposed to users.
For instance, if there are 10 job postings, or advertisements
every job postings and advertisements get equal 10% to get placed at the top / front page of the postings.
Of course, this is just an example, and the probability could be manually determined.
For an example - consider the link below
take a look at this Korean website -
various service providers get equal chance to be placed at the top, and every single time when the website is refreshed, the new random listing is created - providing equal chance for advertisers to be exposed to users.
Some website apply manual listing, or list by the latest order. I believe this feature could be of help for many Host using Flarum
2. customizable advertisement and job positing according to 'tags'
I believe this is very important for the new job positing scheme.
Flarum provide various tags and sub tags for the parent tag, and I believe having job positing scheme where the host could manually set the listing according to the tags would be useful.
consider this scenario.
if there are mother tags called 'basketball' and 'soccer', and each of the tags has sub tags 'Ottawa' and 'Quebec' which represent Canada's provinces.
We can list Quebec based basketball team advertisement on 'Basketball' - 'Quebec' tags and
we can list Ottawa based soccer coach job listing on "Soccer' - 'Ottawa' tags.
this listing too should be able to be randomly listed, or manually listed
**3. UI, Horizontal job positing model - and on/ off for homepage **
Many job positing website shows vertical job listing, but to maximize the benefit of Flarum's current UI, I think it is best to provide horizontal job posting, above the discussion filter bar, and below the navigation bar, showing list or job positing advertisement that could be slided would be awesome.
consider the following: https://ca.finance.yahoo.com/
on yahoo finance, below the navigation bar, Index are listed horizontally and I think we could apply similar UI on Flarum.
Also, I thought that applying job posting, and advertisement on homepage could be a bit messy, so I think it would be nice to have on/off feature for homepage.
**4. administration **
In administration, as mentioned above, having the section to manage the order of the list ( either random, or manual probability, or newest / oldest, or entirely manual ) and where this list are going to be placed (homepage and discussion, or only discussion or homepage, or between posts. most importantly, which tag sections! will be crucial.
Also, I think it would be amazing to provide preview for advertisers
Admin could grant right to advertiser, or specific group to access preview section -
with access to the preview section, they can choose advertisement scheme, either post type of advertisement or profile type of advertisement, which is already exemplified on Korean website I have shown you guys.
they can see the preview of their advertisement and could choose which tag they want to promote on - and finally decide to post them. Their advertisement will be listed accroding to the Host/ Admin's setting.
I know this feature could be little tricky as it has lot to do with backend / so if it's too time consuming, I think we could work on it without having this feature.