Skip to content
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

Can we add an Options page to the content-react template? #224

Open
takanuva15 opened this issue Nov 20, 2024 · 4 comments
Open

Can we add an Options page to the content-react template? #224

takanuva15 opened this issue Nov 20, 2024 · 4 comments

Comments

@takanuva15
Copy link
Collaborator

Hi, can we add an options page to the content-react template? That will help speed up development since many extensions have options they want to allow users to toggle.

Worst case, the dev can simply remove it, but at least it'd be there by default for all users.

(I know there are other content templates besides react, but react is the most popular so tackling that first would be a great first step)

@cezaraugusto
Copy link
Member

hey @takanuva15if you're feeling adventurous feel free to create a content-react-options template based on content-react and I'll happily add it to the templates list. for all else, let's keep them very simple

@dandv
Copy link

dandv commented Dec 20, 2024

I'm trying to port a Svelte extension from a boilerplate that comes with all pages by default (New Tab, Side panel etc.).

Worst case, the dev can simply remove it, but at least it'd be there by default for all users.

I'd also support creating "kitchen-sink" templates for React and Svelte, with explanations of how to remove components. Easier to get started that way, than figuring out how to properly wire up background workers, content script injection etc.

@takanuva15
Copy link
Collaborator Author

And as a bonus, having a single react template (that people can remove features from) would also eliminate thousands of lines of duplicate code that would inevitably occur if there were instead multiple separate react templates for every major feature of a chrome extension

@cezaraugusto
Copy link
Member

hey folks, thanks for the feedback. I think the comments here make a lot of sense.

if having a more complete example is best, let's do it. such starter templates need to have at least a content_script and an HTML entrypoint (popup, sidebar, newtab, etc) that includes a JS and CSS file.

I'm currently focusing on cross-browser compatibility so a new template from me is unlikely for the next few months, but I would love to see the idea taking shape and more than happy to review such work. we can just call these kitchen-sink templates by their framework name so extension create my-extension --template=react or extension create my-extension --template=svelte.

let me know your thoughts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants