Proposal : Logo for the project and new website design #4920
-
|
I am willing to create a logo for this project. Please share opinions.
Let me know if there is no need for logo&/design. |
Beta Was this translation helpful? Give feedback.
Replies: 22 comments
-
|
I propose calling it A better web-presence sure wouldn't hurt. Just yesterday i was attempting to help out somebody on the skunity forums. It turned out he was still using Skript 2.1.2, released in 2014 on bukkit - which he considered the Would love to help out on documentation aswell |
Beta Was this translation helpful? Give feedback.
-
|
Damn man, the docs redesign looks amazing! I love the color choice, font, padding, everything. A little bit of criticism though: I don't think the fork name is needed on the logo anymore, this fork is the only one actively being developed, and even the link was recently updated not to contain
Please do continue and feel free to hit me up somewhere if you want to & need help with generating the actual docs. |
Beta Was this translation helpful? Give feedback.
-
|
I continued little bit and this is what it looks like now, going to continue later. Logo
Web design
|
Beta Was this translation helpful? Give feedback.
-
|
when done, can you please pick a license for the designs? Preferably one compatible with skript's |
Beta Was this translation helpful? Give feedback.
-
|
Skript's GNU General Public License v3.0 license is fine for me. Should we create another repo under SkriptLang for design & developement process and with issue tracker to propose ideas or something? Feel free to set new logo as organization avatar. |
Beta Was this translation helpful? Give feedback.
-
|
New website design and new logo? Count me in! It should be easy enough to plug in new CSS and HTML to docs generator. I suppose other improvements could be made to the generation itself, too. @0x4d48 Are you familiar with Git? Could set up a repository for website templates if you want. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I am familiar with Git. Repo would be great. |
Beta Was this translation helpful? Give feedback.
-
|
Alright. Skript's current docs templates (https://github.com/SkriptLang/Skript/tree/master/docs) should have some ideas about how to use them for new styling. In case something is unclear, I can also work on integrating your work to them. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to test |
Beta Was this translation helpful? Give feedback.
-
|
Do you have a Discord account? I think it would be easier to discuss this if you join here https://discord.gg/V4qFVnh |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/SkriptLang/site-templates - I've dropped you invite that gives push access there. It is possible to test the templates locally. Place the template folder (or create a symbolic link) named as doc-templates under plugins/Skript and run /sk gen-docs from server console. Edit: Too many new messages, got confused :) |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
@0x4d48 i'm guessing you are handling the HTML/css, then? If so, keep in mind #1402 will need support for a section documentation page, too. If not, I could give it a shot -- I have mild webdev experience and am the author of #1402 anyway. edit: ignore me i just saw this: |
Beta Was this translation helpful? Give feedback.
-
|
just dropping this here: |
Beta Was this translation helpful? Give feedback.
-
|
Well, if you want to help me with this project, that's ok for me. I would have more resources to put in other projects Also if you have ideas regarding how website works (generating html, reading json), they're welcome. I wouldn't want though to do anything else than a new template. |
.Beta Was this translation helpful? Give feedback.
-
|
@Pikachu920 @xXAndrew28Xx did you mean just generating the docs to json (or using something like TuSKe docs) and then reading them via JS? If yes, on one hand it sounds better for the development purposes for sure, but on the other, kinda RIP non-javascript users, I'm pretty sure all the main languages generate docs that are just static html |
Beta Was this translation helpful? Give feedback.
-
|
Well for sure converting to json. It doesn't really matter to me whether the server parses the json and serves the web content or the client parses it and changes the DOM. |
Beta Was this translation helpful? Give feedback.
-
|
in skript-dev channel it was decided to stay static |
Beta Was this translation helpful? Give feedback.
-
Could you (or somebody else) justify this? For me (web professional) a react site loading and parsing JSON seems much simpler. |
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't say it is simpler, considering Skript already has a HTML template engine for generating docs. Same template engine generates current JSON docs, too. Aside that, using Javascript for static sites has a number of downsides. First, the Javascript and JSON data files will need to be fetched. That takes time, unless HTTP/2 PUSH is available. In addition to that, it requires CPU time from client's computer. Parsing, JIT-compiling and executing JS to construct a static site is, seriously, waste of client's processing power (and battery life). For these reasons, no static site should use Javascript for basic page content. Even if it is more convenient, please think of your users. Unless the site is for internal use in, say, a company, it is bad idea to assume that users have CPU power to waste. That is to say nothing of users who disable Javascript, or do not receive it due to a network errors. It is possible to write fast Javascript code. However, can it be faster than having no executable code in your website? I don't think so. |
Beta Was this translation helpful? Give feedback.
-
|
The docs theme has changed already see #3935 and #4319, this theme is no longer needed. |
Beta Was this translation helpful? Give feedback.
The docs theme has changed already see #3935 and #4319, this theme is no longer needed.