New Tobin Paradigm wrote: ↑2020-10-02, 11:53It may help to start small.. You can't just jump in and go crazy.
Well, you can, if you're also crazy...
Steven Pusser's build is for distribution through a repository so that it can be updated with the system's package manager. Travis' build does not integrate with the package manager and instead uses Pale Moon's own updater. Otherwise the two builds are equivalent.
For add-on development and testing I usually make a new profile, which you can do with the profile manager (run palemoon --no-remote --profilemanager from the terminal). That way you don't risk damage to your current profile.Drugwash wrote: ↑2020-10-02, 11:42Should we download and install an alpha to work with? Would that affect the current profile? Is there a portable alpha that would use its own profile?
Where should we look for errors? What kind of errors should be targeted first? Are there any page templates for testing purposes? Are there any specific tools to use?
There's a lot of scattered documentation and resources out there. The only tools you really need are a text editor and a zip tool. For hunting down errors, the browser console is likely the best place, but it will also display webpage errors (which can be quite numerous), so you kinda have to know what you're looking for.