S
What's on your mind?
TEXT
POLL
- All14 posts
- General4 posts
- Announcement8 posts
- Issues2 posts
- Events0 posts
Sort by
Card Layout
Can someone give me a list of the main characters in the epic seven franchise? (Full names by the way. I.e. Ras Elclare)
Just Updated
I wish Promise was added on Apple Music. What do you guys think of the song?
<p>Building the Artifact Template.</p><p>
</p><p>Lets see about getting some Artifacts up. Working into problems with Medallions being included, so use the ArtifactMedallion </p>
</p><p>Lets see about getting some Artifacts up. Working into problems with Medallions being included, so use the ArtifactMedallion </p>
<p>If anyone wants to contribute to Images, please go to epic-seven.fandom.com/wiki/Images_to_be_Processed</p><p>
</p><p>As well, if you can capture images and don't have immediate time to process the sprites out of them, please upload to that page for other's to contribute.</p>
</p><p>As well, if you can capture images and don't have immediate time to process the sprites out of them, please upload to that page for other's to contribute.</p>
<p>Due to limited capability of the Infobox "control", I will be porting Templates that utilize it to Formatted Tables.</p><p>
</p><p>This will be done through limited application. Some of the current Infobox Templates need to have more advanced functionality applied to them and Infoboxes are limited on implementing that functionality.</p><p>
</p><p>One such Template is the Hero Template.</p><p>
</p><p>More information to come as work begins to migrate identified Templates away from the Infobox "control".</p>
</p><p>This will be done through limited application. Some of the current Infobox Templates need to have more advanced functionality applied to them and Infoboxes are limited on implementing that functionality.</p><p>
</p><p>One such Template is the Hero Template.</p><p>
</p><p>More information to come as work begins to migrate identified Templates away from the Infobox "control".</p>
<p>There is a huge problem with scale on the Mobile site.</p><p>
</p><p>Although this is not an immediate problem, as we are still working on getting the Data and formatting foundations in place.</p><p>
</p><p>If possible, could use someone to find out the specific areas of weakness in the display and formatting within these smaller screen formats. I am pretty sure it has more to do with the pixel definitions to sizes, which can be resolved at a later time.</p>
</p><p>Although this is not an immediate problem, as we are still working on getting the Data and formatting foundations in place.</p><p>
</p><p>If possible, could use someone to find out the specific areas of weakness in the display and formatting within these smaller screen formats. I am pretty sure it has more to do with the pixel definitions to sizes, which can be resolved at a later time.</p>
<p>If possible, I could really use someone that would not mind scraping the content from the Announcements into the Wiki.</p><p>
</p><p>Although, not all the content has to be present (like images and videos) but the main content would greatly appreciated.</p><p>
</p><p>The purpose is to make sure that the content is referable for future dates. In other words, the content won't disappear just because the developer no longer supports the game and/or has sold the code to another developer who does not have the data.</p>
</p><p>Although, not all the content has to be present (like images and videos) but the main content would greatly appreciated.</p><p>
</p><p>The purpose is to make sure that the content is referable for future dates. In other words, the content won't disappear just because the developer no longer supports the game and/or has sold the code to another developer who does not have the data.</p>
<p>I will be slowly migrating images to a more standardized name. With the eventual creation of Templates for Badge and Medallion displays. I will need to standardize the associated images.</p><p>
</p><p>Be prepared for clarity on Image naming conventions.</p>
</p><p>Be prepared for clarity on Image naming conventions.</p>
<p>I appreciate everyone contributing content to the wiki.</p><p>
</p><p>Here are some pointers about cleanup and/or contribution:</p><p>1. Header syntax should have limited usage. </p><p>It is great for micro-editing a whole article but should be restricted to content that is related. Content such as individual Skills, Connections, or Specialties should not have a Header markup used; instead, they should have a Definition Markup (See: epic-seven.fandom.com/wiki/Hazel#Skills)</p><p>
</p><p>2. Templates development/contributions:</p><p>- While I generally do most of the Template development, it is greatly appreciated for you to provide granular Template. There is one (1) catch, if a template will only ever be utilize on a single article/page, then it should not be a Template at all.</p><p>- Templates are to allow for boilerplate-like structure and formatting. This allows for minimal content to provide the most visual content. This helps with supporting the article format and overall consistency between similar groups.</p><p>- When developing Templates be sure to NOT use the Template on the article in which you are defining it. This will cause a pseudo-infinite loop to occur. This is why we utilize epic-seven.fandom.com/wiki/Template:Documentation to put the descriptive text about the Template on a separate page.</p><p>- If you find a bug with a Template, please do not start editing it. Make sure you completely understand the down-stream ramification of the modification before you submit. If you are not completely sure, start a conversation on that Templates Talk page or create a discussion (here) about the Template, in question, and make sure to link to the Template.</p><p>
</p><p>3. Any new article should have {{Goldbishop Review}} added to the top of the article.</p><p>- This will allow me to specifically review and verify formatting.</p><p>
</p><p>4. Any new Template should have {{Goldbishop Review}} added to the <noinclude> block.</p><p>- This will allow me to effectively manage and efficiently identify new content.</p><p>
</p><p>This page will Grow and future Guidelines will be added, so keep checking back....After a period of time, they will eventually make there way into the contributing article for wider consumption.</p>
</p><p>Here are some pointers about cleanup and/or contribution:</p><p>1. Header syntax should have limited usage. </p><p>It is great for micro-editing a whole article but should be restricted to content that is related. Content such as individual Skills, Connections, or Specialties should not have a Header markup used; instead, they should have a Definition Markup (See: epic-seven.fandom.com/wiki/Hazel#Skills)</p><p>
</p><p>2. Templates development/contributions:</p><p>- While I generally do most of the Template development, it is greatly appreciated for you to provide granular Template. There is one (1) catch, if a template will only ever be utilize on a single article/page, then it should not be a Template at all.</p><p>- Templates are to allow for boilerplate-like structure and formatting. This allows for minimal content to provide the most visual content. This helps with supporting the article format and overall consistency between similar groups.</p><p>- When developing Templates be sure to NOT use the Template on the article in which you are defining it. This will cause a pseudo-infinite loop to occur. This is why we utilize epic-seven.fandom.com/wiki/Template:Documentation to put the descriptive text about the Template on a separate page.</p><p>- If you find a bug with a Template, please do not start editing it. Make sure you completely understand the down-stream ramification of the modification before you submit. If you are not completely sure, start a conversation on that Templates Talk page or create a discussion (here) about the Template, in question, and make sure to link to the Template.</p><p>
</p><p>3. Any new article should have {{Goldbishop Review}} added to the top of the article.</p><p>- This will allow me to specifically review and verify formatting.</p><p>
</p><p>4. Any new Template should have {{Goldbishop Review}} added to the <noinclude> block.</p><p>- This will allow me to effectively manage and efficiently identify new content.</p><p>
</p><p>This page will Grow and future Guidelines will be added, so keep checking back....After a period of time, they will eventually make there way into the contributing article for wider consumption.</p>
(Edited by Goldbishop)
This post is locked.
<p>Due to recent issues, the Hero Template is currently not editable. I am working with Wikia Support to identify and resolve the issue.</p>
<p>I am working on a long-term approach to Event highlighting on the mainpage.</p><p>
</p><p>Ideally, we would only show the last 6 events to occur, automatically.</p><p>
</p><p>Currently, someone has to go in and format the main page to include the new events and remove some set of events.</p><p>
</p><p>I am currently working on this feature, so do not be surprised if the front page looks "normal" one session and is awfully weird the next.</p>
</p><p>Ideally, we would only show the last 6 events to occur, automatically.</p><p>
</p><p>Currently, someone has to go in and format the main page to include the new events and remove some set of events.</p><p>
</p><p>I am currently working on this feature, so do not be surprised if the front page looks "normal" one session and is awfully weird the next.</p>
This post is locked.
<p>As this wikia is being developed, here are some basic guidelines to be aware of.</p><p>
</p><p>1) Monster/Hero/Artifact Information should be present on each page, whether formatted into an InfoBox or not. All the information will make its way into the InfoBox where appropriate; otherwise, it will be left on the article page in a formatted approach.</p><p>2) Categories are fluid at the moment, so be patient. As we work to organize the content into a easily searchable approach, some content may go in and out of various categories.</p><p>3) Templates are highly fluid and volatile, at the time of this post. Therefore be patient and communicate with the modifier via the Templates Talk page.</p><p>4) If a page does not exist, BY ALL MEANS DROP RAW DATA IN. The active members will catch the new article(s) and apply the current InfoBox format.</p><p>5) Heros can be Monsters AND Monsters can be Heros. As far as definition, we use the Journals (in game) as the demarcation to define whether to use Monster or Hero Infoboxes.</p>
</p><p>1) Monster/Hero/Artifact Information should be present on each page, whether formatted into an InfoBox or not. All the information will make its way into the InfoBox where appropriate; otherwise, it will be left on the article page in a formatted approach.</p><p>2) Categories are fluid at the moment, so be patient. As we work to organize the content into a easily searchable approach, some content may go in and out of various categories.</p><p>3) Templates are highly fluid and volatile, at the time of this post. Therefore be patient and communicate with the modifier via the Templates Talk page.</p><p>4) If a page does not exist, BY ALL MEANS DROP RAW DATA IN. The active members will catch the new article(s) and apply the current InfoBox format.</p><p>5) Heros can be Monsters AND Monsters can be Heros. As far as definition, we use the Journals (in game) as the demarcation to define whether to use Monster or Hero Infoboxes.</p>
(Edited by Goldbishop)
