third party extension doc(v0.1)

[technophile-04]

Description:

Tried writing very basic doc for creating third party extension with phase 1 & 2. Lol I think it could way better / improved.

[rin-st]

Thanks Shiv, good starting point! Added some small comments

Also, I think pr should be into developer-extension-v0.2 since yarn create-extension is not in the main branch yet

[carletex]

This is a great start, thank you @technophile-04 !!

Left some comments.. .mosty about context (sorry, I think I said that word a lot haha)

[technophile-04]

Tysm all for great feedback!! Update with suggested not sure if its on point, but please feel free to suggest change / push tweaks!!

[MattPereira]

This is REALLY DOPE idea ya'll are working on here!!! 👾 ❤️ 👾

The DX may be a little harder but you gain EZ mode for keeping a build up to date with the latest version of scaffold 🤯

I think the biggest hurdle will be getting devs to understand the caveats for what is or is not allowed

Obviously I don't understand all the nuances of whats possible or should be allowed , but I kinda wish there was a way to just overwrite some of the base instance files completely to allow for control of stuff like the order of navbar links and running fully customized versions of the home page, tailwind.config.js, and the footer component w/o the price fetching overhead

However, THIS IS STILL ABSOLUTELY AMAZING 💪 🚀 🌕

[technophile-04]

Thanks Matt for the review!! Yes the best thing about extension is that you always get up-to-date version of SE-2 for any extension(since people are not allowed to change base things)

I think the biggest hurdle will be getting devs to understand the caveats for what is or is not allowed

yes 100%, we are still figuring out what are the best way to tackle it. #73 logs this nicely while developing the extension but we could also refine this document more with further iterations/feedback

Obviously I don't understand all the nuances of whats possible or should be allowed , but I kinda wish there was a way to just overwrite some of the base instance files completely to allow for control of stuff like the order of navbar links and running fully customized versions of the home page, tailwind.config.js, and the footer component w/o the price fetching overhead

Yup I get you, but allowing people to override base instance files will again led to extension creators needing to keep their version up to date + we don't know if they unintentionally change something which breaks the resultant "instance" completely and hard to debug. But yup completely get you and maybe allowing certain files makes sense, somethings we need to discuss/refine as we get more and more feedback.

[rin-st]

I've run it through a spell checker and it found some (very minor) additional typos. Please recheck if everything is right. e098210

Other than that, lgtm! Great job!

[carletex]

I think this is a good merge. We can tinker as we go.

I'd personally clarify that all of this workflow might not be needed at all (if you are doing something simple) to avoid scaring builders haha More in this comment

But let's also see how it feels for other people.

[technophile-04]

Thanks all !! Merging this for now, but also created #87 (which I think we should tackle before being loud with general people and opening it for all)