(Pro tips can still come from non-pros, right? 👀)

I only started doing this recently, but it’s a lot better for my stress levels 😂

I change the title to DEV ONLY so I know how safe it is to edit the functionality etc. I also have a banner in the HTML that shows if I’m not actually editing the original “real” version, which also reassures me.

Then I can break stuff, save to my hearts content (I have an itchy save-finger). And only copy it across to the real version when I’m happy it’s safe. Just remember not to overwrite the $meta stuff if that’s different in your dev copy. Though if you accidentally do that, the backups are very useful for quickly grabbing what you need to put back.

For the name, I call it the same, but with -dev- in there somewhere, and -4958734957 a load of random numbers at the end so it’s super unlikely people could stumble across it.

  • Cocell@lemmy.worldEnglish
    2·
    2 months ago

    I am planning on removing the canvas too.

    About the app stages, could you explain what you mean by alpha? Because, from semantic versioning perspective, alpha refers to a stage of a software that is still in development.

    And about managing multiple stages, I am thinking hosting them in GitHub or in my local machine, and then manage multiple versions of them there directly, I have been slowly getting into it.

    • BluePowerEnglish
      2·
      2 months ago

      I used this term alpha to define the version as an “under maintenance” version of the Preview builds. It’s basically a more private-ish version of the Preview versions, where I save the code to a place where the features are left unfinished (directly on Perchance). This could save some time as I don’t need to constantly copy and paste the generator’s code into a text file and paste them back once I want to continue working, and also to reduce the accidental saving events that happen uncommonly. And with that, I could also plan more efficiently too.