Thanks for reporting. I think we should improve this reporting experience in the future. There are several repos that are the source of this website, like: https://github.com/apache/echarts-www https://github.com/apache/echarts-doc https://github.com/apache/echarts-handbook https://github.com/apache/echarts-examples and more. So it may take some time for us to ensure every page has such reporting hints.
Thanks *Ovilia* On Wed, Aug 6, 2025 at 7:39 PM sebb <seb...@gmail.com> wrote: > On Wed, 6 Aug 2025 at 11:40, Ovilia <oviliazh...@gmail.com> wrote: > > > > Thanks Sebb, > > > > What issue would you like to report? Mailing list is a good place to > report. > > This very issue: it's not obvious how to report issues with the website. > If the mailing list is the best place, it should say so, and provide > some guidance as to what info to provide. > > > Since the website has several repos to combine with, it may not be easy > to support such a feature for all web pages. > > In which case, direct people to the main website repo (once issues > have been enabled), and ensure the issue template asks for the > original page location. > > > We do have "Edit this page on GitHub" for handbook pages like > https://echarts.apache.org/handbook/en/get-started/ > > That does point to the source page, but does not offer an option to > report an issue. > It may not be appropriate to create a PR for an issue, or the reporter > may not wish to clone the repo. > Or the issue may relate to multiple pages, which would be a lot of > work for the reporter. > Or the problem may be present on the page, but be derived from somewhere > else. > > For example, the getting started page has a heading "In This Page". > That does not read well in English; it should be "On this page". > The heading does not appear in the source for the page, so how is > someone supposed to report that? > > > > > Thanks > > > > Ovilia > > > > > > On Wed, Aug 6, 2025 at 4:13 PM sebb <seb...@gmail.com> wrote: > >> > >> It's not easy reporting issues with the ECharts website. > >> > >> The website repo does not have an issues tab, and the code repo > >> templates are not designed for use when reporting website issues, as > >> they include a lot of irrelevant information (and probably omit some > >> relevant data, such as browser details) > >> > >> It would be a great help if issues were enabled on the GH website > >> repo, and a link to the repo could be added to the website. > >> Some website builders can even generate a link to the source file for > each page. > >> See for example the footer of the following page, which links to the > >> repo and the source file within it: > >> https://community.apache.org/about/ > >> But even a link to the website repo would help. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > >> For additional commands, e-mail: dev-h...@echarts.apache.org > >> >
