#html coding structure

[zvaigzdelasas]

There's probably a viable pathway into career software development by starting as a QA tester - especially if you demonstrate basic proficiency w like python or javascript (node)

[crowcoding]

HTML & CSS Comment Tips

One valuable thing I have learned when starting any project is to include comments on your pages to provide a more structured layout.

For example, in HTML files, comments can be made with <!-- --->; anything within that space won’t appear on the page or be read by the browser.

A good way to use this in a page is to outline your areas, like in the image below.

Anywhere on your pages where you have a new section, you should use comments to outline what they are. This helps in a few ways. First, it increases readability for yourself and anyone else reading your code. Second, as your projects grow, doing this helps keep them organized. 

It’s easier to add to and edit when you can find the area where you want to make changes or add classes based on the comment tags rather than trying to narrow it down through many <div> tags. Third, it helps with remembering what you were doing.

The same principles apply to CSS files, although comments are left in a CSS file type with /*     */.

Using comments to outline the different style groups you intend to use in your projects can help you find the parts you want to edit. In general, using comments is something everyone should do. They are very helpful in JavaScript and other languages when making notes about what a function does or should be doing. You can also leave yourself notes about what you were working on. 

[jihnari]

i have a thousand things i should be doing today but instead i figured out how to make epubs

and it's going great!!!

look at that!! look at that beautifully locally rendered dialog box!!!

thought id start small, something with a css file and some images but nothing too fancy. it took about two hours from vague thought to much research to final success.

turns out an epub is just a zip file with html and css in there! so that's easy. harder is that there's little to no way to get decent debug messages when you screw up. also i couldn't figure out how to get my xhtml file to see a folder with images in it so the images are scattered in the main folder but hey! they render!

[weepingwitch]

i know this means absolutely nothing to most people but basically all of the little web game things I've made recently (angels in automata, hex plant growing game, d.a.n.m.a.k.u., life music, sudoku land, the metroidvania style map editor, etc etc etc) are all entirely self-contained individual client-side html files that can be downloaded and run offline and have literally no libraries or frameworks or dependencies, because i'm an insane woman who enjoys hand coding my input handling and display code from scratch in vanilla js and having it all live in one single html file with the game logic and the page structure and the page style all just living and loving together side by side in a universal format that can be run by any web browser on any devixe. i'll even include image files as base64 data-uri strings just to keep every single asset inside the one file.

[webtutorsblog]

Unlimited Learning: HTML Tutorial for Beginners - WebTutor

Are you looking to learn HTML? Look no further! At WebTutor.dev, we offer comprehensive HTML tutorials and resources to help you become proficient in HTML, whether you're a beginner or an experienced developer. Our website is designed to provide you with an immersive and engaging learning experience, covering all aspects of HTML, from the basics to advanced concepts.

Why Choose WebTutor for HTML Learning?

Free Online HTML Editor: We understand that practice is key to mastering HTML. That is why we provide a free online HTML editor that allows you to practice your coding skills in a real-time environment. Our editor comes with a range of features and tools to help you write, test, and debug HTML code efficiently.

Best HTML Editor Recommendations: Looking for the best HTML editor for your coding needs? We have got you covered! Our website offers recommendations for the best HTML editors available in the market, based on user reviews, features, and ease of use.

Beginner-Friendly HTML Tutorials: If you are new to HTML, don't worry! Our tutorials are designed with beginners in mind. We start with the basics and gradually progress to more complex concepts, with clear explanations and examples to help you grasp the fundamentals of HTML.

Learn at Your Own Pace: At WebTutor.dev, we believe that learning should be flexible and tailored to your needs. That's why our tutorials are self-paced, allowing you to learn at your own speed and convenience. You can access our tutorials anytime, anywhere, and from any device.

Comprehensive Learning Resources: Our website is a treasure trove of learning resources for HTML. From tutorials and articles to quizzes and practice exercises, we offer a wide range of materials to help you reinforce your learning and solidify your HTML skills.

Best Place to Learn HTML and CSS for Free: If you are looking to learn both HTML and CSS, WebTutor.dev is the best place to do it for free! Our tutorials cover both HTML and CSS, giving you a complete foundation in front-end web development.

Supportive Community: Learning HTML can be challenging, but you don't have to do it alone. At WebTutor.dev, we foster a supportive community where you can connect with fellow learners, share your progress, ask questions, and get help from experienced developers.

