New Site.
I rebuilt the site, yes. No more WordPress crappy infrastructuring, no more Gutenberg mess ups, or security updates 5 times a day.
Does mean more work for me to get it looking good and useful, but i tend to be doing everything for Deso anyway. But the result is a fast site, with builds/guides able to be constructed from .md files with some preset frontmatter values. calling gw2 armory embeds in via shortcodes. for example a gw2 armory embed can be rendered with
{% gw2a item, 'id',"wiki" %}
Next stage with builds is to have the templates translate the buildcode from game or gw2skills.net directly in saving time looking up ID's for each trait. This is more complex than first realised, so I have left manually adding the ID's in each post as default.
Some quick possibly relevant FAQ's! #
- Why does the symbol for Focus look weird.
Good question, I had to make it by hand and not really happy with it. Do you know what weapon hasn't been usable by other classes via Elite/Weapon specializations? Thats right, Focus. Theres no icon for it in the API.
- why do build pages look terrible on mobile/tablet?
I protyped the layout in flexbox at the last minute, it can do mobile/tablet but the CSS isn't in yet. Still fixing.
- Why doesn't Anet news posts have pictures?
I've not worked out how to pull pictures in the feed from content:encoded into pages yet, bit of a pain when the parser doesn't support that, and they are randomly Youtube links instead of pictures. Currently they are embedded in post content, which this framework struggles with.
- Why does Deso suck so much when its permamently full?
Why does Very High population Baruch Bay, when not linked, have multiple zergs on each map all the time? Anet hates us, and the pop caculations are broken. Recently we dropped to High after a major population shift across all servers, with very few players joining Deso, its going to be High while we fight Very High servers with better coverage.
- Can I help with Guides and Builds?
Sure! though i'll likely setup a github repo where Builds and Guides can be stored/edited. This site uses lots of langauges, but likes MarkDown files (.md) as filters run better on them for skill markups. Most of the build info goes in the FrontMatter, with the critical parts being Profession, Buildcode, Type of build and skill IDs