Dashboard or Guidebook
Hello 👋
So i have this scenario, I'm building a website for a nonprofit, they have active events all over the year so they need to regularly update the website content. I'm not sure which way of updating the content should I provide them since I'm not familiar with Dashboards and the expected launch date is the beginning of the upcoming year.
I thought of giving them a separate file with blocks of HTML elements with Thier classes so the client can just put the text they wish or the photos they wish inside the HTML Tags, I'll give them instructions on how to do it. Same thing for the REST APIs.
I follow CUBE CSS methodology and i only use Vanilla CSS/JS/HTML, No frameworks or libraries except jQuery.
And I use Flask and python for backend.
So the question is, what should I do? guide or spend time on learning Dashboards? Are they easy to learn?
5 Replies
Also sorry if it's in the wrong channel, i wasn't sure where to post 😅
Step 0: Make sure you can deliver on such a short timeline
Step 1: Ditch jQuery. It's unnecessary. What once made jQuery great is now part of vanilla JS.
Step 2: Use a CMS. Don't trust non-devs (hell, even devs sometimes) with raw HTML. It's just asking for trouble
Step 3: Make sure you have everything written down i in your statement of work for the contract both parties signed
I only use jQuery when I'm lazy to deal with DOMs lol
There's no contract it's voluntarily, I'm doing the website for free for them. And yeah it can postpone a but I plan to finish it on time.
I'm not familiar with CMS what do you suggest to use?
jQuery downloads and runs unneeded JS that is part of what the browsers supply for free. So please, for your user's sake, don't use jQuery. Byte for byte JS is the most expensive part of of any website, so each byte of JS the end user must download (and jQ isn't exactly small) is pushing a lot on them, their machine, and their internet connection.
Also, get a contract. It doesn't matter if you're doing it pro bono or getting paid. A contract lets every party know what is expected of them and there's not gonna be scope creep or a case of, "he said, she said, they said". It's in the contract. Everyone knows exactly what is expected and when. Not wanting to use a contract—especially on something "simple" like this (pro tip, it's never "simple")—is a red flag. If they're not willing to write down what they want they either want to push you for more or they don't know what they want. Either is a bad place to be.
As for CMS, since you're using Flask/Python you'll have to do some research on what CMSs are available on that stack, I'm not familiar with Python at all
I'll try to avoid jQuery then 😅
For the contract I agree with you, I also don't like to work without writing down everything. I guess it's because I know the Founder we didn't discussed it. 😅
I'll do one tomorrow 👌
For the CMS, ok I'll try to search 👌
Thanks for the answer and advice, appreciate it 🙌