HTML Developer Career Opportunities: HTML is a fundamental skill for web development, and mastering it can open a world of career opportunities. With our comprehensive HTML tutorials, you will be well-equipped to pursue a career as an HTML developer and create dynamic and interactive websites.

HTML is Easy to Learn: If you are wondering whether HTML is hard to learn, fear not! HTML is a markup language, not a programming language, and it is considered one of the easiest languages to learn for beginners. With our step-by-step tutorials and interactive learning resources, you will find HTML a breeze to learn and master.

Whether you are a beginner or an experienced developer, our HTML Introduction page has something for everyone. From HTML tutorials for beginners to advanced HTML concepts for professionals, we have got you covered. So why wait? Start learning HTML today!

[codewithnazam]

HTML Tables with examples: A Comprehensive Guide for Web Developers on Creating, Formatting, and Displaying Data

I. Introduction In this article, we will explore the world of HTML tables and their importance in web design. HTML tables are an essential part of building websites, as they allow developers to organize data and information in a structured and visually appealing way. They enable users to present information in a tabular format, making it easier to read and understand. HTML tables are used in a…

[dduane]

Hello! Do you think your conception of magic in YW is influenced at all by computer code? Between High Wizardry and some of the website admin stuff you discuss here, I'm guessing you've coded at least a little.

I'm an actor-turned-librarian who's cobbled together a little bit of coding competency through goofing off. The other day I tried to explain how I conceptualize a coding project and, well, first you need to figure out something's name -- and make sure you're properly specific for the context, you may need a lot of detail in how you name it -- and then you can start figuring out how to persuade it to do what you want ....

So I guess it's sort of a chicken-and-egg question: have I conceptualized coding in the image of my favorite fictional magic systems, or have I been generally drawn to magic systems with a sort of code-y, process-y inspiration?

I wouldn't like to second-guess your in-brain structure. But I can talk about my historical processes a bit, as they may apply to this.

Let me step back slightly. Before* I was a writer, I was a nurse. Before I was a nurse, I was studying to be an astrophysicist. Both of these arts/sciences require a certain sense of the hard structure of the universe—of the ways it requires you to put bits of it together if you're going to get anything useful done. This general outlook has determined, to a certain extent, how I interact with the nuts and bolts of the online world.

More historically speaking: I'm one of an unusual stratum of computer users who were technologically orphaned by the (bankruptcy) failure of the Osborne computer company in the mid-1980s. Those of us who had these machines, and who were at all techie-oriented, quickly became WAY more so in an attempt to keep our Osbornes running after the company went under. We learned how to keep our babies going without any available support, and when we moved on to other machines, we quickly became expert in fixing them... having learned the bitter lesson that when your computer fails, most of the time you're the only one you're going to be able to rely on to keep it going.

We learned to do things for ourselves, from the bottom up: hardware to programming. That mindset has remained with me from then until now.

After my Osborne, I moved from an early Apple (lent by our old friend Michael Reaves) to various early DOS/TRS machines when I moved over to this side of the Atlantic. I wrote Star Trek: The Kobayashi Alternative on a TRS-80 Model 100, gods bless its gentle hardworking heart. (I can still see in my mind the pale, pine-panelled interior of the ancient creaky London hotel, just south of Notting Hill Gate Tube, where I did most of the Trek work while I was in town on other business. I'd hooked the computer's modem to the hotel's phone system with alligator clips.) While Peter and I were later sorting out where we'd live on this side of things, for a long time—before portable computers, except for the TRS—the big machines lived in the boot of the Volvo while we migrated from place to place. And always the alligator clips were there.

Finally we settled in Ireland, and not too long after us, so did the Internet. (But not before I had to go up to Dublin one time, with the alligator clips again FFS!, and show the adorably clueless national telephone company guys how to hook up/in. ...I never pass that building without thinking of it: once Telecom Eireann, then Eircom, then Eir. Now it's a Starbucks. No matter. I remember where to hook the alligator clips in.)

And then, with the internet, lo, there came the (net-oriented) coding. Our first household web site went online in 1995. I handcoded our site's HTML. (Because what's a girl to do: wait for the techbois to make such work accessible or affordable? Bwahahahaha.) I continued to do that until the early 2000s, at which point I moved our sites to Drupal and learned its obscure ways. These days—having decided that Updating Damn Drupal Core Every Week is not what my mom raised me for—I've migrated all our household sites to WordPress, and I like it. I still pay a lot of attention to them, but at least I don't have to custom-code every whole damn page. I'm happy enough to let Elementor do that, while inserting occasional custom CSS, because (a) I have other writing to do, and (b) Life Is Too Short.

(I also used to hand-build our household computers, because (a) money was short and (b) why not know exactly what all your hardware is? But more recently I've started letting Scan in the UK do that. It's another Life Is Too Short thing... and Scan does good work. Lovely tight builds, and good customer service when needed.)

So: yeah, I code. :) Is the Young Wizards universe’s spell structure influenced by that? Uh, yeah. Inevitable, I’d think. Habit is such a taskmaster.

