-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text on Event page should be well formatted #83
Comments
Well, for one, we need better content. And please elaborate on what you don't like about the format @manrajgrover |
@Slayslot It clearly is an ordered list but is showing it in paragraph form. |
@manrajgrover As I thought, it's because that's the way it has been entered in the database. |
I'm going to keep this open just so someone else doesn't open something similar. I'll close it when it's fixed for MozStar. People, this is not a front-end issue. Refrain from commenting here unless you have something useful. |
This is not a backend related bug. Shall be fixed in front-end only. Correct me if I'm wrong. Also if anyone is interested in taking this up, please go ahead. |
@CuriousLearner Formatting this on frontend is not productive when it can be sent in the correct format from the backend and displayed accordingly on the frontend. |
Hi! |
Hi @Anshika-G So, in this particular bug, as you can see from the first comment by Manraj: http://mozpacers.org/#event7 The description of this, and several other events, when have an ordered list or any other kind of formatting, they should be handled and shown as such. May be you can look at how the editors display it. The backend currently sends JSON response which is served over a REST API. We need to think of a way, may be integrating markdown or something so that the issue can be handled and description is well formatted as it was intended to be shown. What in your opinion would be suited here? |
I think we need to change front end formatting |
Currently text on Event pages are not formatted. For example, see this. This needs to be fixed.
The text was updated successfully, but these errors were encountered: