Programming

13384 readers

1 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

remington

alyaza

Hexorg

Helping those who come after me maintain a website. (lemmy.sdf.org)

submitted 1 year ago by JPAKx4@lemmy.sdf.org to c/programming

8 comments fedilink hide all child comments

Hello fellow programmers!

I have a website I am creating for a non-profit with multiple locations, and I want to know the best approach to take. The styling will be the same for all them, but the actual content should change depending on the location. I want to create the website in a way that is easy for someone who is not technical to update, even if it's only text, images, and links. Any thoughts would be helpful.

I would like to avoid libraries or frameworks, as I want a simple ftp server to reduce costs and complexity for everyone involved.

top 8 comments

sorted by: hot top controversial new old

[–] tumulus_scrolls@lemmy.fmhy.ml 8 points 1 year ago* (last edited 1 year ago) (1 children)

There's a case to be made, realistically speaking, that using a well-known framework or even a CMS like Wordpress means less complexity specific to your website to understand for the next person. FTP cough SFTP or Markdown/HTML is definitely not beyond non-technical people to understand and use, but sadly there could be some resistance nowadays I imagine.

I would look into static website generators. Sadly I'm not sure what is most reliable nowadays, but I would prioritize easy of use and installation, as speed is probably meaningless on your scale. Here's a random article.

[–] JPAKx4@lemmy.sdf.org 1 points 1 year ago

Sounds good, I'll look into it, and thank you for the article.

[–] Micah 7 points 1 year ago (1 children)

Have you worked with WordPress before? You could create a theme for the sites to maintain consistency, while letting the client have CMS access to edit the content.

[–] JPAKx4@lemmy.sdf.org 1 points 1 year ago

That'll probably be the best way to go, thank you.

[–] george@midwest.social 6 points 1 year ago (1 children)

Document document document.

Also, the nice thing about libraries, frameworks, and CMSs is that they already have documentation. If it seems like a pain to learn one of those, imagine how much worse it would be for someone to learn custom code that doesn’t have any resources on Google.

[–] JPAKx4@lemmy.sdf.org 2 points 1 year ago

Thanks for your response! I'll do my best, however the issue is I don't necessarily want someone to look over documentation just to edit a date on a webpage. I do understand what you mean though.

[–] kelvinjps 6 points 1 year ago (1 children)

maybe a static site generator and set up some CMS?

[–] Penguincoder 1 points 1 year ago

Problem is teaching non techies how to use that static site generator. Start talking about html or git and the eyes will glaze over. Definitely not sustainable.