Meanwhile, summing up: I'm fluent in HTML. I'm nearly as fluent in CSS. I have enough PHP to be dangerous (to myself as well as others). I have memories of C that I can dredge up when necessary. I generated most of the Rihannsu language in MS-BASIC, gods bless it. ...And beyond that (as we say around here), deponent saith not. :)

*Or “while”, as I started writing when I was six or seven.

[codemerything]

A structured way to learn JavaScript.

I came across a post on Twitter that I thought would be helpful to share with those who are struggling to find a structured way to learn Javascript on their own. Personally, I wish I had access to this information when I first started learning in January. However, I am grateful for my learning journey so far, as I have covered most topics, albeit in a less structured manner.

N/B: Not everyone learns in the same way; it's important to find what works for you. This is a guide, not a rulebook.

EASY

What is JavaScript and its role in web development?

Brief history and evolution of JavaScript.

Basic syntax and structure of JavaScript code.

Understanding variables, constants, and their declaration.

Data types: numbers, strings, boolean, and null/undefined.

Arithmetic, assignment, comparison, and logical operators.

Combining operators to create expressions.

Conditional statements (if, else if, else) for decision making.

Loops (for, while) for repetitive tasks. - Switch statements for multiple conditional cases.

MEDIUM

Defining functions, including parameters and return values.

Function scope, closures, and their practical applications.

Creating and manipulating arrays.

Working with objects, properties, and methods.

Iterating through arrays and objects.Understanding the Document Object Model (DOM).

Selecting and modifying HTML elements with JavaScript.Handling events (click, submit, etc.) with event listeners.

Using try-catch blocks to handle exceptions.

Common error types and debugging techniques.

HARD

Callback functions and their limitations.

Dealing with asynchronous operations, such as AJAX requests.

Promises for handling asynchronous operations.

Async/await for cleaner asynchronous code.

Arrow functions for concise function syntax.

Template literals for flexible string interpolation.

Destructuring for unpacking values from arrays and objects.

Spread/rest operators.

Design Patterns.

Writing unit tests with testing frameworks.

Code optimization techniques.

That's it I guess!

[eamour]

Hiii, im still fairly new to tumblr and I was wondering how do you get the pretty text colors in your blogs? Are they images or are you changing the color of your text?

Sorry if this is a weird question-..

Thank youuuu

hey ♡

no, it’s not a weird question at all! i‘ll give you a guide.

✿⠀all about coding

for the colour in my texts i use html coding and hex codes.

to simplify this, html is used to design or structure your texts (you know, the size, the colour, if it’s italic or bold,…) the hex code then determines the colour you choose for your text.

unfortunately, you cannot edit your texts' colours on your phone but make sure to do it on your laptop/computer.

✿⠀in steps

example · let’s say i want to edit my post and want the header to say "hello!" in a pinky shade (let’s use the hex code #c98ba3). this is what i would do ...

go on the tumblr website on my laptop

click create

choose text

click on the gear icon on the upper right corner

scroll to text editor and select HTML

click anywhere on the screen to make that page disappear and return to my post

switch from preview to HTML

type in the code <p><span style="color: #c98ba3">hello!</span></p> in the second row, not where it says "title"

switch back to preview and boom! now my text that says "hello!" is pink :)

✿⠀notes

if you are looking for colours to use and their associated hex code, just know that google's "colour picker" shows up once you look for a hex colour picker.

⠀⠀⠀i hope this could help you ♡

[zoeythebee]

This is THE single largest milestone in my entire 7 year game programming career.

I don't think I've ever gone over my history with moving platforms before, but basically. Back in my sophomore year of highschool I had a programming class! I hadn't chosen to take it, but the class I wanted got cut so I got this instead. And I already knew how to program, and the teacher was chill so I was like "can I like just work on whatever?" and she said sure. The rest of the class was doing an online html+css class.

