Closed rcheetham closed 4 months ago
AFAICT from my grep this is only septa datasets and one "Bike Network - Supporting Datasets"
Supporting in-line HTML in markdown is more complicated and I think this should just be removed/modified to be markdown.
My understanding for how these markdown files are created, is that they were created from the import process from CKAN. Going forward, a new dataset markdown file would be created manually. Is this understanding correct?
Yes manually (or technically using Decap CMS but that's not easily setup here at the moment).
For this case though it would be manually updating the existing files to remove the html tags and replace with markdown if possible. Note although generic I believe this mostly affects Septa so this is related to #66
@BryanQuigley I think this might be partially fixed. I did a lot of editing on SEPTA this weekend and some HTML tags seem to be rendering ok. I also checked the referenced "Bike Network" data set and it seems to be fine.
But some tags still don't render. is an example.
< /br > above. Yes it seems to be mostly fixed but seems to be a strick subset of tags, but that seems fine.
There are HTML tags (and possibly some markdown) in dataset descriptions. These are being display as HTML, rather than interpreted.
I don't know if we should treat this as a bug or find a way to strip out all of the tags and replace them with line breaks. Some examples in search results and on a data set page below: