[FEATURE] Refactor Site Management

[aDreamEater]

I would like some mechanism to automatically group all sites of a certain URL format in a specific category, possibly based on merge-site rules, or by adding a similar menu.

For example, automatically placing all websites that match the string

*.fandom.com

in a website category that I've created, named "Wiki".

This categorization should be modifiable in the [Site Management] and [Record] menus, if specific entries for whatever reason shouldn't match that category, but by default it would now place all discrete urls that match the string into that category.

[sheepzh]

Hi, @aDreamEater, thanks for your submission.

I know you. Compared with automatic categorization, I think the best approach would probably be to have [Site Management] support for searching sites using regular expressions (like *.fandom.com) instead of just exact URLs. Then you could select all sites to change their category. This will not overcomplicate the system while still meeting your requirements.

[aDreamEater]

It's more that I can be confident that any site from the example "fandom.com" URL belongs in my 'wiki' category due to the nature of the website's content (it is a wiki aggregate). But there are so many potential subdomains that it would be better to be able to have the subdomains automatically categorized according to the base URL, rather than occasionally going into the settings to manually bulk categorize them.

Searching .fandom.com already works, and doesn't seem to have a significant difference from searching *.fandom.com, so your suggested change is largely unnecessary for my purposes.

The reason why I suggested what I did is because I noticed that some sites only show up in the [Site Management] menu after I manually edit them in the [Record] menu, whether that is from changing the [Site Name] or from changing the [Site Category]. (Sorted in 10 entries per page and merged by date, I currently have 119 pages in Site Management, and 265 in Record).
I don't know if this is a bug, or if it is an intended behavior, or how difficult or unlikely it would be to change, so I tailored my initial suggestion to work around it.

Since the [Record] menu seems to lack bulk editing (other than batch delete), and my only need for editing the sites was categorizing subdomains, and the subdomains weren't appearing in the [Site Management] menu until they had already been edited, categorizing certain newly visited subdomains to automatically match the parent domain's category seemed the most useful thing to request.

Since that doesn't seem likely, second best would probably be to request an option to batch change categories in the [Record] menu.

[sheepzh]

Now [Site Management] only displays those sites with icons or names. When you visit a website for the first time, this extension automatically detects the name and icon. For websites that are not detected, you need to add them manually. This is a legacy issue.

I think maybe it can also categorize them at the same time according to custom rules. So now I strongly prefer to refactor the whole site management function, which will do exactly what you want.

This is certainly a big change, and it won’t happen quickly. Thank you again~

I will track the progress in this issue. Here are the subtasks (continuously modified

• Show all the websites on [Site Management], and optimize the space of storing site info.
• Support managing automatic categorization rules ( may be refactored with [Merge-site Rules]
• Automatically categorize sites when firstly visiting
• Change the label of option to collect site names automatically

[aDreamEater]

Oops, sounds like a big job. Good luck!

Something new I just noticed when testing adding names manually (I tried the useful automatically complete site names in batches tool first) is that editing an existing site name in [Site Management] doesn't seem to work right now.

Adding a site name of my own designation to one without does work, but if I go to change a name that exists or I added, it doesn't change from whatever it was initially set as. (It at first seemed to work when done in [Record], but on refresh it reverts to the initial name).

Normally I would put this as a separate bug, but since this issue is now about changes to Site Management, I thought It'd be on topic to put it here first.

Thanks!

[sheepzh]

@aDreamEater Thanks for your feedback, I created one new issue to track this problem

#426

I will fix it ASAP