Anyway I was like "yo I have an entire class period to program! I am gonna make a game!" That game was the first version of ThreeEye, and it's scope was very small. My plan was some like 8 levels, and the only mechanics were movement, spikes, and moving platforms. Spikes were extremely easy.

But there are no words for the difficulties I faced trying to impliment moving platforms.

I spent... Every. Single. Class period.

For. A. Semester.

Trying get them working.

I tried making the game in Gamemaker and Godot.

In Gamemaker I had a strange issue with the player sorta hovering above the platform, instead of cleanly moving on top of it. And also sinking a pixel inside of the platform when moving up. I never fixed it.

I then tried Godot, and I continued to struggle.

Oh I struggled, I struggled and struggled and struggled.

And was it worth it? No.

I found the bug, and it was caused by my refusal to actually read documentation and instead follow tutorials. The tutorial I was reading had the arguments for a 'move_and_slide_with_snap` function out of order.

So I fixed the bug.

And immediately found another bug that was even more dramatic and hard to debug.

And I quit.

I quit game dev for 2 years, and never looked back. At that point almost all I had done was watch tutorials and ineffectively debug. And I was so hyper focused on fixing this ONE issue that I never grew. I burnt out and I declared that programming wasn't for me.

2 years later I discovered a video of someone making a game without a game engine, but in C. And I thought it looked fun. So I decided that I would try programming again, but I wouldn't focus on trying to FINISH something. I would program as a hobby, and try to enjoy the act itself.

And I got that spark back, and now, 2 and a half years later. I solved moving platforms with the following 2 lines of code.

And it's not these lines specifically, my skills as a programmer and EVERYTHING surrounding these two lines is what brought me here. My code structure was good enough, such that actually implementing the moving platforms took 5 minutes. I copy and pasted some code, cut some stuff out, and added the above lines.

I know I am technically a better programmer than when I first faced this challenge, but after having actually beat it. I feel like I have made it further than I ever had before.

Also that means this game is also further along in progress then anything else I've made before.

Yippie!

[libraford]

I will sometimes complain that I don't make much money and someone who is very well-meaning will advise me to 'learn to code.'

That's like telling someone to 'learn to draw an anatomically correct hand.'

I'm pretty good at drawing hands because I drew throughout high school, did art programs in college, and continued to draw consistently as an adult- so I developed a knack for drawing complicated things.

There are a lot of people who cannot draw hands. It doesn't make them bad artists, it just means that they didn't focus on the same things as I did. And if they focused on drawing hands, maybe they'd get pretty good at it, too.

But also maybe they wouldn't! Some people just don't! Like they can study and sketch the bone structure and the guidelines and the forms to hell and back but turning it into a hand just isn't happening.

That's me with code. I know enough html to hotlink some text and turn it into fun colors. I tried to learn some code in college because we were told that it would be required of us in our professional lives, but I did not get very far. Its not because I'm lazy, or that I had a bad teacher, or that I don't WANT to- my brain just does not do numbers the way that coders do numbers.

I watch my photography mentor in one of her zoom meetings rattle off coding terms and I'm jealous. My brain can't do that. She watches me sketch out compositions and maps for photoshoots from memory and she's jealous. I watch my girlfriend cut an old prom dress into pieces and sew it back together into a costume and I'm jealous. She sees me dance in it and she's jealous.

Like I understand that this is the direction of the world- that coding is a very important skill that pays well because its in demand (or is it? I've had so many coding friends get laid off in the past year that it makes me nervous) but I don't see the point in learning a skill that I know will frustrate me, that I will not be good at, and that I will inevitably be the first to be let go if I manage to get a job in the field.

[cthulhubert]

Alright, so bear with me.

Humans have three cone cells in our eyes that are how we perceive color in the world. I often think red, green, and blue, but apparently people studying them use Long, Medium, and Short to be unambiguous (just for one example, if you activate M really strongly and not L or S, the color people report seeing is yellow-green). Each type activates at different strengths to different wavelengths of light. Here's a lovely graphic from Wikipedia showing response levels of each cone type to different wavelengths:

So you can see that if some light activates L some, but not M, we'll perceive deep red, activates them both a bit, we see orange or yellow, depending on the specific amount.

It's interesting that some effect (a specific mix of pigments, or some structural coloration) could be producing some mostly 495nm light, or a blend of some slightly higher and slightly lower wavelengths, and either way we see cyan. (And a good thing, too, otherwise our display technology would be extremely unconvincing.)

Of course, then there's what happens when we get activation of L and S at once, but not M, our eye-brain systems don't infer "yellow-green", because green is specifically what's missing from there: we generate magenta, a non-spectral color. (And when all three activate we get white, of course.)

I found myself thinking about birds, with their four cones.

They're more evenly spaced too, the bastards. (These bastards are specifically finches but I'm under the impression that most birds are similar.)

