Ciro Santilli (三西猴) OurBigBook.com sponsor me: cirosantilli.com/sponsor, opinions my own 2020冠状病毒审查 ,2020郝海东 ,2018新疆改造中心,1989六四事件,1999法轮功 ,2019 996.ICU, 2018包子露宪,2015 709大抓捕,2015巴拿马文件 邓家贵,2017低端人口,2008西藏骚乱<script>alert(1)</script>
                                            Ciro Santilli (三西猴) OurBigBook.com sponsor me: cirosantilli.com/sponsor, opinions my own 2020冠状病毒审查 ,2020郝海东 ,2018新疆改造中心,1989六四事件,1999法轮功 ,2019 996.ICU, 2018包子露宪,2015 709大抓捕,2015巴拿马文件 邓家贵,2017低端人口,2008西藏骚乱<script>alert(1)</script>
                                        
                                    If this is going to be done, there should be an API-based data generator in this repo I think. Faker is a well known ruby solution: https://github.com/faker-ruby/faker The Js port...
Another reasonable option would be to sort by last create or better, last applied to an article (current ordering appears undefined: https://github.com/gothinkster/realworld/issues/839 ) as that would lead to good experience...
I think tag list is just not specified in the spec as it should be. I assume they are just sorting alphabetically which is a reasonable choice if the tag...
Ah fantastic, if there's going to be a new CSS, that makes things simpler.
I also didn't mean to propose that we should enforce how implementations implement their CSS. My main recommendation is that we don't host a reference CSS file where it can...
We should not only remove `/#/` from the spec, but also have frontend test that check that they are not present: https://github.com/gothinkster/realworld/issues/269 We should encourage the URLs of all implementations...
Since you mentioned something related, will there be a reference implementation/has a stack been selected for it? My vote is for node.js express + react :-) (with [sequelize backend fingers...
Yes, that would not be a bad option I think. Notably for me my general concern is to make [the logged out website viewable without JavaScript](https://github.com/gothinkster/realworld/issues/691), so no problem with...
Yes... this might be the same as was mentioned at: https://github.com/gothinkster/conduit-bootstrap-template/issues/1 So broken. https://demo.productionready.io/main.css looking correct:  This repo at 0b45af7bb43c2a038f09215885ff4cdb87b47a9b all broken: ...
Yes, it seems that it is because this repo is out of sync with https://demo.productionready.io/main.css posted screenshots at: https://github.com/gothinkster/conduit-bootstrap-template/issues/5#issuecomment-829104220