(Of course, "violet" actually means ultra-violet here. Look at the graphic, their UV cone stops responding where our S cone starts. I would edit this, but spent like half an hour discovering that tumblr doesn't support table under html or code/"preserve formatting" under markdown anymore; so you get a screencap of what I sent on discord.)

Birds could see "vio-green" (accepting name suggestions) as a color region as distinct from blue/indigo as green is from purple/magenta.

Look at that. Two whole ass independent spectral color divisions we don't have, and six non-spectral inferences. Eight whole categories of visual perception more than us. Decadent.

The heart quails to imagine what the 16 color receptors of a mantis shrimp would create. I mean, okay, it doesn't because we've studied their eyes and brains and they don't blend colors the way we do, smooshing them down to a much simpler set of perceptions.

But imagine if we rebuilt our eyes and brains for it! Color indicates chemistry, with that level of subtle blending of characteristics, would vision become like tasting everything we look at?

Please pet the bear that is with me on your way out.

[copperbadge]

With the new post editor on tumblr being pushed harder and harder, and the increasing warnings that the legacy editor will go away soon, I was wondering if anyone actually knows like...why they are doing this. 

Wordpress, which owns Tumblr, has the same unwieldy and crash-prone structure on its site, where each paragraph, image, media, or other element of a page or post is a “block” and you combine blocks to make the page. Because I produce a lot of original content and a significant portion of it is fairly complex (lots of text, text and photos interacting, links lists), I constantly run into the issue, with the new editor, of being unable to edit posts comprehensively because I have to move paragraphs one at a time (no selecting more than one block!) and if I select the start or end of a paragraph to edit, it either refuses to edit at all, or crashes. If a post is longer than about a page, the editor crashes regardless, consistently, and generally just after I’ve made significant edits that haven’t yet saved. (Sometimes it crashes because it tried to save.) 

I suppose it’s possible that Wordpress just thinks we’re dumbfucks who can’t program html and is trying to make it “easier” but it’s not making like...anything easier. I can’t imagine it takes less processing power on the code end, either, or my posts wouldn’t crash, something they never do in the Legacy editor.

So like...what’s the benefit of this? Does anyone know? I presume there is one, I just can’t figure out how this new post structure (or the page structure on Wordpress, which causes me headaches every time I try to update my author site) is of any benefit to anyone, anywhere. Presumably this makes Tumblr and Wordpress more compatible but like, why the fuck are they doing it this way on Wordpress, either? Can someone explain it to me like I’m five, please. (I’m a pretty bright five but still.) 

[lanayrucodes]

Immortales: Skin Bundle ($20)

I've been wanting to branch out into a more minimalist style for a while, and found the opportunity to do so when I was struck by the coding bug over the weekend and began to experiment with a more semi-transparent style of index that eventually evolved into this. I tried to keep the skin as light as physically possible, with minimal Javascript or Jquery inclusions, and instead tried to optimize it to build off of HTML5 elements as best I could without needing to weigh it down with more external resources.

The Immortales skin is a dark themed, responsive skin for Jcink forums, and is optimized for Google Chrome. (Cross-tested in Opera GX and Mozilla Firefox.)

You can purchase the skin here: https://ko-fi[DOT]com/s/6f663cfe6e

Bundle Includes:

All custom HTML structures

a forum index a topic row for threads a post row with a sticky/hover mini profile a main profile custom board stats, with the five (5) recent topics appended a member list, sortable by filters

Full set of DOHTML templates

x1 general announcement/admin template x1 application template (tabbed, for threads) x4 thread templates x5 development templates x1 miscellaneous codes for TW/CW x1 tabbed webpage/guidebook

Custom Userlinks Menu

Easy to add/modify group variables for color coordination (five groups already included)

Responsive to smaller monitors

Upon purchase, buyers will receive an installation guide with editing and customization instructions, as well as any XML/HTML files.

Support & Refunds:

Refunds or returns are not offered on pre-made skins. Due to the nature of how they're distributed and the fact that they're digital files I cannot offer refunds for a purchase if you buy a skin from me.

If you encounter bugs or skin-breaking issues, please reach out to me and I will do my best to fix them and provide you with updated files.

I do not offer coding support beyond initial problems with my skins at install. (i.e. Finding a bug when you install a fresh copy of the skin onto your site, etc.) If the skin breaks during modifications you make on your own, I am willing to help restore the skin to it's original state. I do not provide support for third party coding that is not mine.

[peekaboorpg]

Avec la màj d'hier sur Epicode, j'ai eu envie d'updater mes LS/tutos dessus et je commence par reprendre le guide des différentes versions de forum ! Malheureusement, il faut avoir un compte pour lire, donc pour ceux qui en ont un voici le lien du sujet :

et pour ceux qui n'en ont pas, je vous invite à cliquer sur le lien ci-dessous pour lire l'article complet directement sur tumblr.

Disclaimer : je suis quasi sûre qu'il reste plein de choses à dire, n'hésitez pas à me suggérer des rajouts (notamment sur phpbb3 et punbb que je connais pas bien) et j'updaterai ça ✨

Choisir la version de son forum

La première étape de la création d’un forum est de choisir parmi 6 versions différentes celle que vous souhaitez. Mais ce n’est pas forcément évident pour tout le monde, surtout quand on a aucune idée de ce que ces noms signifient !

A quoi ça sert, la « version » du forum ?

Pour simplifier, il s’agit de l’élément qui va déterminer la structure HTML de base de votre forum. PhpBB2 va par exemple faire une structure en tableaux (= avec <table>, <tr>, <td>) alors qu’Invision va faire une structure avec des éléments en flottement (=avec float, position) ModernBB et AwesomeBB sont beaucoup plus modernes que les autres et utilisent des standards comme flexbox et grid.

Globalement, ce choix ne vous empêchera pas de coder les choses comme vous le voulez par la suite si vous êtes déjà à l’aise avec vos templates, ce n’est que pour déterminer la structure de base, mais il est quand même important de partir sur une base de templates qui vous convient plutôt que d’avoir à tout transformer vous-même.

Comment choisir ?

— PhpBB2

Forumactif la décrit ainsi : « PhpBB2 est la version qui vous permet de totalement personnaliser votre forum. Si vous avez besoin d'un forum flexible et stable, n'hésitez pas à essayer cette version. » En réalité, toutes les versions permettent de personnaliser de A à Z son forum, c’est surtout la plus ancienne version sur la plateforme et elle est donc très datée, mais elle est toujours fonctionnelle.

Avantages

Beaucoup, beaucoup des LS disponibles sur les forums d’entraide sont des LS compatibles avec PhpBB2 seulement. Pour les utilisateurs de LS qui n’ont pas forcément de connaissances en HTML, la version PhpBB2 est plus riche en ressources. De plus, les tutoriels d’apprentissage sont aussi très souvent en PhpBB2, ce qui rend cette version très accessible… Malgré de nombreux désavantages.

Désavantages

La structure en elle-même n’est pas extrêmement claire pour les débutants, même si encore une fois la plupart des tutos d’apprentissage sont sur PhPBB2. De plus, elle ne donne pas forcément de bases très correctes puisque, comme je disais en introduction, cette structure est basée sur des tableaux et peut inciter à structurer tous vos futurs codes en tableaux là où des techniques plus actuelles permettraient de produire des codes nettement plus modernes et clairs. (En utilisant flexbox ou grid notamment, comme ce sera le cas dans Modern et AwesomeBB.)

— Invision

Forumactif la décrit ainsi : « Invision est une des versions les plus performantes de Forumactif, sa puissance et sa stabilité rendent cette version incontournable aux utilisateurs qui souhaitent exploiter au maximum leur forum. » Je conseillerais en effet plutôt cette version aux personnes déjà à l’aise avec le codage, puisqu’elle intègre des techniques plus modernes de codage… Qui ne sont déjà plus assez modernes.

Avantages

Elle est bien plus facile que PhpBB2 d’un point de vue codage. Les templates sont construits de façon bien plus claire et l’affichage du thème de base contient des petites choses sympathiques comme (entre autres) des catégories rétractables, et l’affichage de la liste des membres en petits blocs plutôt qu’en liste. Il permet également d’aligner les profils à gauche ou à droite dans les messages en utilisant un simple bouton dans le panneau d’admin (Général → Forum → Configuration → Structures des pages, option Position du profil dans les messages).

Désavantages

À nouveau, le désavantage majeur est le manque de LS/tutos sur cette version qui est pourtant très intéressante. À noter cependant qu’elle utilise les flottements (float et position) pour placer ses éléments, un standard aujourd’hui déprécié au profit de flexbox/grid. Cette version a quelques LS disponibles, mais les ressources et les aides demeurent limitées, car elle a été très vite éclipsée par ModernBB.

— ModernBB

Forumactif la décrit ainsi : « Le thème ModernBB permet de créer un forum design, simple et intuitif. Le code a été modernisé pour faciliter les personnalisations du forum. » En effet, le look de base est beaucoup plus plaisant et moderne que les versions précédentes ; et le code est beaucoup plus conforme aux standards de codage d’aujourd’hui, utilisant en majorité flexbox pour créer des colonnes. Il est donc aussi beaucoup plus clair pour apprendre à coder.

Avantages

L’affichage de base de ModernBB offre des fonctionnalités sympas, comme un header pleine largeur, une barre de navigation qui suit le scroll, les catégories rétractables, la position droite/gauche du profil dans les messages, et des statistiques qui s’affichent en footer du forum. De plus, elle est en partie responsive (c’est-à-dire qu’elle s’adapte aux petites largeurs d’écrans) avec un mode mobile-friendly. Récemment, Forumactif a aussi permis d’afficher des images dans la liste des sujets sous cette version.

On note également l’existence d’une ressource très utile, le Blank Theme de @code-lab, qui permet d’avoir une base propre et optimisée pour commencer à coder sur cette version et la rend beaucoup plus accessible aux débutants comme aux confirmés.

Désavantages

Bien qu’on pousse désormais pour que les ressources s’adaptent à cette version, il n’y en a toujours pas autant que pour PhpBB2. Néanmoins, cette version est celle qui est privilégiée désormais pour les nouveaux LS.

— AwesomeBB

Forumactif la décrit ainsi : « Le principal avantage de la version AwesomeBB est sa fonction responsive. Votre forum s'adapte à toutes les tailles d'écran, les membres peuvent ainsi discuter, partager des photos et chatter aussi bien sur PC que sur mobile. » Effectivement, cette version est entièrement responsive car elle est codée de façon moderne et cohérente avec les standards de codage actuels.

Avantages

AwesomeBB regroupe tous les avantages de ModernBB avec quelques différences d’affichage, notamment la prise en compte de la toolbar directement dans la barre de navigation, offrant des panneaux latéraux qui s’ouvrent au clic.

Désavantages

Il n’y a littéralement aucunes ressources disponibles en forum d’entraide pour cette version.

Changer de version

Il est possible de changer de version de forum à n’importe quel moment.

Panneau d’administration → Affichage → Choisir un thème → Onglet « Version »

Mais attention ! Puisque chaque version a sa propre structure HTML pour le forum, vos templates modifiés ne seront plus compatibles avec, et l'opération supprimera votre CSS. Certains javascripts peuvent aussi être incompatibles et devront être modifiés pour fonctionner. En clair, votre contenu (messages, avatars, comptes, etc…) sera sauf, néanmoins votre forum n’aura plus du tout la même apparence.

Et en résumé ?

Au final la véritable hésitation se situe entre PhpBB2 et ModernBB. Actuellement, l’offre des forums d’entraide permet surtout de se familiariser avec PhpBB2 qui est pourtant très vieillot. La version ModernBB est néanmoins très intéressante malgré le manque d’encadrement pour ceux qui veulent s’y lancer, et gagne en présence sur les nouveautés en LS/tutos.

Pour ceux qui ne souhaitent pas se plonger dans le code profond de leurs forums et simplement personnaliser l'apparence grâce au PA et aux images, le choix est nettement plus simple : basez vous simplement sur l'apparence de chaque version pour décider de la structure qui vous plaît le plus. Pour voir les différentes versions "en action", voilà les liens d'aperçu fournis par forumactif :

PhpBB2

PhpBB3

PunBB

Invision

ModernBB

AwesomeBB